blocks|key|1237859|text|这通常是通过将发送邮件的Return-Path头设置为每个收件人的唯一地址来实现的。例如，如果您有唯一的用户if来标识每个收件人，则可以使用bounce%2Buserid@example.com。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1237860|如果邮件被退回，你收到它并解析接收器(这将bounce%2Buserid@example.com)，然后你可以采取适当的行动。|1237861|使用%2B语法可以创建单个邮件用户(bounces@example.com)，该用户接收所有退回邮件，并仍然区分收件人。|1237862|entityMap^0|C|B|1Y|P|0|L|P|0|2|1|G|J|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|K|$]]

This is typically achieved by setting the <code>Return-Path</code> header of your outgoing Mail to a unique Address for every recipient. For example, you could use <code>bounce+userid@example.com</code> if you have a unique userid identifing every recipient.

If the Mail gets bounces, you recieve it and parse the reciever (which will <code>bounce+userid@example.com</code>), you can then take appropriate actions.

Using the <code>+</code> syntax makes it possible to create a single mail-user (<code>bounces@example.com</code>) which recieves all bounces and still distinguish between the recipients.

blocks|key|2459711|text|您不能依靠退回邮件的标头或正文来可靠地识别原始收件人，尤其是当您希望自动执行此过程时。即使您添加了自己的自定义标头，弹跳服务器在向您发回通知时也很可能会剥离这些标头。尝试解析邮件正文中的文本以提取收件人的电子邮件地址充其量也是不可靠的，因为没有标准的格式，而且每次退回邮件都是不同的。唯一一条在退回中保持完全不变的信息是返回路径电子邮件地址--您的服务器通告它想要退回到的地址。因此，自动化真正准确的退回捕获的唯一方法是将接收者直接编码到返回路径地址本身中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2459712|这通常是通过对每个收件人使用唯一的值覆盖服务器的默认返回路径地址来完成的，例如email+XXXXX+@yourdomain.com，其中XXXXX是收件人的电子邮件地址或其他内部标识符的某种编码和/或混淆表示。这项技术需要使用电子邮件服务器，它可以支持这种类型的通配符捕获所有地址，以便您不必为要发送到的每个电子邮件地址设置新的退回帐户。假设您只需将服务器配置为将所有此类your+*电子邮件转储到您的脚本中，该脚本只需解码XXXXX即可确定原始收件人是谁。|2459713|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You can not rely on either the headers or the body of the bounced message to be able to reliably identify the original recipient, especially if you want to automate the process. Even if you add your own custom headers, it's likely that the bouncing server will strip them when it sends notification back to you. And trying to parse text in the body of the message in order to pull out the recipient's email address can be dodgy at best, as there's no standard format and every bounce you get will be different. The only piece of information that will remain completely untouched in a bounce is the return path email address -- the address that your server advertises it wants bounces sent to. Thus, the only way to automate truly accurate bounce catching is to encode the recipient directly into the return path address itself.

This would typically be done by overriding your server's default return path address for each outgoing message, using a unique value per recipient, like bounce-XXXXX@yourdomain.com, where XXXXX is some encoded and/or obfuscated representation of the recipient's email address or some other internal identifier. This technique requires the use of an email server which can support this type of wild card catch-all address so that you don't have to set up a new bounce account for each email address you're sending to. Assuming that, you simply configure the server to dump all such bounce-* emails to your script, which needs only to decode the XXXXX in order to determine who the original recipient was.

blocks|key|2459715|text|如果您的工具要直接与收件人的SMTP服务器对话，可能更可取的做法是检查通过SMTP+protocol返回的4xx+(临时故障，例如“邮箱已满”)或5xx+(错误，例如“没有这样的用户”)响应的错误代码。由于反垃圾邮件/后向散射预防机制，您不应该依赖收件人的服务器在邮件未通过时回复未送达报告。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2459716|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol^0|11|D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If your tool is going to be talking directly to the recipients' SMTP servers, it 
might be more advisable to check the error codes returned via the <a href="http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol" rel="nofollow">SMTP protocol</a> for 
4xx (temporary failure, e.g. "mailbox full") or 5xx (error, e.g. "no such user") 
responses. Due to antispam/backscatter prevention mechanisms, you shouldn't rely on 
the recipient's server to reply with a non-delivery report whenever a message doesn't
go through.

I am working on a tool that will be sending bulk messages (not spam :) and I need to add a feature that will detect bounced messages. Is there a standard response associated with bounces? Would it be in the header of the body?

Detecting bounced messages

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正在开发一个工具，它将发送大量邮件(而不是垃圾邮件:)，我需要添加一个功能，将检测退回的邮件。是否有与退回相关的标准响应？它会在正文的标题中吗？

问检测退回邮件
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问检测退回邮件EN