Slashdot Mirror

← Back to Stories (view on slashdot.org)

Survival Tips for Yahoo's New Anti-Spam Policies?

Posted by Cliff on from the tackling-the-SPAM-hydra dept.

skagin asks: "Yahoo has instituted a new set of anti-spam policies which are causing havoc for our customers (we're a small ISP). List mail with non-existant, over-quota, or recently cancelled recipients is being bounced whole, and much of the one-to-one mail we send is bouncing. Yahoo tells us that our mailserver is being treated as suspicious because of the number of bad recipients being sent to, but most of those are bounces from yahoo spam sent to non-existant addresses on our network. Our customers are going nuts. Is anyone else out there having this problem with Yahoo?"

3 of 18 comments (clear)

  1. possible solution? by digitalmuse · · Score: 3, Interesting

    Could you possibly use procmail to drop all that bad spammage that's being sent to the non-existant users on your domain?
    Even better, don't just drop them, collect them and drop the collection of yahoo-originated spam on their desk;
    "It's your friggin mess, you clean it up..."
    all else fails, inform all your users with a nicely worded e-mail along with some e-mail address for the appropriate people who they can complain/rant to at (uselessbastards@yahoo.com)
    Ask them to forward this to any of their user@yahoo.com associates and put the pressure on from both sides. Good luck and let us know how things turn out.

    --
    "If I wanted your input on my pet project, I'd stick my hand up your ass and use you like a sock-puppet." - Muse
  2. Re:That might explain by david+duncan+scott · · Score: 3, Interesting

    Is that your friend's real address?

    --

    This next song is very sad. Please clap along. -- Robin Zander

  3. Yahoo Mail -- Silent Edits by fm6 · · Score: 4, Interesting
    This is pretty offtopic, but I can't resist the chance to bring attention to this problem.

    As an anti-virus measure, Yahoo Mail filters all HTML attachments to disable malicious Javascript applets. What's wrong with that? The filtering is very simplistic. There's no attempt to identfy and remove scripts as such. They just do a global search for intrusive Javascript constructs ("eval") and replace them with benign ones ("review"). They don't even check for word boundaries! So if you get a newsletter called "Medieval History" it will come through as "Medireview History".

    The potential for garbled communication is mind-boggling. To make matters worse, they don't warn people that they do this.