Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
The Internet

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

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?"
This discussion has been archived. No new comments can be posted.

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

Comments Filter:
  • Try not bouncing any emails to addresses at yahoo.com, wait a few weeks and they should take you off the list.

    -Wade
  • possible solution? (Score:3, Interesting)

    by digitalmuse ( 147154 ) on Thursday February 28, 2002 @09:15AM (#3083545)
    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.
  • I tried to send mail to a friend of mine last week, Yohoo appearently has something to do with his domain(I think they host it for him in some way)...anyway my mail bounced for no apparent reason....

    Postfix Bounce Log included:
    The Postfix program

    : host mail.san.yahoo.com[209.132.1.30] said: 550
    RCPT TO: Relaying not allowed

    [ Part 2: "Delivery error report" ]

    Reporting-MTA: dns; majere.epithna.com
    Arrival-Date: Thu, 21 Feb 2002 14:48:45 -0500 (EST)

    Final-Recipient: rfc822; brianb23@mystictavern.com
    Action: failed
    Status: 5.0.0
    Diagnostic-Code: X-Postfix; host mail.san.yahoo.com[209.132.1.30] said: 550
    RCPT TO: Relaying not allowed

    [ Part 3: "Undelivered Message" ]

    Date: Thu, 21 Feb 2002 14:48:45 -0500 (EST)
    From: xxxxxxxxx
    To: Brian and Angi Berkovitz
    Subject: Re: friday
  • by YeOldeCurmudgeon ( 465541 ) on Thursday February 28, 2002 @11:14AM (#3084092)
    I've noticed a significant increase in the amount of spam received on the Yahoo accounts of friends since January, 2002. Personally, I believe that when various free Groups were bought and merged with Yahoo groups, some came with email address security weaknesses spammers are exploiting. I added one filter that seems to kill most of the internal Yahoo spam. If the header says it originate's from within Yahoo but doesn't have the typical Yahoo! trailer, it is spam.
  • As the postmaster [at] kitv.co.uk. I had similar problems with Hotmail, lots of junk email from them, hotmail rejecting email from my domain, an arrogant postmaster who was completely ignorant of RFC, .

    After trying to resolve it directly with them and failing. I simply blacklisted hotmail, the amount of time saved from less junk email vastly over shadowed the time required to explain that we 'no longer supported hotmail because of all the junk email they send. 'You can hear my customers sagely nodding to themselves, praising my iniative, and vowing to tell there friends to move from hotmail."

  • by fm6 ( 162816 ) on Thursday February 28, 2002 @01:19PM (#3084998) Homepage Journal
    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.

"If it ain't broke, don't fix it." - Bert Lantz

Working...