[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: spamcop blacklisting servers for misdirected DSN messages
For what it's worth, I use a rather non elegant approach to handle this.
I have a scheduled job that finds "user doesn't exist" messages from
syslog, bounces those against known valid aliases, taking the truly bad
addresses and dynamically re-building the smtp-policy.spam file. The
bounce against valid aliasses allows me to remove bad addresses if the
alias has subsequently been made valid.
This doesn't prevent the first attempt to reach a bad address, but does
prevent subsequent ones, because zmailer will reject the message if
the "to address" is contained in the smtp-policy.spam file.
> So any ideas on this one? I have been a big fan of Spamcop
> up to this point and it would be ironic to be blacklisted by
> a service I use. If emails cannot be easily rejected at the
> smtp stage perhaps a tweak to the 'nosuchuser' error handling
> (possible just with an alteration in aliases.cf?) to have all
> misaddressed email only go to the postmaster, ie. suppress
> sender notification? This may only be workable with smaller
> domains. The postmaster can then either manually forward to
> the sender (or correct recipient) or delete and blacklist the
> %&^$@&% spammer.
> Daryle A. Tilroe
> To unsubscribe from this list: send the line "unsubscribe zmailer" in
> the body of a message to firstname.lastname@example.org
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to email@example.com