Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Can't send emails to Yahoo

Posted on 2012-09-17
12
Medium Priority
?
909 Views
Last Modified: 2012-10-19
Hello,

I just changed server and moved all my accounts but one. The domains on the new server can't send emails to yahoo accounts, but they could when they where on the old serever and the one still on the old server can email yahoo accounts. I checked the dns settings and the spf records and they seem fine, I just can't figure out what the problem is.
0
Comment
Question by:izzy11515
  • 7
  • 5
12 Comments
 
LVL 16

Expert Comment

by:grahamnonweiler
ID: 38406757
What is the error / bounce message you receive from Yahoo! when you try to send emai? It is possible that Yahoo! is blocking your mail because your new IP address is blacklisted.
0
 

Author Comment

by:izzy11515
ID: 38408639
They all come back with this error message: Reason: General Failure which doesn't really help.
I' ve tested the mail server on all blacklists I could find but it's not listed anywhere. I can email Hotmail, gmail etc without any problems. Only Yahoo is rejecting the emails.
0
 
LVL 16

Expert Comment

by:grahamnonweiler
ID: 38408871
If you wish, using one of the email accounts on the server that is having problems sending to Yahoo! you can send an email to "support-at-nonweiler.com" and we will check your headers and server handshake for any obvious signs or reasons it may be getting blocked at Yahoo!

Other than that it is difficult to recommend a course of action. One thought however, is that the new DNS settings are still replicating, although normally a DNS change is fully replicated within 72 hours maximum.
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 

Author Comment

by:izzy11515
ID: 38408900
I just sent you an email.
0
 
LVL 16

Expert Comment

by:grahamnonweiler
ID: 38409086
We have received your mail.

The irregularities in the transmission chain are:

1) Reverse lookup on the sending server IP address does not match the sending server domain name - this could present some problems (even though the converse reverse look matches most mail servers look for the HELO domain to match the RDNS lookup).

2) Your SPF record is using a tild "~" when it should be a dash "-" (again not all mail servers get upset about this but some do)

3) The sending IP has a "neutral" senderbase score (should not cause problems but coupled with the above might increase risk)

Based on the above, the only real standout thing is item 1.
0
 

Author Comment

by:izzy11515
ID: 38409175
Thanks. About Nº1, on my server I have many domains and I had to put one as Local domain name in Mailenable SMTP properties. Should I have put something else?
0
 
LVL 16

Expert Comment

by:grahamnonweiler
ID: 38409903
The reverse lookup on the server's IP address give a different domain name from what you have set-up in MailEnable.

Change the reverse lookup to be the same as mail enable.

So (using "yourdomain.com" as an alias for your real domain name") you currently have:

server.yourdomain.com

returning on a reverse lookup for the IP - when it should really be:

mail.yourdomain.com

which would then be the same as MailEnable.

Either that or change MailEnable to "server.yourdomain.com"
0
 

Author Comment

by:izzy11515
ID: 38413120
I fixed both issues 1/ and 2/ but the problem remains.
0
 
LVL 16

Expert Comment

by:grahamnonweiler
ID: 38416555
Can you access the MailEnable logs? If so look at the SMTP outgoing log to review the communication with Yahoo!

If you can not access the log files then ask your hosting company to provide you with an extract of the log for a Yahoo! transmisson.

Are you sure the bounce message is actually coming from Yahoo!, normally it shows you the reason, with some detail at least. It is possible that the bounce message is coming from MailEnable.

Also check which version of MailEnable is running at your host - it could be an older version that is not RFC compliant (although this is unlikely)
0
 
LVL 16

Expert Comment

by:grahamnonweiler
ID: 38416562
I also noticed that you say at the opening of this thread that you still have one account on the old server - which I assume has a different IP address. I am not sure how that is able to send mail for your domain as the SPF record would exlcude it. Anyway, is that old server also using MailEnable?
0
 

Author Comment

by:izzy11515
ID: 38417407
it's another domain on the other server. All the domains that I passed to the new server have the same problem, doesn't matter what domain I use. Mailenable version is 6.5.

Stmp log:

All messages from xxx.xxx.xxx.xx will be permanently deferred; Retrying will NOT succeed. See http://postmaster.yahoo.com/errors/421-ts03.html

Doesn't make much sense since it's a new server with a new ip and I haven't been sending many emails.
0
 
LVL 16

Accepted Solution

by:
grahamnonweiler earned 1500 total points
ID: 38421192
Sorry for the delay getting back to you.

Now it makes sense. Yahoo! has blocked your IP address, either because of recent activity or (more likely) past activity that exceeded their "allowable" burst rate.

It's quite possible that someone had used the IP address for a spoof'd Yahoo! account (either intentionally or unintenionally through a virus/malware).

In any case Yahoo! have blacklisted your IP address - and it seems to only be Yahoo! - and normally when this happens it can take months to get them to remove your IP address. A little bit hypocritcal really considering the amount of spam that comes out of their IP address space.

If it is only your domains on the new server then you can try contacting Yahoo! to have your IP address removed from their Blacklist, but as I say that will take some time.

If there are other domains on the server that you do not control then you will have to talk to your hosting company about getting moved to a different IP address.

Bottom-line, I'm sorrry to say, is the quickest solution will be to change IP addresses if it is essential that you can send to Yahoo! - and if you are on a Shared Hosting environment it might be wise to consider moving anyway as obviously there were some issues with spam originating out that IP address space.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We aren’t perfect, just like everyone else.  Check out the email errors our community caught and learn the top errors every email marketer should avoid.
Last month Marc Laliberte, WatchGuard’s Senior Threat Analyst, contributed reviewed the three major email authentication anti-phishing technology standards: SPF, DKIM, and DMARC. Learn more in part 2 of the series originally posted in Cyber Defense …
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses
Course of the Month20 days, 16 hours left to enroll

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question