退回电子邮件中的标头变量：如果删除或不删除，哪些点会产生影响？
我们使用 BounceStudio 来分析时事通讯系统的退回电子邮件。标题的添加方式如下：
// Namespace System.Net.Mail
MailMessage mail = new MailMessage();
mail.Headers.Add("X-BPS1", UserId);
// etc.
smptClient.Send(mail);
到目前为止一切顺利。有趣的是，很多退回的电子邮件不包含我们添加的标头。我无法弄清楚是否保留标头可能取决于什么？我所做的一个有趣的观察是，它似乎取决于使用哪个发件人地址（尽管它们是使用相同的 smtp 发送的）。从来自地址 AI 的新闻通讯 A 接收到大部分标头变量（大约 90%，我猜这很好），从带有来自地址 B 的新闻通讯 B（当然还有其他接收者）我只收到大约 20% 的标头变量，另外 80% 的退回邮件不包含标头信息。所有邮件都是 html 邮件，技术上是相同的。
留下的问题是什么会影响退回邮件中的标头？有人知道有关该主题的详细信息或良好来源吗？ 或者说如何更好地设计系统？
我是否正确，最好的方法可能仍然是将信息隐藏在发件人或返回路径电子邮件地址中，然后从那里解析出来？但这将包括使用通配符或类似的配置 smtp，在那里没有太多知识。
感谢您的任何提示 SL3DG3
We use BounceStudio in order to analyze the bounced emails for a newsletter-system. The headers are added like this:
// Namespace System.Net.Mail
MailMessage mail = new MailMessage();
mail.Headers.Add("X-BPS1", UserId);
// etc.
smptClient.Send(mail);
So far so good. The interesting thing is that a lot of the bounced emails don't include the headers we added. I couldn't figure out on what that could depend if the headers are preserved or not? One interesting observation I made is the fact that it seems to depend on which from-address is used (they are sent with the same smtp though). From newsletter A with from-address A I receive most header variables (about 90%, which is good I guess), from newsletter B with from-address B (and other receivers of course) I only receive about 20% of the header variables, the other 80% of the bounced mails don't include the header-information. All mails are html-mails and technically the same.
Leaves the question what could influence the headers within the bounced mails? Does somebody know details or good sources about that subject?
Or how could I design the system better?
Am I right that the best way might still be hiding the information within the from- or return-path email-adress and then parse it out from there? But this would include configuring the smtp with wildcards or similar, don't have much knowledge there.
Thx for any tipps
sl3dg3
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果远程 MTA 产生反弹，您将受到其摆布。毫不奇怪，Windows MTA 在这方面似乎特别俗气。标准解决方案是 VERP，即每个收件人的唯一信封发件人地址（以及返回路径：）。
If the remote MTA generates the bounce, you are at its mercy. Unsurprisingly, Windows MTAs seem to be particularly tacky in this regard. The standard solution is VERP, i.e. a unique envelope sender address (and hence Return-Path:) for each recipient.