Handling Anti-Spam Systems When You Aren't Spamming?
"Many large ISPs are implementing anti-spam filters based on how many emails they receive from a single sender to many of their clients (thinking that if they get over five mails in a few seconds, they must be bulk-mail spammers, and therefore block the rest of them), but this is hurting the delivery of services like ours. Worse still is that there is typically no error message returned to us - the emails simply get dropped, much like a standard packet-filter firewall works. Then we have clients wondering why they didn't get their expected message.
Sometimes, ISPs will add us to their "white" lists (as opposed to "black" lists of known spammers), which fixes the problem, but only for that one ISP.
(I find it ironic that the email system was designed to be quite reliable, so that you could send a message and have reasonable confidence that it got to its intended recipient, and yet we're now moving away from this in the effort to fight spam.)
Now I know we don't want to tell spammers how they can get around the anti-spam filters, but I'm wondering how have others fought the anti-spam problem with their mailing lists?"
I'm one of the SpamAssassin developers and I find their technique odd.
;-)
Wouldn't this have a horrendously high false positive ratio for things like mailing lists?
Anyway, tell them to use SpamAssassin - it kicks ass. And I'm not biased, honest
Matt. Want XML + Apache + Stylesheets? Get AxKit.