Anti-Spam, or, Anti-Delivery...
Yahoo! is getting to be very aggressive against spam. Problem is we can’t deliver ANYTHING for about the past 6 days because we can’t get a dialog with them as to 1) why they’re unblocking and 2) they won’t unblock. I think ultimately here we’ll be forced to discontinue most or all forwarding services if Yahoo!, etc, continue the current extremely unfriendly-unable-to-cooperate behavior.
What would I like to see? Well…It’d be nice if they used a SpamCop like process to find the ACTUAL source of an email and inform some sort of blacklist of that source, that other places can query. (DNSBL’s are great for this, REALLY!)
The problem is then that the small percentage of spam in this particular case causes the majority of email to be undeliverable. AND PEOPLE ARE REQUESTING THIS STUFF GET FORWARDED.
This is part of why we’re trying to take steps to reduce the amount of junk we take in, I’m still researching (or rather it’s on the ToDo list) how we can effectively deploy greylisting.
I’m also working on redesigning the mail system so that we can do more processing “up front” and for forwarded addresses. Doing this requires more horsepower in our mail front end’s (MFE’s) and requires we take some steps to reduce the amount of obvious junk before we start doing heavy work. Right now we do some blacklist lookups, then go through AV processing, then pass it along for final delivery, either for local delivery, or offsite delivery. Local delivery benefits from being processed by SpamAssassin, remote delivery can’t. Our current SA setup is bound by which mailbox the final delivery goes to for selecting rules/scores, so no local mailbox, no way to go. It’s also directly coupled with final delivery presently.
What I want to do, is for forwarded addresses allow a “discard” threshold of some sort to be set. Set it so it can’t be turned off completely and can’t be raised above a certain score threshold (say 8 or 10) and either discard or locally deliver anything above the threshold.
The real problem is of course the rather dull way in which we all handle this mess. If more providers blocked the crap up front there’d be a lot less to deal with.
I hear everyone clamoring but it’s so haaaaaard. Seriously now, REALLY, how many of your customers NEED port 25 access? I bet almost none. They should be using your mail servers ISPs! Heck even just having a voluntary opt-in-to-port-25 access will solve a huge chunk of the issue, even if the ISP does no verification.
Maybe this is the end of all forwarding service. As that seems to cause most of the problem, uneducated users who refuse to listen and stop reporting spam on their forwarded email is what lead to the removal of AOL forwarding.