On Thu, 28 May 2009, David Nicol wrote:

On Wed, May 27, 2009 at 9:18 AM, David Favor <da...@davidfavor.com> wrote:

I host many domains and I'd like to protect them all
against backscatter

I wrote a plugin to create VERP variable envelope return path
addresses for each and every message passing through my forwarding
system, kept track of in a little database and expired after three
weeks.  Anything coming from <> that isn't to a recognized verp
address hits the floor.  Overkill? Doesn't require parsing possibly
not-included message headers.  Requires storage space to keep the VERP
table, essentially one line for each message for however long you want
the verp addresses to be good.

This is essentially BATV.

However beware that BATV does break some things:

- It will drop your outbound mails to ezmlm mailing lists into the moderation queue (unless you have some sort of "don't VERP mails to these addresses" function and remember all your mailing lists).

- It will "break" some remote whitelisting systems which look at the MAIL FROM to determine if your mail is in the whitelist.

- It will cause some greylisting systems to greylist every email you send.

Also, for BATV you need to make sure you have FULL and UTTER control of all your outbounds.

If you're willing to live with these issues then BATV works great.

Matt.

Reply via email to