blocks|key|4043939|text|你有没有看过使用Swiftmailer库的功能？|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4043940|4043941|我在过去使用过它，并获得了很好的结果，尽管不是在你所描述的应用程序中，但我已经将它用于基于PHP的‘邮件列表’，在那里我检查主题并发送到适当的组。|4043942|但我创建了一条新消息，没有转发。希望这能有所帮助。|4043943|entityMap^0|8|B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|P|8|@]|D|@]|E|$]]|$1|G|3|H|5|6|7|Q|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|R|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

Have you taken a look at functionality using Swiftmailer library ?

<a href="http://swiftmailer.org/" rel="nofollow">http://swiftmailer.org/</a>

I have used this in the past and have gotten good result, altho not in an application like you have described, I have however utilized it for PHP based 'mailing lists' where I checked for subject and sent to proper group.

But I created a new message, did not forward. Hope that helps.

blocks|key|1541571|text|这并不是一个真正的答案，而是对另一种方法的建议。我认为，如果您只是将邮件移动到现有帐户内的不同文件夹中，则会简单得多，也不容易出错(即，不会出现传递问题)。也就是说，cron运行并处理收件箱中的所有电子邮件。如果发现停止，它会执行所需的工作，然后(通过IMAP函数)简单地将电子邮件移动到名为“已处理”或类似文件夹的子文件夹中。否则，它会将电子邮件移动到名为“检查这些”或类似文件夹的子文件夹中。这样，您就不需要担心转发、进一步投递或第二个帐户，每个人都可以直接监控已处理、未处理和挂起的邮件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1541572|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This isn't really an answer, but a suggestion for an alternate method. I think it would be much simpler and less prone to error (i.e., no delivery issues) if you simply moved the messages around to different folders within the existing account. I.e., the cron runs and processes all emails in INBOX. If if finds STOP, it does the required work and then (via IMAP functions) simply moves the email to a subfolder named "Processed" or similar. Otherwise, it moves the email to a subfolder named "Check These" or similar. Then you don't need to worry about forwarding, or further deliveries, or a second account, and everyone can monitor the processed, unprocessed, and pending mails directly.

blocks|key|1541579|text|我以前也遇到过这种情况。为了修复它，我必须在使用imap_fetchbody()之后对电子邮件正文执行imap_base64()。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1541580|$body+=+imap_fetchbody($imap,+1,+1);
$headers+=+imap_headerinfo($imap,+1);
$body+=+imap_base64($body);|code-block|syntax|javascript|1541581|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This has happened to me before. In order to fix it I had to do a imap_base64() on the body of the email after I used imap_fetchbody().

<pre><code>$body = imap_fetchbody($imap, 1, 1);
$headers = imap_headerinfo($imap, 1);
$body = imap_base64($body);
</code></pre>

