I'm primarily a
User Developer Sysadmin A mixture Something else entirely .. ( 515 votes ~ 10 comments )
You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.
To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.
This is the comment you were replying to, attached to the weblog Suppressing backscatter bounces on secondaries
#3 Re: Suppressing backscatter bounces on secondaries Posted by lee (90.212.xx.xx) on Sun 20 Apr 2008 at 20:07 This entry is only concerned with preventing backscatter being generated on forwarders and secondaries. In terms of dealing with receipt of backscatter bounces, I do use an Exim-based filter, but at the user level. This just splits out bounces into boxes for later processing rather than having them hit my inbox. This takes all null-return addressed mail and filters it into one of three boxes. One for known backscatter based on the address used; one for mails that can be recognised as fairly standard bounces, and one for bounces with unrecognised properties. Also note, this doesn't catch backscatter from domains that don't use a null return path. I recommend just blacklisting domains that send bounces in this way. ## handle bounces if $return_path is "" then if $h_To: contains "address.no.mail.is.sent.from@example.com" or $h_To: contains "other.unused.address@example.com" then save bounce-forged/ else if $h_Content-Type: contains "delivery-status" or $h_Subject: contains "failure notice" or $h_Subject: contains "Mail delivery failed:" or $h_Subject: contains "Mail System Error - Returned Mail" or $h_Subject: contains "Undeliverable" or $h_Subject: contains "Returned mail: Service unavailable" then save bounce/ else save bounce-unknown/ endif endif finish endif
This entry is only concerned with preventing backscatter being generated on forwarders and secondaries.
In terms of dealing with receipt of backscatter bounces, I do use an Exim-based filter, but at the user level. This just splits out bounces into boxes for later processing rather than having them hit my inbox.
This takes all null-return addressed mail and filters it into one of three boxes. One for known backscatter based on the address used; one for mails that can be recognised as fairly standard bounces, and one for bounces with unrecognised properties.
Also note, this doesn't catch backscatter from domains that don't use a null return path. I recommend just blacklisting domains that send bounces in this way.
## handle bounces if $return_path is "" then if $h_To: contains "address.no.mail.is.sent.from@example.com" or $h_To: contains "other.unused.address@example.com" then save bounce-forged/ else if $h_Content-Type: contains "delivery-status" or $h_Subject: contains "failure notice" or $h_Subject: contains "Mail delivery failed:" or $h_Subject: contains "Mail System Error - Returned Mail" or $h_Subject: contains "Undeliverable" or $h_Subject: contains "Returned mail: Service unavailable" then save bounce/ else save bounce-unknown/ endif endif finish endif
Posting Format:
Inappropriate comments will be removed.
Some help on entry formatting is available
Username:
Password:
[ Advanced Login ]
Register Account
