refer:http://help.sign-up.to/index.php/Email_Bounce_Code_Explanations
Sign-Up.to interpret email bounce codes in accordance with the RFC 3463
- Enhanced Mail System Status Codes Memo. While most email servers
follow the same guidelines, some do differ, so explanations provided in
this document and within Sign-Up.to applications should be considered
an indication rather than an absolute truth.
Some email servers also send a brief explanation of the area
along with the error code. Where this occurs, Sign-Up.to will show this
additional information in the application. Due to the difference in
interpretation of the guidelines, this addition information may not
always agree with this documentation.
Bounce Codes
Codes are formed of three digits separated by periods. In the case
of bounce errors, the first digit of these codes is either a 4 or a 5.
A four typically means a persistent but not necessarily permanent
error, where 5 is usually a permanent error. In the explanations below,
Sign-Up.to treat errors beginning with 4 as soft, 5 as hard except
where stated otherwise.
4.0.0 / 5.0.0
Undefined persistent error. Unfortunately some systems only
issue general warnings such as this. As these error messages are vague,
we treat them as soft bounces.
4.1.x / 5.1.x
Destination address error, usually caused by a bad address.
4.2.x / 5.2.x
Destination mailbox error, usually caused by a quota limit or
other rule/error on the recipient’s server. Sign-Up.to treat all these
errors as soft bounces.
4.3.x / 5.3.x
Destination mail system error or misconfiguration.
4.4.x / 5.4.x
Networking issues with intermediate or destination mail server.
4.5.x / 5.5.x
Mail delivery protocol status. This can be caused by any
number of factors, from delivery mail server protocol errors to
intermediate network issues or delays.
4.6.x / 5.6.x
Unsupported media or message content error.
4.7.x / 5.7.x
Security or policy status has triggered an error. It’s
possible that an aggressive anti-SPAM policy or undesirable previous
content has caused the system to reject mail. Sign-Up.to treat these as
hard bounces so as not to further aggravate the destination mail
server.
Acknowledgements:
RFC3463 - http://www.faqs.org/rfcs/rfc3463.html
分享到:
相关推荐
资源内包含从官方提取的 Bounce Tales 游戏原版文件(.jar 格式 及 .jad 格式都有)以及基于原版的汉化版,附带有安卓模拟器,借助安卓模拟器可在安卓手机上进行玩耍
Bounce+Tales中文版.jar
Jangly Bounce
资源来自pypi官网。 资源全名:bounce_email-0.0.2.tar.gz
诺基亚手机游戏,《Bounce Tales》是一款由诺基亚公司开发的游戏,大部分按键式诺基亚手机在“应用软件”中的“游戏”文件夹里会有。其中,普通游戏共12关,奖励游戏共3关。
BOUNCE
Bounce+Tales.jar
用Arduino设计电子产品时,该库文件可以很好地帮助设计一个“完美”的按键,通过调用各个函数,就可以实现按键的各种处理,包括按键的消抖处理,延时和响应
Bounce.js是一款功能非常强大的可视化CSS3动画代码生成js库插件。该js库插件提供了一个在线APP,通过该APP可以在可视化的条件下编辑CSS3的各种动画效果。此外,你也可以单独使用Bounce.js,通过js代码来完成各种CSS3...
Bounce是一个用于游戏和互动应用的3D物理引擎
bouncetales蹦球传说特色: 1、这里的关卡还是非常多样的,还有一些隐藏的内容供大家发现哦。 2、有着非常精美的画面,游戏的内容也是非常的丰富的,玩起来也还算是有趣。 3、你可以与游戏中的小红球一起冒险,享受...
JavaScript
书中的弹射小球的JAVA源程序。实现比较简单
JavaScript
bounce effects creating smooth graph
radial_bounce028
parse_email ( emlDataString ) ;关于 PHP-Bounce-Handler 此类可用于解析退回邮件报告。 它解析具有根据 RFC 1892 和 1894 文档格式化的多部分报告内容类型的电子邮件消息。 如果反弹没有很好地形成,它也会尝试...
本示例说明如何使用Simulink?的两种不同方法对弹跳球进行建模。
弹跳2 Thomas Ouellet Fredericks的Arduino防弹跳库和接线,来自社区的许多贡献: : ...通过软件的库管理器进行安装或在下载最新版本然后将“ Bounce2”文件夹放在“库”文件夹中。 请注意,该库的原始
lotus_bounce_DoS