MX records - 550-Verification failed error
I can't figure this one out.
I have users of one of my domains having trouble getting thier emails to people. Outgoing emails often get this response:
----- The following addresses had permanent fatal errors -----
<sample@sample.com>
(reason: 550-Verification failed for <test@pactprevention.org>)
----- Transcript of session follows -----
... while talking to sample.com.:
>>> RCPT To:<sample@sample.com>
<<< 550-Verification failed for <test@pactprevention.org>
<<< 550-No Such User Here
<<< 550 Sender verify failed
550 5.1.1 <sample@sample>... User unknown
Reporting-MTA: dns; jessica.andrews.com
Received-From-MTA: DNS; [72.243.245.50]
Arrival-Date: Mon, 21 Jul 2008 11:46:03 -0500
The sample@sample.com is a sample of course, but the rest is accurate in case you are able to test this for me. The actual domain (A records) go to this organzations web master, I handle the email for them, so just the MX records are pointed at my server.
All my other domains are set up the same way, with mail routed to mail.andrews.com, where my server handles incoming mail. Other domains I have set up the same way as pactprevention work without getting caught with this same error. I can't find any difference between my domains that work ok and this one that gets the error.
Is someone able to test this or have an idea of what needs changing for the user to be verified correctly?
I have users of one of my domains having trouble getting thier emails to people. Outgoing emails often get this response:
----- The following addresses had permanent fatal errors -----
<sample@sample.com>
(reason: 550-Verification failed for <test@pactprevention.org>)
----- Transcript of session follows -----
... while talking to sample.com.:
>>> RCPT To:<sample@sample.com>
<<< 550-Verification failed for <test@pactprevention.org>
<<< 550-No Such User Here
<<< 550 Sender verify failed
550 5.1.1 <sample@sample>... User unknown
Reporting-MTA: dns; jessica.andrews.com
Received-From-MTA: DNS; [72.243.245.50]
Arrival-Date: Mon, 21 Jul 2008 11:46:03 -0500
The sample@sample.com is a sample of course, but the rest is accurate in case you are able to test this for me. The actual domain (A records) go to this organzations web master, I handle the email for them, so just the MX records are pointed at my server.
All my other domains are set up the same way, with mail routed to mail.andrews.com, where my server handles incoming mail. Other domains I have set up the same way as pactprevention work without getting caught with this same error. I can't find any difference between my domains that work ok and this one that gets the error.
Is someone able to test this or have an idea of what needs changing for the user to be verified correctly?
I bet it's a missing Reverse Lookup Record (PTR Record). That is by far the most common cause of errors like this.
If 72.243.245.50 is the public IP of your mail server then this is very likely to be the case. There is no Reverse Lookup Record for that address.
You must ask your ISP to add one for you, it should point to the FQDN of the SMTP service, which should have an associated Host record.
e.g.
SMTP Service Name: smtp.yourdomain.com
Public FQDN: smtp.yourdomain.com -> 72.243.245.50
Reverse Lookup (PTR): 72.246.245.50 -> smtp.yourdomain.com
Chris
Yeah.. thought of that, but he said :
"All my other domains are set up the same way, with mail routed to mail.andrews.com, where my server handles incoming mail. Other domains I have set up the same way as pactprevention work without getting caught with this same error. I can't find any difference between my domains that work ok and this one that gets the error. "
which tends me to think that hes got multiple domain names already running on this mail server successfully, therefore its probably not going to be a DNS related issue...
Steve
"All my other domains are set up the same way, with mail routed to mail.andrews.com, where my server handles incoming mail. Other domains I have set up the same way as pactprevention work without getting caught with this same error. I can't find any difference between my domains that work ok and this one that gets the error. "
which tends me to think that hes got multiple domain names already running on this mail server successfully, therefore its probably not going to be a DNS related issue...
Steve
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you both very much.
I found a tool that tests the mx record and apparently none of my domains has a ptr. Which begs the question, why is this domain having trouble and not every domain. Maybe there is some whitelisting going on or something else that is also a factor.
But anyway, to get the ptr resolving correctly, from what I have read after reading your answers, I have to contact my hosting company, it's not anything on my server that I can adjust (unless I starting hosting the dns records on my box).
Thanks again, you've gotten me on the right track here.
I found a tool that tests the mx record and apparently none of my domains has a ptr. Which begs the question, why is this domain having trouble and not every domain. Maybe there is some whitelisting going on or something else that is also a factor.
But anyway, to get the ptr resolving correctly, from what I have read after reading your answers, I have to contact my hosting company, it's not anything on my server that I can adjust (unless I starting hosting the dns records on my box).
Thanks again, you've gotten me on the right track here.
what mail server software are you running ?
this wont be a DNS issue though, it will be a Mail Server configuration issue.
so long as you have the MX record set to point to your mail server IP in the zone file for the domain name, then thats all you need to do with DNS.. the rest is how you configure the mail server to handle it..