blocks|key|4044046|text|我很久以前就编写了这个方法，使用IMAP将电子邮件消息解析成相应的部分：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4044047|function+Message_Parse($id)
{
++++if+(is_resource($this->connection))
++++{
++++++++$result+=+array
++++++++(
++++++++++++'text'+=>+null,
++++++++++++'html'+=>+null,
++++++++++++'attachments'+=>+array(),
++++++++);

++++++++$structure+=+imap_fetchstructure($this->connection,+$id,+FT_UID);

++++++++if+(array_key_exists('parts',+$structure))
++++++++{
++++++++++++foreach+($structure->parts+as+$key+=>+$part)
++++++++++++{
++++++++++++++++if+(($part->type+>=+2)+%7C%7C+(($part->ifdisposition+==+1)+&&+($part->disposition+==+'ATTACHMENT')))
++++++++++++++++{
++++++++++++++++++++$filename+=+null;

++++++++++++++++++++if+($part->ifparameters+==+1)
++++++++++++++++++++{
++++++++++++++++++++++++$total_parameters+=+count($part->parameters);

++++++++++++++++++++++++for+($i+=+0;+$i+<+$total_parameters;+$i%2B%2B)
++++++++++++++++++++++++{
++++++++++++++++++++++++++++if+(($part->parameters[$i]->attribute+==+'NAME')+%7C%7C+($part->parameters[$i]->attribute+==+'FILENAME'))
++++++++++++++++++++++++++++{
++++++++++++++++++++++++++++++++$filename+=+$part->parameters[$i]->value;

++++++++++++++++++++++++++++++++break;
++++++++++++++++++++++++++++}
++++++++++++++++++++++++}

++++++++++++++++++++++++if+(is_null($filename))
++++++++++++++++++++++++{
++++++++++++++++++++++++++++if+($part->ifdparameters+==+1)
++++++++++++++++++++++++++++{
++++++++++++++++++++++++++++++++$total_dparameters+=+count($part->dparameters);

++++++++++++++++++++++++++++++++for+($i+=+0;+$i+<+$total_dparameters;+$i%2B%2B)
++++++++++++++++++++++++++++++++{
++++++++++++++++++++++++++++++++++++if+(($part->dparameters[$i]->attribute+==+'NAME')+%7C%7C+($part->dparameters[$i]->attribute+==+'FILENAME'))
++++++++++++++++++++++++++++++++++++{
++++++++++++++++++++++++++++++++++++++++$filename+=+$part->dparameters[$i]->value;

++++++++++++++++++++++++++++++++++++++++break;
++++++++++++++++++++++++++++++++++++}
++++++++++++++++++++++++++++++++}
++++++++++++++++++++++++++++}
++++++++++++++++++++++++}
++++++++++++++++++++}

++++++++++++++++++++$result['attachments'][]+=+array
++++++++++++++++++++(
++++++++++++++++++++++++'filename'+=>+$filename,
++++++++++++++++++++++++'content'+=>+str_replace(array("\r",+"\n"),+'',+trim(imap_fetchbody($this->connection,+$id,+($key+%2B+1),+FT_UID))),
++++++++++++++++++++);
++++++++++++++++}

++++++++++++++++else
++++++++++++++++{
++++++++++++++++++++if+($part->subtype+==+'PLAIN')
++++++++++++++++++++{
++++++++++++++++++++++++$result['text']+=+imap_fetchbody($this->connection,+$id,+($key+%2B+1),+FT_UID);
++++++++++++++++++++}

++++++++++++++++++++else+if+($part->subtype+==+'HTML')
++++++++++++++++++++{
++++++++++++++++++++++++$result['html']+=+imap_fetchbody($this->connection,+$id,+($key+%2B+1),+FT_UID);
++++++++++++++++++++}

++++++++++++++++++++else
++++++++++++++++++++{
++++++++++++++++++++++++foreach+($part->parts+as+$alternative_key+=>+$alternative_part)
++++++++++++++++++++++++{
++++++++++++++++++++++++++++if+($alternative_part->subtype+==+'PLAIN')
++++++++++++++++++++++++++++{
++++++++++++++++++++++++++++++++echo+'<h2>'+.+$alternative_part->subtype+.+'+'+.+$alternative_part->encoding+.+'</h2>';

++++++++++++++++++++++++++++++++$result['text']+=+imap_fetchbody($this->connection,+$id,+($key+%2B+1)+.+'.'+.+($alternative_key+%2B+1),+FT_UID);
++++++++++++++++++++++++++++}

++++++++++++++++++++++++++++else+if+($alternative_part->subtype+==+'HTML')
++++++++++++++++++++++++++++{
++++++++++++++++++++++++++++++++echo+'<h2>'+.+$alternative_part->subtype+.+'+'+.+$alternative_part->encoding+.+'</h2>';

++++++++++++++++++++++++++++++++$result['html']+=+imap_fetchbody($this->connection,+$id,+($key+%2B+1)+.+'.'+.+($alternative_key+%2B+1),+FT_UID);
++++++++++++++++++++++++++++}
++++++++++++++++++++++++}
++++++++++++++++++++}
++++++++++++++++}
++++++++++++}
++++++++}

++++++++else
++++++++{
++++++++++++$result['text']+=+imap_body($this->connection,+$id,+FT_UID);
++++++++}

++++++++$result['text']+=+imap_qprint($result['text']);
++++++++$result['html']+=+imap_qprint(imap_8bit($result['html']));

++++++++return+$result;
++++}

++++return+false;
}|code-block|syntax|javascript|4044048|我从来没有深入测试过它，我相信它有一些but，但这可能是一个开始……改编这段代码后，您应该能够将$result索引(text、html、attachments)与转发脚本(例如使用SwiftMailer+)一起使用，而不必担心保持MIME边界的完整性。|offset|length|style|CODE|4044049|entityMap^0|0|0|1C|7|1M|4|1R|4|1W|B|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]|$I|V|J|W|K|L]|$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|N|$]]

I coded this method a long time ago to parse an email message into their appropriate parts using IMAP:

