rackAID

Call Sales: 877-435-2445

Navigation

Resources

How To Remove Your Email Server from Yahoo’s Blacklist

Posted by Jeff H. 03/09/2009

So you fire up your favorite mail client (mine’s Thunderbird) only to find upset customers and bounced emails. Appears, Yahoo! has blacklisted you. You see tons of messages with an error:

421 4.7.0 [TS01] Messages from <1.2.3.4> temporarily deferred
due to user complaints
- <1.2.3.4> ; see <a href="http://postmaster.yahoo.com/421-ts01.html">http://postmaster.yahoo.com/421-ts01.html</a>

So what now? Your server has been blacklisted by Yahoo!. The email queues are building up, clients are calling, and you cannot forward that latest NSFW video to your friends on Yahoo!.

To get removed from Yahoo!‘s blacklist, you need to follow some simple steps:

  1. Find the cause
  2. Fix the problem
  3. Wait …
  4. Fill out the form
  5. Wait …

If you are a spammer (and you know if you are), then don’t wast your time with these tips. They will not help you.

If your wearing a white hat happened to get nailed by the blacklist, read on.

Find the Cause
The first step is to find the cause. Email service providers are increasingly relying on sender reputation metrics to determine if email is spam or should be flagged for additional processing. Yahoo! works with ReturnPath for this feature. If you consistently trigger Yahoo!‘s blacklist, you may find that you get permanently blocked or your email is routed to the junk folder.

Yahoo! did not blacklist your server to spite you. Something triggered the listing. To prevent future listings, you must identify the trigger. If you get re-listed, your sender reputation will drop, and as a result, email will be even more difficult to delivery successfully.

In my experience, if you run normally clean email operations and follow these steps, your Yahoo! email delivery problems will reside within 48 hours or less.

Some key reasons for getting blacklisted:

  • Compromised Web Script
  • Compromised End-User Account
  • Legitimate Bulk Emailing
  • Forwarded Email

If you have a client forwarding large volumes of email to Yahoo! and the client flags these forwarded messages as spam, you could get blacklisted. The reason is it is impossible for the filtering to determine if the forwarding was intentional or a trick used by the spammers. As a result, spam filters often hold the last and first links in the delivery chain responsible.

Historically, open relays have been prone to blacklisting, but recent versions of hosting control panels and email software often disables relaying by default. We encourage the use of SMTP AUTH on all servers to prevent unauthorized mail relay.

Call the Postmaster
All major ISPs, Yahoo! included, maintain very useful Postmaster help pages. These pages often detail the do’s and don’ts for sending to their email servers. Yahoo!‘s Postmaster help center provides a variety of topics. When you get a chance, I recommend you review their best practices area and assure your email policies are in check with what they recommend.

Blacklist Removal Process
Do not try to get removed from Yahoo!‘s blacklist if you have not found the source of the problem. You don’t want cycles of de-listing and re-listing to damage your sender reputation. If you have found the problem, then simple wait. In many cases, I find that the block is removed in under 48 hours.

If you are still blocked after 48 hours (or impatient), you can then submit Yahoo!‘s Mail Delivery Issues Form. Before submitting, be sure you are abiding by Yahoo!‘s email policies. Also, verify that all of your DNS setting are correct. Reverse DNS (PTR), MX, A, and SPF records should all be checked If you are using DomainKeys, be sure to test that those are working as they should. The key is not to raise any red flags during the review process. Make the reviewers job easy by fixing problems first.

Though some fields on the delivery report are optional, it is best to provide as much information as possible. Especially, the “Enter additional information here:”. You will want to detail in 2-3 sentences your remediation efforts. For example, if the problem was a compromised web script send them a note:

We have identified an insecure web application on our server that permitted unauthorized email relay through our system. We have removed this script.

Keep it short and technical. Yahoo! postmaster staff reviews 1000’s of these requests, so being short and to the point is best.

Bulk Senders
If you are sending bulk email, you will receive a special type of bounce pointing you to Yahoo!‘s error pages. Before starting the blacklist removal process, be sure to review Yahoo!‘s bulk email sending policies. Once you are compliant, send in the Yahoo! Mail Bulk Sender Form to get your account exempted from the bulk sender triggers. You must maintain a clean list. Simply submitting the form does not let your email flow freely. If you are spamming, this will not help you. If you maintain clean, double opt-in lists, then your emails will get to their recipients.

Quick Review

  1. When you get blacklisted by Yahoo!
  2. Find the trigger
  3. Fix the trigger
  4. Submit a mail delivery report
  5. Wait …
  6. Review best practices.

In the next couple of weeks, I will be providing quick how-to’s for getting out of the blacklists maintained by Google, MSN, Earthlink and Frontbridge. Also, if you send large volumes of email or are an email service provider, don’t forget about email feedback loops. Yahoo! now provides a Compliant Feedback Loop based on DomainKeys.

Bookmark and Share

Comments

Photo of Jason Bradbury

Jason Bradbury · 12/02/2009 12:15 pm

Just thought I’d post a link to a spam blacklist tool I use to check the lists in real-time…
http://www.spamblacklist.co.uk.

Photo of Jeff H.

Jeff H. · 12/04/2009 01:10 pm

We also use http://www.dnsstuff.com to check for blacklists.  Unfortunately, many ISPs do not publish their blacklist.  So we do a manual telnet session to port 25 at the ISP. If you are blocked,  you will often get an error indicating what actions to take.

Photo of Jeff H.

Jeff H. · 12/04/2009 01:19 pm

Also on most servers, the IP you need to check is the main server’s address not the sites IP address.

Add Comment

Notify me of comments?