PHP 中的退回邮件处理 - 任何最新的解决方案？

Bounced mail Handling in PHP - Any up-to-date solutions?

提问by DrSpock

I need to do some bounced mail processing using PHP. Going through the e-mails is no problem, but investing the resources in writing our own library to parse the bounced e-mails is very undesirable.

我需要使用 PHP 进行一些退回邮件处理。浏览电子邮件是没有问题的，但投入资源编写我们自己的库来解析退回的电子邮件是非常不可取的。

There are 3 PHP solutions that I've found that are supposed to be for processing bounced mail, but they are all way out of date and no longer maintained, from what I can see. (PHPList, PHPMailer-BMH, Bounce Handler @ PHPClasses.org)

我发现有 3 个 PHP 解决方案应该用于处理退回的邮件，但据我所知，它们都已经过时且不再维护。(PHPList, PHPMailer-BMH, Bounce Handler @ PHPClasses.org)

Does anyone know of an up-to-date set of rules for processing bounced e-mails? I don't necessarily need any handling logic, even just an up-to-date ruleset would be satisfactory.

有谁知道处理退回电子邮件的最新规则集？我不一定需要任何处理逻辑，即使只是最新的规则集也会令人满意。

Thanks for any assistance.

感谢您的帮助。

回答by hakre

Bounce handling is non-trivial as you need to deal with a lot of different servers and responses. This includes those servers that are misconfigured and bounces because your email/host/IP has been blacklisted / spam-scored. And there are tons of bounces because of "out of office" auto-replies.

弹跳处理非常重要，因为您需要处理许多不同的服务器和响应。这包括那些由于您的电子邮件/主机/IP 已被列入黑名单/垃圾邮件评分而配置错误和退回的服务器。由于“不在办公室”的自动回复，有大量的退回邮件。

A simple solution I know is to put own headers into the message that identify the receiver address and the concrete sending (a token). When it bounces, the bounce can be verified based upon this.

我知道的一个简单解决方案是将自己的标头放入标识接收方地址和具体发送（令牌）的消息中。当它反弹时，可以基于此验证反弹。

Another solution is to encode additional information into the sender address and parse it accordingly for bounces. For this you need to know about how email works, which generally is useful if you need with bounces.

另一种解决方案是将附加信息编码到发件人地址中，并相应地解析它以进行退回。为此，您需要了解电子邮件的工作原理，如果您需要退回邮件，这通常很有用。

• Bounce Email handling with PHP?
• Tool for parsing SMTP logs that finds bounces
• How to check if an email address exists without sending an email?
• Specifying the bounce-back address for email

• 使用 PHP 处理退回电子邮件？
• 用于解析发现退回邮件的 SMTP 日志的工具
• 如何在不发送电子邮件的情况下检查电子邮件地址是否存在？
• 指定电子邮件的退回地址