<pre><code>function Message_Parse($id)
{
 if (is_resource($this-&gt;connection))
 {
 $result = array
 (
 'text' =&gt; null,
 'html' =&gt; null,
 'attachments' =&gt; array(),
 );

 $structure = imap_fetchstructure($this-&gt;connection, $id, FT_UID);

 if (array_key_exists('parts', $structure))
 {
 foreach ($structure-&gt;parts as $key =&gt; $part)
 {
 if (($part-&gt;type &gt;= 2) || (($part-&gt;ifdisposition == 1) &amp;&amp; ($part-&gt;disposition == 'ATTACHMENT')))
 {
 $filename = null;

 if ($part-&gt;ifparameters == 1)
 {
 $total_parameters = count($part-&gt;parameters);

 for ($i = 0; $i &lt; $total_parameters; $i++)
 {
 if (($part-&gt;parameters[$i]-&gt;attribute == 'NAME') || ($part-&gt;parameters[$i]-&gt;attribute == 'FILENAME'))
 {
 $filename = $part-&gt;parameters[$i]-&gt;value;

 break;
 }
 }

 if (is_null($filename))
 {
 if ($part-&gt;ifdparameters == 1)
 {
 $total_dparameters = count($part-&gt;dparameters);

 for ($i = 0; $i &lt; $total_dparameters; $i++)
 {
 if (($part-&gt;dparameters[$i]-&gt;attribute == 'NAME') || ($part-&gt;dparameters[$i]-&gt;attribute == 'FILENAME'))
 {
 $filename = $part-&gt;dparameters[$i]-&gt;value;

 break;
 }
 }
 }
 }
 }

 $result['attachments'][] = array
 (
 'filename' =&gt; $filename,
 'content' =&gt; str_replace(array("\r", "\n"), '', trim(imap_fetchbody($this-&gt;connection, $id, ($key + 1), FT_UID))),
 );
 }

 else
 {
 if ($part-&gt;subtype == 'PLAIN')
 {
 $result['text'] = imap_fetchbody($this-&gt;connection, $id, ($key + 1), FT_UID);
 }

 else if ($part-&gt;subtype == 'HTML')
 {
 $result['html'] = imap_fetchbody($this-&gt;connection, $id, ($key + 1), FT_UID);
 }

 else
 {
 foreach ($part-&gt;parts as $alternative_key =&gt; $alternative_part)
 {
 if ($alternative_part-&gt;subtype == 'PLAIN')
 {
 echo '&lt;h2&gt;' . $alternative_part-&gt;subtype . ' ' . $alternative_part-&gt;encoding . '&lt;/h2&gt;';

 $result['text'] = imap_fetchbody($this-&gt;connection, $id, ($key + 1) . '.' . ($alternative_key + 1), FT_UID);
 }

 else if ($alternative_part-&gt;subtype == 'HTML')
 {
 echo '&lt;h2&gt;' . $alternative_part-&gt;subtype . ' ' . $alternative_part-&gt;encoding . '&lt;/h2&gt;';

 $result['html'] = imap_fetchbody($this-&gt;connection, $id, ($key + 1) . '.' . ($alternative_key + 1), FT_UID);
 }
 }
 }
 }
 }
 }

 else
 {
 $result['text'] = imap_body($this-&gt;connection, $id, FT_UID);
 }

 $result['text'] = imap_qprint($result['text']);
 $result['html'] = imap_qprint(imap_8bit($result['html']));

 return $result;
 }

 return false;
}
</code></pre>

I've never tested it deeply and I'm sure it has some bugs, but it might be a start... After adapting this code you should be able to use the <code>$result</code> indexes (<code>text</code>, <code>html</code>, <code>attachments</code>) with your forwarding script (using SwiftMailer for instance), without worrying about keeping the MIME boundaries intact.

blocks|key|2447968|text|使用IO处理程序捕获字符串形式的电子邮件内容，拆分邮件头，然后使用php+'mail()‘函数发送邮件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2447969|否则，如果您真的想使用php-imap执行此操作，|2447970|php-imap扩展名是libc-client，它是pine电子邮件客户端软件的一部分，找出使用pine执行此操作所需的手动步骤，然后查看pine执行的c-client调用。这将为您提供在php中所需的步骤。|2447971|c-client文档相当少，访问pine源代码是获取用法详细信息的最佳方式。|2447972|我想你可能会发现php扩展的作者“为了你的方便或保护”省略或修改了阻碍这条路的东西。|2447973|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

use an IO handler to capture the content of the email as a string, split out the headers and then use the php 'mail()' function to send it.

Else if you really want to do this with php-imap, 

the php-imap extension is libc-client which is part of the pine email client software
figure out the manual steps needed to do it using pine and then look at the c-client calls pine makes to do it. that will give you the steps needed in php.

the c-client documentation is fairly minimal, going to the pine source is the best way to get usage details.

I think you may find that the author of the php extension has "for your convenience or protection" omitted or changed stuff that blocks this path.

We have a cron'ed PHP script that checks an inbox every ten minutes. The purpose of this script is to handle "STOP to quit" functionality for our SMS notification service we provide. If the script finds any emails with the word "STOP" at the beginning of the email, we remove the user from our notification database.

To cover our bases, we'd like any emails that don't meet the above criteria to be forwarded on to another email address (which is an alias) that several people receive and check hourly. However, we're running into problems forwarding the emails from this PHP script.

Knowing how the <code>mail</code> function of PHP works, it's quite obvious we need to reinsert the headers before mailing. However, MIME multipart emails always get sent as a garble of text, including the barriers and any base64 encoded attachments.

Does anyone know of a simple way to take an email message and forward it on properly using a PHP script?

We're using the native IMAP functions built in to PHP 5. We also have access to the PEAR Mail module. However, we have been unable to find any examples or people doing similar tasks by searching Google.

Forwarding emails with a PHP script

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们有一个cron‘’ed脚本，它每十分钟检查一次收件箱。此脚本的目的是为我们提供的SMS通知服务处理“停止退出”功能。如果脚本发现任何在电子邮件开头带有单词"STOP“的电子邮件，我们将从通知数据库中删除该用户。为了覆盖我们的基础，我们希望任何不符合上述标准的电子邮件都被转发到另一个电子邮件地址(这是一个别名)，几个...

问使用PHP脚本转发电子邮件
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用PHP脚本转发电子邮件EN