控制“不在办公室”的位置回复已发送
邮件服务器如何决定何时何地发送“不在办公室”类型的自动回复？
看来这取决于邮件服务器，因此有些会使用回复：地址，其他则使用发件人：也许还有发件人：地址。一些服务器（或全部？）似乎关心优先级：字段，并且根本不会在优先级：批量（或者可能优先级：列表？）上发送外出回复。返回路径似乎用于更严重类型的反弹，但也许它也被使用？
我想要实现的（这次）是最大限度地减少发送到 from: 地址的回复电子邮件的数量。我不介意把它们送到回复地址。
我一直在寻找某种参考或最佳实践 - 有任何参考或建议吗？我查看了一些相关的 RFC（RFC2822、RFC3834）但是我正在寻找事情的实际处理方式。
How do mail servers decide when and where to send "out of office"-type autoreplies?
It seems this is mail server dependent, so some will use a reply-to: address, others the From: and perhaps the Sender: address. Some servers (or all?) seem to care about the Precedence: field and will not send out of office replies at all on Precedence:bulk (or maybe precedence:list?). The return-path seems to be used for more severe types of bounces, but maybe it's used as well?
What I want is to achieve (this time) is to minimize the number of response e-mails that go to the from: address. I don't mind getting them at the reply-to address.
I've been looking for some sort of reference or best practices - any references or suggestions? I 've looked at some relevant RFCs (RFC2822, RFC3834) but I'm looking for how things are actually handled.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
以下是一些想法：
保护）
垃圾邮件、邮件列表……）。
auto-replied' 和 'Precedence:bulk' 标头
查看此示例，了解可能的标头和发件人模式来检测自动发件人：
https://github.com/gryphius/fuglu /blob/master/fuglu/src/fuglu/plugins/vacation.py
这个实现只发送到信封发件人地址(Return-Path)，在我看来，外出基本上和“您的邮件被推迟”错误，因此应转到退回邮件地址。但无论如何，我很少看到非批量的回复标题，
Here are a few thoughts:
protection)
spam, mailing lists, ...).
auto-replied' and 'Precedence: bulk' headers
have a look at this example to see possible header and senderpatterns to detect automated senders:
https://github.com/gryphius/fuglu/blob/master/fuglu/src/fuglu/plugins/vacation.py
This implementation only sends to the envelope sender address(Return-Path), In my opinion, out-of-office is basically the same as a "your message is deferred" error and should therefore go to the bounce address. But I rarely see Reply-To Headers in non-bulk anyway,