There is some great answer here on SO (but I haven't found it for this answer) that goes into many details on the topic. If I find it, I'll add it.

这里有一些很好的答案（但我没有在这个答案中找到它），其中包含有关该主题的许多细节。如果我找到它，我会添加它。

The general point is, that I don't know about many PHP based tools to deal with bounces, I know PHPList (PHP components for mailinglist handling) has something in their repository:

一般的观点是，我不知道许多基于 PHP 的工具来处理退回邮件，我知道 PHPList（用于邮件列表处理的 PHP 组件）在他们的存储库中有一些东西：

• Settings for handling bounces (last valid snapshot)(latest equivalent:Bounce Management - PHPList Manual)

• 处理退回的设置（最后一个有效快照）（最新版本：退回管理 - PHPList 手册）

Edit:The related question with the very informative answer is:

编辑：具有非常丰富的答案的相关问题是：

• How to send 100,000 emails weekly?

• 如何每周发送 100,000 封电子邮件？

Edit:It's not much, just some links:

编辑：这并不多，只是一些链接：

I am wondering why there is no standard in email bouncing that allows you easily to identify bounces and the bounce reason - or is there? (like a RFC)

我想知道为什么电子邮件退回没有标准可以让您轻松识别退回和退回原因 - 或者有吗？（如 RFC）

There is RFC3834 - Recommendations for Automatic Responses to Electronic Mailwhich go updated by RFC5436 Sieve Notification Mechanism: mailto.

有RFC3834 - 对电子邮件自动响应的建议，由RFC5436 Sieve Notification Mechanism: mailto更新。

Bouncing is also discussed in part in RFC5321 Simple Mail Transfer Protocol, which clearly gives a reason that an MTA must report back if a message can not be delivered.

在RFC5321 简单邮件传输协议 中也部分讨论了退回，它清楚地给出了一个原因，即如果邮件无法传递，MTA 必须报告。

The main problem is that the bounce-address (the sender) can not be verified in SMTP, so sending a bounce message bears the problem that it probably goes to a wrong person (Backscatter Spam).

主要问题是无法在 SMTP 中验证退回地址（发件人），因此发送退回邮件的问题在于它可能会发送给错误的人（Backscatter Spam）。

A relyable mailer therefore not only checks for bounces but does more with SMTP to gain a certain level of quality, see:

因此，可靠的邮件程序不仅会检查退回邮件，还会通过 SMTP 执行更多操作以获得一定的质量水平，请参阅：

• Bounce Address Tag Validation (BATV)
• Sender Policy Framework (SPF)

• 退回地址标签验证 (BATV)
• 发件人政策框架 (SPF)

The whole Wikipedia page of the Non delivery reportmight be interesting for a first view on the picture.

未交付报告的整个维基百科页面对于第一次查看图片可能会很有趣。

回答by iWantSimpleLife

Here's how I did it once before. It can capture at least over 70% of the bounce mails consistantly.

这是我以前做过一次的方法。它可以连续捕获至少 70% 以上的退回邮件。

In the emails being sent out, put in a custom header (like "x-email-check-id") to have a unique identifer for each email being sent (maybe create a GUID and store that in the database for each email)

在发送的电子邮件中，放入自定义标题（如“x-email-check-id”），以便为每封发送的电子邮件提供唯一标识符（可能创建一个 GUID 并将其存储在每封电子邮件的数据库中）

On the server end, write a cron job to periodically download emails from the bounce address, and look for this header in the reply message. That way, you can match the bounce mail with the email sent out. This way, you can establish that this email is bounced from your sending and is not a spam email.

在服务器端，编写一个cron作业，定期从退回地址下载邮件，并在回复消息中寻找这个header。这样，您可以将退回邮件与发送的电子邮件进行匹配。通过这种方式，您可以确定这封电子邮件是从您的发送中退回的，而不是垃圾邮件。

After that, search the email content for specific keywords to determine the reason for bounce. This list of keywords should be updated often as newer email servers return different text. But here is the list that I used.

之后，在电子邮件内容中搜索特定关键字以确定退回的原因。此关键字列表应经常更新，因为较新的电子邮件服务器返回不同的文本。但这是我使用的列表。

$Email__Full[] = 'databytes limit';
$Email__Full[] = 'exceeded dropfile size';
$Email__Full[] = 'exceeded email quota';
$Email__Full[] = 'exceeded storage';
$Email__Full[] = 'exceeding receiving limits';
$Email__Full[] = 'exceeds the maximum size';
$Email__Full[] = 'folder is full';
$Email__Full[] = 'mail system full';
$Email__Full[] = 'mailbox exceeds allowed size';
$Email__Full[] = 'mailbox full';
$Email__Full[] = 'mailbox has exceeded the limit';
$Email__Full[] = 'mailbox is full';
$Email__Full[] = 'mail box full';
$Email__Full[] = 'out of disk space';
$Email__Full[] = 'out of diskspace';
$Email__Full[] = 'over disk quota';
$Email__Full[] = 'over quota';
$Email__Full[] = 'over the allowed quota';
$Email__Full[] = 'problem with the recipient\'s mailbox';
$Email__Full[] = 'quota exceeded';
$Email__Full[] = 'quota violation';
$Email__Full[] = 'space has been used up';
$Email__Full[] = 'space not enough';
$Email__Full[] = 'status: 5.2.1';
$Email__Full[] = 'status: 5.2.2';
$Email__Full[] = 'status: 5.2.3';
$Email__Full[] = 'status: 5.3.3';

$Email__NotExist[] = '/var/mail/nobody';
$Email__NotExist[] = '550 5.1.1';
$Email__NotExist[] = 'account expired';
$Email__NotExist[] = 'account inactive';
$Email__NotExist[] = 'account suspended';
$Email__NotExist[] = 'address is administratively disabled';
$Email__NotExist[] = 'address is not recognized';
$Email__NotExist[] = 'address is rejected';
$Email__NotExist[] = 'address not recognized';
$Email__NotExist[] = 'address rejected';
$Email__NotExist[] = 'bad destination email address';
$Email__NotExist[] = 'cname lookup failed';
$Email__NotExist[] = 'connection refused';
$Email__NotExist[] = 'couldn\'t find any host';
$Email__NotExist[] = 'could not be found';
$Email__NotExist[] = 'deactivated mailbox';
$Email__NotExist[] = 'delivery time expired';
$Email__NotExist[] = 'destination server not responding';
$Email__NotExist[] = 'disabled or discontinued';
$Email__NotExist[] = 'does not exist';
$Email__NotExist[] = 'does not like recipient';
$Email__NotExist[] = 'doesn\'t have a yahoo.com account';
$Email__NotExist[] = 'doesn\'t have a yahoo.com.sg account';
$Email__NotExist[] = 'domain is for sale';
$Email__NotExist[] = 'find a mail exchanger';
$Email__NotExist[] = 'find any host named';
$Email__NotExist[] = 'following address(es) failed';
$Email__NotExist[] = 'host unknown';
$Email__NotExist[] = 'i couldn\'t find any host by that name';
$Email__NotExist[] = 'illegal user';
$Email__NotExist[] = 'in the queue too long';
$Email__NotExist[] = 'inactive recipient';
$Email__NotExist[] = 'inactive user';
$Email__NotExist[] = 'incorrectly addressed';
$Email__NotExist[] = 'invalid recipient';
$Email__NotExist[] = 'invalid user';
$Email__NotExist[] = 'isn\'t in my control/locals file';
$Email__NotExist[] = 'mailbox not available';
$Email__NotExist[] = 'mailbox not found';
$Email__NotExist[] = 'mailbox unavailable';
$Email__NotExist[] = 'mail is looping';
$Email__NotExist[] = 'message is looping';
$Email__NotExist[] = 'name is not recognized';
$Email__NotExist[] = 'name not found';
$Email__NotExist[] = 'name not recognized';
$Email__NotExist[] = 'no local mailbox';
$Email__NotExist[] = 'no longer accepts mail';
$Email__NotExist[] = 'no longer an employee';
$Email__NotExist[] = 'no longer on server';
$Email__NotExist[] = 'no longer valid';
$Email__NotExist[] = 'no mailbox';
$Email__NotExist[] = 'no route found to domain';
$Email__NotExist[] = 'no such user';
$Email__NotExist[] = 'none of the mail servers for the destination domain has so far responded';
$Email__NotExist[] = 'no valid host';
$Email__NotExist[] = 'no valid recipients';
$Email__NotExist[] = 'not a valid mailbox';
$Email__NotExist[] = 'not listed';
$Email__NotExist[] = 'not listed in domino';
$Email__NotExist[] = 'possible mail loop';
$Email__NotExist[] = 'recipient cannot be verified';
$Email__NotExist[] = 'recipient unknown';
$Email__NotExist[] = 'recipients are invalid';
$Email__NotExist[] = 'recipnotfound';
$Email__NotExist[] = 'relaying denied';
$Email__NotExist[] = 'several matches found in domino';
$Email__NotExist[] = 'status: 5.1.1';
$Email__NotExist[] = 'status: 5.1.3';
$Email__NotExist[] = 'status: 5.1.4';
$Email__NotExist[] = 'status: 5.1.6';
$Email__NotExist[] = 'status: 5.1.7';
$Email__NotExist[] = 'this user doesn\'t have a yahoo';
$Email__NotExist[] = 'too many hops';
$Email__NotExist[] = 'unable to deliver';
$Email__NotExist[] = 'unable to relay';
$Email__NotExist[] = 'unknown address';
$Email__NotExist[] = 'unknown recipient';
$Email__NotExist[] = 'unknown user';
$Email__NotExist[] = 'unrouteable address';
$Email__NotExist[] = 'user doesn\'t have';
$Email__NotExist[] = 'user unknown';
$Email__NotExist[] = 'x-notes; 550 5.1.1';
$Email__NotExist[] = 'x-notes; recipient\'s domino directory';
$Email__NotExist[] = '$B%G%#%l%/%H%j$K$O8+$D$+$j$^$;$s!#'; //* Returned from japanese domino . Somehow means directory is not found.

$Email__Banned[] = '_spam_';
$Email__Banned[] = '550 5.7.1';
$Email__Banned[] = '550 access denied';
$Email__Banned[] = '550 no thanks';
$Email__Banned[] = '550 spam';
$Email__Banned[] = '554 5.7.0';
$Email__Banned[] = '554 5.7.1';
$Email__Banned[] = '554 denied';
$Email__Banned[] = '554 message does not conform to standards';
$Email__Banned[] = '554 message refused';
$Email__Banned[] = '571 message Refused';
$Email__Banned[] = 'activated my anti-spam features';
$Email__Banned[] = 'administrative prohibition';
$Email__Banned[] = 'appears to contain uce/spam';
$Email__Banned[] = 'appears to be spam';
$Email__Banned[] = 'appears to be unsolicited';
$Email__Banned[] = 'banned for spamming';
$Email__Banned[] = 'blackholed by uribl.com';
$Email__Banned[] = 'blacklisted by surbl';
$Email__Banned[] = 'blocked by filter';
$Email__Banned[] = 'blocked by kbas system';
$Email__Banned[] = 'blocked by our content filter';
$Email__Banned[] = 'blocked by spamsssassin';
$Email__Banned[] = 'blocked by the recipient';
$Email__Banned[] = 'blocked by user\'s personal blacklist';
$Email__Banned[] = 'blocked due to spam like qualities';
$Email__Banned[] = 'blocked using spam pattern';
$Email__Banned[] = 'blocked using uceprotect';
$Email__Banned[] = 'body part contains disallowed string';
$Email__Banned[] = 'classified as **spam**';
$Email__Banned[] = 'content blacklist';
$Email__Banned[] = 'content filter rejected the message';
$Email__Banned[] = 'consider the message to be spam';
$Email__Banned[] = 'considered spam';
$Email__Banned[] = 'contains spam';
$Email__Banned[] = 'content filter rejection';
$Email__Banned[] = 'content rejected';
$Email__Banned[] = 'denied by policy';
$Email__Banned[] = 'detected your message as spam';
$Email__Banned[] = 'does not accept UCE';
$Email__Banned[] = 'domain is banned';
$Email__Banned[] = 'email abuse detected';
$Email__Banned[] = 'error 553';
$Email__Banned[] = 'help_spam_16.htm';
$Email__Banned[] = 'high on spam scale';
$Email__Banned[] = 'http://www.google.com/mail/help/bulk_mail.html';
$Email__Banned[] = 'http://www.surbl.org/lists.html';
$Email__Banned[] = 'identified as spam';
$Email__Banned[] = 'identified your message as spam';
$Email__Banned[] = 'listed in multi.surbl.org';
$Email__Banned[] = 'looks like spam';
$Email__Banned[] = 'mail rejected by windows live hotmail for policy reasons';
$Email__Banned[] = 'message bounced by administrator';
$Email__Banned[] = 'message content rejected, ube';
$Email__Banned[] = 'message contains a virus or other harmful content';
$Email__Banned[] = 'message has too high spam probability';
$Email__Banned[] = 'message is blacklisted';
$Email__Banned[] = 'message refused';
$Email__Banned[] = 'no spam here';
$Email__Banned[] = 'not accepted here';
$Email__Banned[] = 'not in the whitelist';
$Email__Banned[] = 'not rfc compliant';
$Email__Banned[] = 'permanently rejected message';
$Email__Banned[] = 'policy violation';
$Email__Banned[] = 'refused mail service';
$Email__Banned[] = 'reject spam mail';
$Email__Banned[] = 'reject the mail';
$Email__Banned[] = 'rejected by filter';
$Email__Banned[] = 'rejected as spam';
$Email__Banned[] = 'rejected by 35 antiSpam system';
$Email__Banned[] = 'rejected by antispam system';
$Email__Banned[] = 'rejected by cloudmark anti-spam';
$Email__Banned[] = 'rejected by our Spam Filter';
$Email__Banned[] = 'rejected by spam filtering';
$Email__Banned[] = 'rejected by surbl';
$Email__Banned[] = 'rejected by the anti-spam system';
$Email__Banned[] = 'rejected due to security policies';
$Email__Banned[] = 'rejected for policy reasons';
$Email__Banned[] = 'rejected for spam';
$Email__Banned[] = 'requires that you verify';
$Email__Banned[] = 'scored as spam';
$Email__Banned[] = 'sender address verification';
$Email__Banned[] = 'sender was rejected';
$Email__Banned[] = 'spam detected by spamassassin';
$Email__Banned[] = 'spam filter pattern';
$Email__Banned[] = 'spam-like characteristics';
$Email__Banned[] = 'spam mail detected';
$Email__Banned[] = 'spam mail refused';
$Email__Banned[] = 'spam message was blocked';
$Email__Banned[] = 'spam rejected';
$Email__Banned[] = 'spam score too high';
$Email__Banned[] = 'status: 5.7.1';
$Email__Banned[] = 'support.proofpoint.com';
$Email__Banned[] = 'suspected spam';
$Email__Banned[] = 'suspicious url in message body';
$Email__Banned[] = 'temporarily deferred';
$Email__Banned[] = 'transaction failed';
$Email__Banned[] = 'unacceptable content';
$Email__Banned[] = 'unacceptable mail content';
$Email__Banned[] = 'unsolicited bulk e-mail';
$Email__Banned[] = 'unsolicited bulk email';
$Email__Banned[] = 'unsolicited email is refused';
$Email__Banned[] = 'validate recipient email';
$Email__Banned[] = 'will be deleted from queue';

$Email__OutOffice[] = 'away for a vacation';
$Email__OutOffice[] = 'away from the office';
$Email__OutOffice[] = 'not in office';
$Email__OutOffice[] = 'on leave';
$Email__OutOffice[] = 'on vacation';
$Email__OutOffice[] = 'out of office';
$Email__OutOffice[] = 'out of the office';

回答by encodes

its easier than you think to write this yourself.

自己写这个比你想象的要容易。

You simply set the bounce back path in the headers. Then set up that email address to run a processing script. you obviously would need to send some form of user id.

您只需在标题中设置反弹路径。然后设置该电子邮件地址以运行处理脚本。您显然需要发送某种形式的用户 ID。

I have used PHPList before and find it fine, there are better services to do what you need but obviously there is a cost for them.

我之前使用过 PHPList 并发现它很好，有更好的服务可以满足您的需求，但显然它们需要付出代价。

Bounces occur when the address doesn't exists or the mail server sends it back. Some mail servers will not reply (as a security feature) so accuracy won't be the best.

当地址不存在或邮件服务器将其发回时，就会发生退回。某些邮件服务器不会回复（作为安全功能），因此准确性不会是最好的。

A lot of the standalone/libraries offer extra features working out which links were clicked and by who working out who read the email. etc

许多独立/库提供了额外的功能，以确定点击了哪些链接以及由谁来计算谁阅读了电子邮件。等等

these things are easy to achieve but take resources.

这些事情很容易实现，但需要资源。

Let me know if there is anything else you need help with

如果还有什么需要帮助的，请告诉我

回答by neokio

After finding no simple answers to this question, I found this excellent solution on github:

在找不到这个问题的简单答案后，我在 github 上找到了这个优秀的解决方案：

https://github.com/cfortune/PHP-Bounce-Handler

https://github.com/cfortune/PHP-Bounce-Handler

回答by preinheimer

I'm a large fan of the ezComponents library, which includes a Mail component which can handle both sending, and parsing mail (as well as connecting to your MTA to retrieve it. http://ezcomponents.org/docs/tutorials/Mail#mail-parsers

我是ezComponents库，其中包括邮件组件，它可以同时处理发送和邮件解析（以及连接到您的MTA找回它的大风扇。 http://ezcomponents.org/docs/tutorials/Mail #邮件解析器

Reading through the docs, it seems like it should be up to your task.

通读文档，似乎这应该取决于您的任务。

回答by siteinteractive

Being a 15 year veteran of online communities, I know that answering a question with a for-profit commercial solution, which the one responding is affiliated with, is walking a fine line. So here I go, walking that line. I'll do my best to address the question specifically. Let's start with a standard disclaimer...

作为在线社区 15 年的资深人士，我知道使用营利性商业解决方案回答问题（回答者所属的解决方案）是在走细线。所以我走了，走那条线。我会尽力具体解决这个问题。让我们从标准的免责声明开始……

DISCLAIMER: I am a principle in the service described below.

免责声明：我是下面描述的服务的原则。

but investing the resources in writing our own library to parse the bounced e-mails is very undesirable.

但是投入资源编写我们自己的库来解析退回的电子邮件是非常不可取的。

Yes, writing your own libraries is no fun for most (but us poor, twisted souls with nothing better to do), considering that the library you write or include may be considered out-dated within days of your modifications.

是的，考虑到您编写或包含的库在您修改后的几天内可能会被视为过时，因此编写自己的库对大多数人来说并不有趣（但我们这些可怜、扭曲的灵魂却无事可做）。

Does anyone know of an up-to-date set of rules for processing bounced e-mails? I don't necessarily need any handling logic, even just an up-to-date ruleset would be satisfactory.

有谁知道处理退回电子邮件的最新规则集？我不一定需要任何处理逻辑，即使只是最新的规则集也会令人满意。

Maintaining such libraries are significantly time consuming, and once it becomes significantly time consuming such libraries are often either abandoned or sparsely updated. This is usually how commercial solutions are born.

维护这样的库非常耗时，并且一旦变得非常耗时，这些库通常要么被放弃要么很少更新。这通常是商业解决方案的诞生方式。

I'm a big fan of Open Source, and there is no doubt that I've personally benefitted greatly from it over the years. For the great majority of you reading this, the above options are perfectly sufficient, as many of you are capable of developing the solutions you need yourselves or modify the available tools to suit your needs, and have the time to do so.

我是开源的忠实粉丝，毫无疑问，多年来我个人从中受益匪浅。对于大多数阅读本文的人来说，上述选项已经足够了，因为你们中的许多人能够开发自己需要的解决方案或修改可用工具以满足您的需求，并且有时间这样做。

For those of you, however, that do not wish to build your own applications, debug and troubleshoot them, update the email processing definitions consistently and often, InboxResponse.com offers email bounce processingas an SAAS solution. It is:

但是，对于那些不希望构建自己的应用程序、对其进行调试和故障排除、一致且经常更新电子邮件处理定义的人，InboxResponse.com 提供电子邮件退回处理作为 SAAS 解决方案。这是：

• Updated often and consistently
• Perfect for those of you that just want something that works
• Can be integrated into any existing mailing systems you presently use, within minutes.
• Supports delivery tracking, bounce processing, multiple levels of soft-bounce processing (temporarily undeliverable emails), unlimited mailing lists, stats, graphs, and more.

• 经常和持续更新
• 非常适合那些只想要有用的东西的人
• 可以在几分钟内集成到您目前使用的任何现有邮件系统中。
• 支持投递跟踪、退回处理、多级软退回处理（暂时无法送达的电子邮件）、无限邮件列表、统计数据、图表等。

A free trial is available at the following URL: https://inboxresponse.com/free-trial/

以下 URL 提供免费试用：https: //inboxresponse.com/free-trial/

May not have been exactly what you were looking for (an Open Source library always kept up-to-date), but I don't think exactly what you are looking for is presently available.

可能不是您正在寻找的内容（一个始终保持最新状态的开源库），但我认为您正在寻找的内容目前尚不可用。

Hope that helps someone!

希望对某人有所帮助！