Yahoo delays, part 4: Yahoo blogs

Yahoo posted some suggestions about contacting their postmaster group over on the ymail blog.  They also explained what they were doing to solve the problems with response delays.

Some of the problem is being caused by excessive follow-up emails, either because senders did not provide all the necessary information initially or because they are asking why they have not heard anything. Each of these requires more work on the part of Yahoo and throws the queues into further disarray and puts everyone even more behind.

Yahoo asks that people be patient, they are working through things. On their end, they have added more staff to the postmaster team. They also suggest senders can help by providing ALL the information they ask for at before submitting the request. Incomplete requests contribute even more to the backlog as Yahoo employees have to chase down senders to get their full information.


  1. Evan says

    I’m just starting to see approval/denials come in which were submitted in early February, so hopefully they’re able to catch up quickly – a month is a long time to wait for a response.

  2. Alex Grieve says

    First thing Yahoo should do if they don’t want to continue mis-identifying good emails as spam is to stop using Spamhaus’ PBL-Policy Black List (see, under error code: 553 5.7.1 [BL21]). Using the Spamhaus XBL, which is essentially the CBL-Composite Black List found at, and Spamhaus’ own SBL-Spamhaus Black List are just fine. But using the PBL is almost akin to committing a hara-kiri! Our tests on our mail server have consistently produced close to 6% of FPs-False Positives, in other words, non-spam emails which got blocked by the PBL.

    Quoting Al Iverson ( “I would always recommend that before using Spamhaus ZEN, or any other blacklist, that you test and investigate on your own, to make sure that you are comfortable with the blacklist provider’s policies.” Good advice which you’d think large email hosters such as Yahoo would heed before starting to deploy *any* blocklist for their millions of users.

  3. Having Email Delivery Problems with Yahoo? Welcome to the Club! -Email Delivery, Avoiding Spam Filters and RSS Marketing Tools says

    […] post on email delivery at Yahoo summed it up so well that I want to recommend reading […]

  4. Al Iverson says

    The point of PBL is to block mail from things that aren’t supposed to be mail servers, either by observation or ISP policy.

    False positives in a list like PBL come in two flavors:

    1. Oops, that IP isn’t dynamic. Oops, we do have MTAs in that space. Oopses, mostly. PBL is good about addressing those. They even have self-removal.

    2. Servers disallowed by ISP policy.

    Those latter ones start religious wars. If you want to accept mail from IPs that shouldn’t be sending mail as defined by the policy of the IP address owner, more power to you. But you can’t use any sort of PBL or any dynamic-blocking list.

    I think FPs from #2 are really only a tiny subset of guys running Linux boxes in their basement. Frankly, I’m okay with not receiving that mail.

    I’d love to see Alex’s stats, because at face value, I don’t see how it’s even possible for PBL to block 6% of legitimate mail. I’m just not buying it.

  5. Alex Grieve says

    Whether one agrees or not in principle, an unknown number of individuals and small companies still run private mail servers from static, and sometimes even dynamic, IP addresses provided by their ISPs. One more rather less-discussed issue is the large number of emails sent from home DSL and cable lines which are then routed via remote mail servers before reaching their destinations.

    In both cases above, the marking of non-spam emails as spam becomes virtually inevitable when using blocklists such as Spamhaus’ PBL which lists millions of IP addresses used by customers of large telecom companies and ISPs.

    Our 6% FP-False Positives rate for PBL comes from real-life filtering for hundreds of user mailboxes, unlike some statistics generated in artificial environments that have no users other than the site’s owner (e.g.

    One can only hope Yahoo will come to its senses and stop its use of non-precise blocklists such as Spamhaus’ PBL if it wants to reduce the number of legitimate emails that are bound to be wrongly rejected as a result of consulting those blocklists. Or it may find its customer base change allegiance to more reliable services that do not blindly reject emails at the perimeter.

  6. laura says

    Hi, Alex,

    I do understand your point and I believe there are some Yahoo folks reading this blog. I can only posit that their testing shows that for mail incoming to Yahoo their statistics show something completely different.

    If using the PBL is problematic for them, and blocks more real mail than they believe their users will put up with, then I expect to see them drop it.

  7. SilentLamb says

    Mar 27 14:50:29 mailhost postfix/qmgr[27984]: 497B11A21FE: to=, relay=none, delay=5.3, delays=5.2/0.03/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host[] refused to talk to me: 553 Mail from XXX.XXX.XXX.XXX not allowed – [10])

    We’re getting this right now. We’re not anyone’s black hole list. I checked. Nor do we fail the open relay test. The email address that you see above is my personal yahoo email addy. The email that was sent was sent from my personal work email addy. The email that was sent said “Test to see I can get this”.

    JFC!!! We’re an educational institution!!!!! We’re not spamming anyone.

  8. laura says


    1) are you using a NAT and is the blocked IP actually the NAT IP?

    2) Is it possible that IP being blocked is an open proxy?

    Without the IP I can’t help you troubleshoot it any further, but those are where I would start. The full list of things to do is on the Yahoo postmaster page at:

  9. Alex Grieve says

    Hi Laura,

    I am happy to report that Yahoo no longer seems to be rejecting emails sent from PBL-listed IP addresses (PBL-Public Policy List). Those emails now seem to be pushed straight into the spam folder, probably without being processed by spam filters, instead of being rejected outright. How do I know that? I have received 2 100% non-spam emails in my spam folder in the last 24 hours and they were both listed in PBL and PBL only.

    Hoping that this is a permanent policy change on Yahoo’s part.

    I would advise anyone with a Yahoo email account to regularly monitor their spam folder in case there is a good email stuck somewhere in it.

  10. Chris Lang says

    This is not meant to be a comment, I just didn’t see any way to contact you.

    I wanted to let you know that I have a new site and a brand new email whitelist generator here:

    I have so much conflicting content that I have to divide the two blogs so the email stuff went to email jedi.

    I have completely retooled the app and now it has even more instructions like blackberries and SpamCop (yeah spam cop has a whitelist).

    Any links of comments on this would be appreciated.

    – Chris


Your email address will not be published. Required fields are marked *

  • DNS problems

    Hurricane Electric had a significant outage of their authoritative DNS servers this morning, causing them to return valid responses with no results for all(?) queries. This will have caused delivery problems for any mail going to domains using DNS - which will include some of their colocation customers, as well as users of their free services - but also will have caused reverse DNS to fail for most servers hosted by Hurricane Electric worldwide, so if any of your mail is being sent from HE hosted machines you may have seen problems. (We're HE customers so we noticed. Still happy with them as a vendor.)No Comments

  • DNS issues

    If you're sending email from any address beginning with a 65 - in - it's possible you'll see some delivery problems. Something appears to be broken with dnssec signatures for the reverse DNS zone, leading queries for reverse DNS to fail for anyone using a dnssec aware DNS resolver (which is almost everyone).1 Comment

  • Our green bar certificate is going away

    Later today we'll be switching from an Extended Validation ("green bar") SSL certificate to a Domain Validation certificate. This isn't exactly a planned change but I'm waiting for responses from Comodo before I go into it too much. I'll share some more details next week.3 Comments