Results 1 to 6 of 6
  1. #1
    Join Date
    Nov 2001
    Location
    Toronto
    Posts
    220

    Difficulties e-mailing @yahoo addresses

    For many months now Yahoo keeps returning 'temporarily deferred' errors when our server tries to deliver an e-mail to any @yahoo address. Sometimes the emails manage to get through after several hours or days of trying and in many other instances the delivery attempts eventually time out after 4 days resulting in a bounce.

    Sample Log entry:

    2007-12-19 03:59:49 [8808] 1J4umL-0002I2-IQ == [email protected] R=lookuphost T=remote_smtp defer (0): SMTP error from remote mail server after initial connection: host c.mx.mail.yahoo.com [216.39.53.3]: 421 Message from (72.52.***.***) temporarily deferred - 4.16.50. Please refer to http://help.yahoo.com/help/us/mail/defer/defer-06.html
    Yes, we have read the above URL above. It has no technical explanation or solution for the error. The only thing we got out of it was to fill out a form for help which we did. But they don't even read our e-mails. They keep sending back generic copy & paste e-mails which are irrelevant to the problem (e.g. asking for info on our mailing list.. what mailing list!? asking for a sample e-mail which went into the bulk folder.. Who said anything about mail going into bulk folder!?). For over 2 months we've been trying to get some sort of explanation for the error or some tips on what to do. They're of no help.

    Meanwhile our users continue to have serious problems e-mailing @yahoo addresses... Anyone else experiencing this problem? Any tips?

    Thanks.

  2. #2
    Join Date
    Apr 2003
    Location
    Melbourne, AU
    Posts
    539
    Search the board.. the problem's been going around the block.
    WK Woon
    CTO | http://www.aflexi.net - A flexible Network
    Building the next generation CDN platform - DEMO .... coming soon

  3. #3
    Join Date
    Nov 2001
    Location
    Toronto
    Posts
    220
    Yes, should have done a bit more searching before posting. Three things I've come up with so far:

    Reverse DNS: already setup
    PTR records: setting up PTR records will cause problems for customers who forward their mail to external e-mail addresses.
    DOMAIN KEYS: Not even sure what the heck this is... will have to read up more tomorrow when I wake up..

  4. #4
    Join Date
    Nov 2007
    Location
    Fort Worth
    Posts
    40
    This issue is faily common and unfortunately there is no quick fix. You need to ensure everything is setup correctly on your side before contacting Yahoo. This includes Reverse DNS, SPF records, correct HELO, and DomainKeys (optional). Add SPF record to your domains sending the email and make sure your mailserver is sending a valid HELO hostname of your mailserver. To test the HELO, telnet to the mailserver on port 25 and make sure address it responds with is a full qualified domain name and the address itself is pingable.
    ---
    Dustin H., MCSA
    Enterhost Support Team
    www.enterhost.com

  5. #5
    Join Date
    Nov 2001
    Location
    Toronto
    Posts
    220
    Quote Originally Posted by Enterhost_Dustin View Post
    This issue is faily common and unfortunately there is no quick fix. You need to ensure everything is setup correctly on your side before contacting Yahoo. This includes Reverse DNS, SPF records, correct HELO, and DomainKeys (optional). Add SPF record to your domains sending the email and make sure your mailserver is sending a valid HELO hostname of your mailserver. To test the HELO, telnet to the mailserver on port 25 and make sure address it responds with is a full qualified domain name and the address itself is pingable.
    Nice tips, thank you. I have reverse DNS setup and I added SPF records for a few domains to test it out. As far as the HELO command, do you mean Yahoo dislikes EHLO? Any ideas on how to change exim to send HELO instead of EHLO?

  6. #6
    Join Date
    Nov 2007
    Location
    Fort Worth
    Posts
    40
    EHLO is fine, just need to make sure your mailserver presents itself with a valid fully qualified domain name (FQDN). Most mailservers reject EHLO that simply say 'mailserver', 'exim', or other generic entries that dont point to a valid IP
    ---
    Dustin H., MCSA
    Enterhost Support Team
    www.enterhost.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •