On 11 Dec 2017, at 10:41 (-0500), Alexander Burch wrote:
5.7.1 codes are used exclusively for policy blocks (IP blacklisted,
content
deemed spammy etc).
Gmail uses it for DMARC rejections.
Hotmail also uses 5.7.1 when an IP is outright blocked.
This type of bounce confuses me a little. It ce
Analyze the Diagnostic-Code text first, that is for sure. You can expect
anywhere between 1000 and 2000 regex rules to get to 99%+
effectiveness. (E)Smtp codes are bad for primary bounce
handling rules, they work fine as a backup.
I would state N is 3 or 4. But I would not remove the recipient fro
If you use a counter-based bounce processing system that eventually
invalidates repeatedly 5xx bouncing recipients, I wouldn't exclude 5.7.1
response codes from that process. If your sending client isn't actively
addressing the issue and working with you to get the block removed, then
continuing to
I would not say exclusively. Code 5.7.1 is also used for “Relay access denied”
for example. This bounce is often caused by typo domains that end up at a
default MX. From my experience, it is better to match a bounce category first
on the text, and then on the status code.
For the actions, I agr
5.7.1 codes are used exclusively for policy blocks (IP blacklisted, content
deemed spammy etc).
Gmail uses it for DMARC rejections.
Hotmail also uses 5.7.1 when an IP is outright blocked.
This type of bounce confuses me a little. It certainly shouldn't be used to
mark the recipient as invalid, a
