mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-16 22:42:21 +08:00
Merge pull request #14897 from wxy/20181222-How-to-detect-automatically-generated-emails
TSL&PRF:20181222 How to detect automatically generated emails
This commit is contained in:
Xingyu.Wang
GitHub
commit
a12f3135e3
@ -1,144 +0,0 @@
|
|||||||
[#]: collector: (lujun9972)
|
|
||||||
[#]: translator: (wxy)
|
|
||||||
[#]: reviewer: ( )
|
|
||||||
[#]: publisher: ( )
|
|
||||||
[#]: url: ( )
|
|
||||||
[#]: subject: (How to detect automatically generated emails)
|
|
||||||
[#]: via: (https://arp242.net/weblog/autoreply.html)
|
|
||||||
[#]: author: (Martin Tournoij https://arp242.net/)
|
|
||||||
|
|
||||||
How to detect automatically generated emails
|
|
||||||
======
|
|
||||||
|
|
||||||
### How to detect automatically generated emails
|
|
||||||
|
|
||||||
|
|
||||||
When you send out an auto-reply from an email system you want to take care to not send replies to automatically generated emails. At best, you will get a useless delivery failure. At words, you will get an infinite email loop and a world of chaos.
|
|
||||||
|
|
||||||
Turns out that reliably detecting automatically generated emails is not always easy. Here are my observations based on writing a detector for this and scanning about 100,000 emails with it (extensive personal archive and company archive).
|
|
||||||
|
|
||||||
### Auto-submitted header
|
|
||||||
|
|
||||||
Defined in [RFC 3834][1].
|
|
||||||
|
|
||||||
This is the ‘official’ standard way to indicate your message is an auto-reply. You should **not** send a reply if `Auto-Submitted` is present and has a value other than `no`.
|
|
||||||
|
|
||||||
### X-Auto-Response-Suppress header
|
|
||||||
|
|
||||||
Defined [by Microsoft][2]
|
|
||||||
|
|
||||||
This header is used by Microsoft Exchange, Outlook, and perhaps some other products. Many newsletters and such also set this. You should **not** send a reply if `X-Auto-Response-Suppress` contains `DR` (“Suppress delivery reports”), `AutoReply` (“Suppress auto-reply messages other than OOF notifications”), or `All`.
|
|
||||||
|
|
||||||
### List-Id and List-Unsubscribe headers
|
|
||||||
|
|
||||||
Defined in [RFC 2919][3]
|
|
||||||
|
|
||||||
You usually don’t want to send auto-replies to mailing lists or news letters. Pretty much all mail lists and most newsletters set at least one of these headers. You should **not** send a reply if either of these headers is present. The value is unimportant.
|
|
||||||
|
|
||||||
### Feedback-ID header
|
|
||||||
|
|
||||||
Defined [by Google][4].
|
|
||||||
|
|
||||||
Gmail uses this header to identify mail newsletters, and uses it to generate statistics/reports for owners of those newsletters. You should **not** send a reply if this headers is present; the value is unimportant.
|
|
||||||
|
|
||||||
### Non-standard ways
|
|
||||||
|
|
||||||
The above methods are well-defined and clear (even though some are non-standard). Unfortunately some email systems do not use any of them :-( Here are some additional measures.
|
|
||||||
|
|
||||||
#### Precedence header
|
|
||||||
|
|
||||||
Not really defined anywhere, mentioned in [RFC 2076][5] where its use is discouraged (but this header is commonly encountered).
|
|
||||||
|
|
||||||
Note that checking for the existence of this field is not recommended, as some ails use `normal` and some other (obscure) values (this is not very common though).
|
|
||||||
|
|
||||||
My recommendation is to **not** send a reply if the value case-insensitively matches `bulk`, `auto_reply`, or `list`.
|
|
||||||
|
|
||||||
#### Other obscure headers
|
|
||||||
|
|
||||||
A collection of other (somewhat obscure) headers I’ve encountered. I would recommend **not** sending an auto-reply if one of these is set. Most mails also set one of the above headers, but some don’t (but it’s not very common).
|
|
||||||
|
|
||||||
* `X-MSFBL`; can’t really find a definition (Microsoft header?), but I only have auto-generated mails with this header.
|
|
||||||
|
|
||||||
* `X-Loop`; not really defined anywhere, and somewhat rare, but sometimes it’s set. It’s most often set to the address that should not get emails, but `X-Loop: yes` is also encountered.
|
|
||||||
|
|
||||||
* `X-Autoreply`; fairly rare, and always seems to have a value of `yes`.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
#### Email address
|
|
||||||
|
|
||||||
Check if the `From` or `Reply-To` headers contains `noreply`, `no-reply`, or `no_reply` (regex: `^no.?reply@`).
|
|
||||||
|
|
||||||
#### HTML only
|
|
||||||
|
|
||||||
If an email only has a HTML part, but no text part it’s a good indication this is an auto-generated mail or newsletter. Pretty much all mail clients also set a text part.
|
|
||||||
|
|
||||||
#### Delivery failures
|
|
||||||
|
|
||||||
Many delivery failure messages don’t really indicate that they’re failures. Some ways to check this:
|
|
||||||
|
|
||||||
* `From` contains `mailer-daemon` or `Mail Delivery Subsystem`
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Many mail libraries leave some sort of footprint, and most regular mail clients override this with their own data. Checking for this seems to work fairly well.
|
|
||||||
|
|
||||||
* `X-Mailer: Microsoft CDO for Windows 2000` – Set by some MS software; I can only find it on autogenerated mails. Yes, it’s still used in 2015.
|
|
||||||
|
|
||||||
* `Message-ID` header contains `.JavaMail.` – I’ve found a few (5 on 50k) regular messages with this, but not many; the vast majority (thousends) of messages are news-letters, order confirmations, etc.
|
|
||||||
|
|
||||||
* `^X-Mailer` starts with `PHP`. This should catch both `X-Mailer: PHP/5.5.0` and `X-Mailer: PHPmailer blah blah`. The same as `JavaMail` applies.
|
|
||||||
|
|
||||||
* `X-Library` presence; only [Indy][6] seems to set this.
|
|
||||||
|
|
||||||
* `X-Mailer` starts with `wdcollect`. Set by some Plesk mails.
|
|
||||||
|
|
||||||
* `X-Mailer` starts with `MIME-tools`.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Final precaution: limit the number of replies
|
|
||||||
|
|
||||||
Even when following all of the above advice, you may still encounter an email program that will slip through. This can very dangerous, as email systems that simply `IF email THEN send_email` have the potential to cause infinite email loops.
|
|
||||||
|
|
||||||
For this reason, I recommend keeping track of which emails you’ve sent an autoreply to and rate limiting this to at most n emails in n minutes. This will break the back-and-forth chain.
|
|
||||||
|
|
||||||
We use one email per five minutes, but something less strict will probably also work well.
|
|
||||||
|
|
||||||
### What you need to set on your auto-response
|
|
||||||
|
|
||||||
The specifics for this will vary depending on what sort of mails you’re sending. This is what we use for auto-reply mails:
|
|
||||||
|
|
||||||
```
|
|
||||||
Auto-Submitted: auto-replied
|
|
||||||
X-Auto-Response-Suppress: All
|
|
||||||
Precedence: auto_reply
|
|
||||||
```
|
|
||||||
|
|
||||||
### Feedback
|
|
||||||
|
|
||||||
You can mail me at [martin@arp242.net][7] or [create a GitHub issue][8] for feedback, questions, etc.
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
via: https://arp242.net/weblog/autoreply.html
|
|
||||||
|
|
||||||
作者：[Martin Tournoij][a]
|
|
||||||
选题：[lujun9972][b]
|
|
||||||
译者：[译者ID](https://github.com/译者ID)
|
|
||||||
校对：[校对者ID](https://github.com/校对者ID)
|
|
||||||
|
|
||||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
|
||||||
|
|
||||||
[a]: https://arp242.net/
|
|
||||||
[b]: https://github.com/lujun9972
|
|
||||||
[1]: http://tools.ietf.org/html/rfc3834
|
|
||||||
[2]: https://msdn.microsoft.com/en-us/library/ee219609(v=EXCHG.80).aspx
|
|
||||||
[3]: https://tools.ietf.org/html/rfc2919)
|
|
||||||
[4]: https://support.google.com/mail/answer/6254652?hl=en
|
|
||||||
[5]: http://www.faqs.org/rfcs/rfc2076.html
|
|
||||||
[6]: http://www.indyproject.org/index.en.aspx
|
|
||||||
[7]: mailto:martin@arp242.net
|
|
||||||
[8]: https://github.com/Carpetsmoker/arp242.net/issues/new
|
|
||||||
@ -0,0 +1,128 @@
|
|||||||
|
[#]: collector: (lujun9972)
|
||||||
|
[#]: translator: (wxy)
|
||||||
|
[#]: reviewer: (wxy)
|
||||||
|
[#]: publisher: ( )
|
||||||
|
[#]: url: ( )
|
||||||
|
[#]: subject: (How to detect automatically generated emails)
|
||||||
|
[#]: via: (https://arp242.net/weblog/autoreply.html)
|
||||||
|
[#]: author: (Martin Tournoij https://arp242.net/)
|
||||||
|
|
||||||
|
如何检测自动生成的电子邮件
|
||||||
|
======
|
||||||
|
|
||||||
|
当你用电子邮件系统发送自动回复时，你需要注意不要向自动生成的电子邮件发送回复。最好的情况下，你将获得无用的投递失败消息。更可能的是，你会得到一个无限的电子邮件循环和一个混乱的世界。
|
||||||
|
|
||||||
|
事实证明，可靠地检测自动生成的电子邮件并不总是那么容易。以下是基于为此编写的检测器并使用它扫描大约 100,000 封电子邮件（大量的个人存档和公司存档）的观察结果。
|
||||||
|
|
||||||
|
### Auto-submitted 信头
|
||||||
|
|
||||||
|
由 [RFC 3834][1] 定义。
|
||||||
|
|
||||||
|
这是表示你的邮件是自动回复的“官方”标准。如果存在 `Auto-Submitted` 信头，并且其值不是 `no`，你应该**不**发送回复。
|
||||||
|
|
||||||
|
### X-Auto-Response-Suppress 信头
|
||||||
|
|
||||||
|
[由微软][2]定义。
|
||||||
|
|
||||||
|
此信头由微软 Exchange、Outlook 和其他一些产品使用。许多新闻订阅等都设定了这个。如果 `X-Auto-Response-Suppress` 包含 `DR`（“抑制投递报告”）、`AutoReply`（“禁止 OOF 通知以外的自动回复消息”）或 `All`，你应该**不**发送回复。
|
||||||
|
|
||||||
|
### List-Id 和 List-Unsubscribe 信头
|
||||||
|
|
||||||
|
由 [RFC 2919][3] 定义。
|
||||||
|
|
||||||
|
你通常不希望给邮件列表或新闻订阅发送自动回复。几乎所有的邮件列表和大多数新闻订阅都至少设置了其中一个信头。如果存在这些信头中的任何一个，你应该**不**发送回复。这个信头的值不重要。
|
||||||
|
|
||||||
|
### Feedback-ID 信头
|
||||||
|
|
||||||
|
[由谷歌][4]定义。
|
||||||
|
|
||||||
|
Gmail 使用此信头识别邮件是否是新闻订阅，并使用它为这些新闻订阅的所有者生成统计信息或报告。如果此信头存在，你应该**不**发送回复。这个信头的值不重要。
|
||||||
|
|
||||||
|
### 非标准方式
|
||||||
|
|
||||||
|
上述方法定义明确（即使有些是非标准的）。不幸的是，有些电子邮件系统不使用它们中的任何一个 :-( 这里有一些额外的措施。
|
||||||
|
|
||||||
|
#### Precedence 信头
|
||||||
|
|
||||||
|
在 [RFC 2076][5] 中没有真正定义，不鼓励使用它（但通常会遇到此信头）。
|
||||||
|
|
||||||
|
请注意，不建议检查是否存在此信头，因为某些邮件使用 `normal` 和其他一些（少见的）值（尽管这不常见）。
|
||||||
|
|
||||||
|
我的建议是如果其值不区分大小写地匹配 `bulk`、`auto_reply` 或 `list`，则**不**发送回复。
|
||||||
|
|
||||||
|
#### 其他不常见的信头
|
||||||
|
|
||||||
|
这是我遇到的另外的一些（不常见的）信头。如果设置了其中一个，我建议**不**发送自动回复。大多数邮件也设置了上述信头之一，但有些没有（这并不常见）。
|
||||||
|
|
||||||
|
* `X-MSFBL`：无法真正找到定义（Microsoft 信头？），但我只有自动生成的邮件带有此信头。
|
||||||
|
* `X-Loop`：在任何地方都没有真正定义过，有点罕见，但有时有。它通常设置为不应该收到电子邮件的地址，但也会遇到 `X-Loop: yes`。
|
||||||
|
* `X-Autoreply`：相当罕见，并且似乎总是具有 `yes` 的值。
|
||||||
|
|
||||||
|
#### Email 地址
|
||||||
|
|
||||||
|
检查 `From` 或 `Reply-To` 信头是否包含 `noreply`、`no-reply` 或 `no_reply`（正则表达式：`^no.?reply@`）。
|
||||||
|
|
||||||
|
#### 只有 HTML 部分
|
||||||
|
|
||||||
|
如果电子邮件只有 HTML 部分，而没有文本部分，则表明这是一个自动生成的邮件或新闻订阅。几乎所有邮件客户端都设置了文本部分。
|
||||||
|
|
||||||
|
#### 投递失败消息
|
||||||
|
|
||||||
|
许多传递失败消息并不能真正表明它们是失败的。一些检查方法：
|
||||||
|
|
||||||
|
* `From` 包含 `mailer-daemon` 或 `Mail Delivery Subsystem`
|
||||||
|
|
||||||
|
#### 特定的邮件库特征
|
||||||
|
|
||||||
|
许多邮件类库留下了某种痕迹，大多数常规邮件客户端使用自己的数据覆盖它。检查这个似乎工作得相当可靠。
|
||||||
|
|
||||||
|
* `X-Mailer: Microsoft CDO for Windows 2000`：由某些微软软件设置；我只能在自动生成的邮件中找到它。是的，在 2015 年它仍然在使用。
|
||||||
|
* `Message-ID` 信头包含 `.JavaMail.`：我发现了一些（5 个 50k 大小的）常规消息，但不是很多；绝大多数（数千封）邮件是新闻订阅、订单确认等。
|
||||||
|
* `^X-Mailer` 以 `PHP` 开头。这应该会同时看到 `X-Mailer: PHP/5.5.0` 和 `X-Mailer: PHPmailer XXX XXX`。与 “JavaMail” 相同。
|
||||||
|
* 出现了 `X-Library`；似乎只有 [Indy][6] 设定了这个。
|
||||||
|
* `X-Mailer` 以 `wdcollect` 开头。由一些 Plesk 邮件设置。
|
||||||
|
* `X-Mailer` 以 `MIME-tools` 开头。
|
||||||
|
|
||||||
|
### 最后的预防措施：限制回复的数量
|
||||||
|
|
||||||
|
即使遵循上述所有建议，你仍可能会遇到一个避开所有这些检测的电子邮件程序。这可能非常危险，因为电子邮件系统只是“如果有电子邮件那么发送”，就有可能导致无限的电子邮件循环。
|
||||||
|
|
||||||
|
出于这个原因，我建议你记录你自动发送的电子邮件，并将此速率限制为在几分钟内最多几封电子邮件。这将打破循环链条。
|
||||||
|
|
||||||
|
我们使用每五分钟一封电子邮件的设置，但没这么严格的设置可能也会运作良好。
|
||||||
|
|
||||||
|
### 你需要为自动回复设置什么信头
|
||||||
|
|
||||||
|
具体细节取决于你发送的邮件类型。这是我们用于自动回复邮件的内容：
|
||||||
|
|
||||||
|
```
|
||||||
|
Auto-Submitted: auto-replied
|
||||||
|
X-Auto-Response-Suppress: All
|
||||||
|
Precedence: auto_reply
|
||||||
|
```
|
||||||
|
|
||||||
|
### 反馈
|
||||||
|
|
||||||
|
你可以发送电子邮件至 [martin@arp242.net][7] 或 [创建 GitHub 议题][8]以提交反馈、问题等。
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://arp242.net/weblog/autoreply.html
|
||||||
|
|
||||||
|
作者：[Martin Tournoij][a]
|
||||||
|
选题：[lujun9972][b]
|
||||||
|
译者：[wxy](https://github.com/wxy)
|
||||||
|
校对：[wxy](https://github.com/wxy)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: https://arp242.net/
|
||||||
|
[b]: https://github.com/lujun9972
|
||||||
|
[1]: http://tools.ietf.org/html/rfc3834
|
||||||
|
[2]: https://msdn.microsoft.com/en-us/library/ee219609(v=EXCHG.80).aspx
|
||||||
|
[3]: https://tools.ietf.org/html/rfc2919)
|
||||||
|
[4]: https://support.google.com/mail/answer/6254652?hl=en
|
||||||
|
[5]: http://www.faqs.org/rfcs/rfc2076.html
|
||||||
|
[6]: http://www.indyproject.org/index.en.aspx
|
||||||
|
[7]: mailto:martin@arp242.net
|
||||||
|
[8]: https://github.com/Carpetsmoker/arp242.net/issues/new
|
||||||
Loading…
Reference in New Issue
Block a user