Forums & Blog

Hi All,

We cannot deliver messages to users with Yahoo Mail consistently, we keep getting a 421 message.  Eventually SmarterMail stops retrying.

Here is the message we get:

Failed Recipient: <REMOVED ADDRESS>@yahoo.com
Reason: Remote host said: 421 Message from (208.106.250.195) temporarily deferred - 4.16.50. Please refer to http://help.yahoo.com/help/us/mail/defer/defer-06.html

We have both DKIM and DomainKeys set up, and I tested the configuration.  Also, we have reverse DNS, SPF, and an email policy in place.  

*sigh* shouldn't this be enough for Yahoo?  

We have created a free online dating site in Chinese / English and wish to be able to send notifications to our users when someone sends them a new message.  These notifications are configurable by the User, and can be disabled.  I've run dnsreport on http://www.zendear.com and everything is as it should be (the only fail is intentional recursive lookups).

Questions:

1.  Who can I contact at Yahoo about this?  Anyone have any experience resolving Yahoo Mail delivery issues?

2.  What information / evidence will they need that we're legitimate, (uhh other than Reverse DNS, SPF, DomainKeys and DKIM) and the notifications that people receive are because they configured their accounts to notify them (and that they can turn off the email notifications)?

3.  If I log on as admin to SmarterMail and watch the Spool directory, I see the retries.  How many times does SmarterMail retry on a 421?  Is this configurable?  

Thanks very much, and happy holidays!!!

here you go.

http://www.smartertools.com/forums/p/13531/30555.aspx#30555

http://support.smartertools.com/Customer/KBArticle.aspx?articleid=191&KBSearchID=152498

 A 4x error means sending server should retry and SM retry as usual.

Here are my retry settings works fine with Yahoo.

5, 15, 30, 60, 90, 1140, 2280

I had the same message but it was because my Reverse DNS wasn't set correctly  (at least...after fixing it, mail went through to Yahoo just fine).

Might be worth double-checking?

We are having the same issue with Yahoo mail. We are a small ISP with about 5000 users. Only a very small percentage of our users can send email to Yahoo, and even that is sporadic. Hundreds of our users' legitimate emails are rejected daily with the following message: 421 Message from (208.66.56.9) temporarily deferred - 4.16.50. Please refer to http://help.yahoo.com/help/us/mail/defer/defer-06.html I have filled out "Yahoo! Mail Delivery Issues Form" a few times. I get the following automated response message: -------------------------------------------------------------------- Hello, This is an automated message regarding your recent request for Yahoo! Mail Customer Care support. We have received your message and willYa respond within the next 48 hours with an answer. Thank you for reaching out to us. We look forward to helping you! Sincerely, Yahoo! Customer Care **Please do not respond to this message as no one will receive it. -------------------------------------------------------------------------- But I never received a response from Yahoo and they continue rejecting our users' legitimate emails. After reading many forums and blogs, it appears that they are doing the same thing to many other small ISPs and companies with their own email servers. This practice can interrupt many legitimate business communications and hurts many small businesses. If anyone has a resolution to this issue, I would greatly appreciate your help. Bernie

Just a word: Somebody must be crazy if he does use a freemail email like Yahoo, Google, Hotmail or GMX for business mail. If a business depends on mail they will surely not use such an account. So it's mostly used from private persons and from spammers, and that does not hurt so much. Also, if Yahoo has such roles it is there fault and not ours. Not every mailserver can implement it's own special rules, where would we get then? So Yahoo is me really careless.

Fritz

I agree that Yahoo is way too agressive in their spam policies. It would all be solved if they followed aol with the loop system.

I also agree that people should not use yahoo for business, but the reality is that many do and we need to make sure our servers can communicate with yahoo.

The upside to all of this is that we, as hosts, have a huge advantage now. we can easily guarantee to business owners that they will receive all of their legitimate email if they switch to us. Yahoo cannot make that claim. In many ways they will be their own downfall.

I started getting this when I moved to a 2008 VPS at Crystaltech recently for my small private hosting operation.  I just followed the link in the 421 bounce and went through the process of getting my mail server IP whitelisted (they only partially whitelisted it). 

I added DomainKeys to most of my domains and everything NOW finally seems to be working although it's still not 100% perfect.  Still some mails sent from me to Yahoo go into user's spam box even if it's a simple "Hey you, how are things going" from one of my users to a Yahooian.  And this is when DomainKeys pass "ok" and SPF is valid, etc.

What more do they want?

I hate Yahoo.

 i have: spf, privacy policy, unsubscribe links, physical address in our mails, domainkeys, sender id, reverse dns, valid helo/ehlo...

 

still get the same errors even if retry is 360, 360, 180... we have been able to send 0 emails to yahoo since august 25th. this is about 5k emails a day not going to yahoo.

 

please check that your helo test is valid... we were having issues and had to create a 2nd spf record to solve the issue. usually the spf record is a txt record with a blank name... however we had to create one with the same name as the host... and delete our cnames. so instead of using a valid fqdn with cname... we now just have host "mail"... then we have mail as a second spf record with the same name as the host... so "mail"... this helped.

 

send test to:

 spf-test@openspf.org

check-auth@verifier.port25.com

 

helo=none? or helo=pass? in the first one. 

 Same issue here, we were whitelisted by Yahoo for many years and we recently switched to a new IP (which was not blacklisted anywhere).  RDNS and DNS match up perfectly, but Yahoo seems to have it in for us.  I finally gave up becuase of too many customer complaints and switched our Mailserver back to the old IP address and guess what...now Yahoo won't accept mail from that address.  If I babysit the spool and reset the retries every so often, they seem to get through with enough retries. 

 

Anybody find a solution that works?

 Yes we have found a solution that effectively works. Please email us at admin[at]whosting.net so we can help you

 stac