Undeliverable message to another country

I moved my email from godaddy.com to a local exchange server and now I get an error sending email to a customer in another country.

This is the error message.
"stef@mweb.co.za
vpostwall05.mweb.co.za #550-Verification failed for <djanson@gmsminerepair.com> 550-It appears that the DNS operator for gmsminerepair.com 550-has installed an invalid MX record with an IP address 550-instead of a domain name on the right hand side. 550 Sender address rejected: Domain not found ##"

Is there something I need to setup on the exchange server to allow this to send out, and then hopefully receive?
Dennis JansonIT ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

grandebobCommented:
This looks to be a DNS problem.

Your MX record should be a host name, like mail.gmsinerepair.com not an IP address.
You should also have a host record that says mail.gmsminerepair.com is     65.216.203.214

While you are at it, contact your ISP and have them setup a reverse DNS entry for the IP address your mail server sends email as.
0
Alan HardistyCo-OwnerCommented:
You should also change the FQDN for your default SMTP virtual server - it is currently set to Edge.GMSMRM.local and should be mail.gmsminerepair.com.
You can set this under Exchange System Manager.
Expand Servers, Expand Your Server, Expand Protocols, Expand SMTP, Select your default SMTP Virtual Server. Right-click on the SMTP Virtual Server and choose properties, Click on the Delivery Tab and then the advanced button and make the changes there.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dennis JansonIT ManagerAuthor Commented:
alanhardisty, I want to make the change but I do not understand the path in your instructions. Remember I am running Exchange 2007 on Windows Server 2008 std.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Alan HardistyCo-OwnerCommented:
Ah - sorry - my mistake - so used to 2003.
Go to Organization Configuration
Hub transport
Send connectors
double click on the connector used to send the outgoing mails
And there you can change the FQDN on that connector

Then Restart the Microsoft Exchange Transport Service
 
0
Dennis JansonIT ManagerAuthor Commented:
alanhardisty, I did your update. I also updated the Receive Connector on the Edge Transport server. I then ran the SMTP diagnostics test and I came up "mail.gmsminerpair.com". Thanks.

Grandebob, I called GoDaddy and requested "reverse DNS" and they said they do not support it. However did find something about creating a SPF record to do the same. Does this sound right?
0
Alan HardistyCo-OwnerCommented:
Call your ISP - your Internet Service Provider to setup RDNS .
Your ISP is the people you use to connect your company to the Internet.
0
Dennis JansonIT ManagerAuthor Commented:
alanhardesty, Ahh, I understand now I will call them.

On the other hand, I was finally able to successfully send and receive email from my customer, however I run multiple domains on exchange. I was only successful with the "gmsminerepair.com" domain email address. When I send the same receiver and email from my "pioneerconveyor.com" account it still comes back undeliverable.

These domains all resolve to the same IP. How do I get HELO to work on all my domains?

All of these domains are on the same SAN certificate.
0
Alan HardistyCo-OwnerCommented:
Please post the full NDR message - would be nice to see if is your server or their server rejecting it.
0
Dennis JansonIT ManagerAuthor Commented:
Here it is:

Reporting-MTA: dns; Edge.GMSMRM.local

Final-recipient: RFC822; stef@mweb.co.za
Action: failed
Status: 5.0.0
Remote-MTA: dns; postwall01.mweb.co.za
X-Supplementary-Info: <postwall01.mweb.co.za #5.0.0 smtp;550-Verification
 failed for <djanson@pioneerconveyor.com> 550-It appears that the DNS
 operator for pioneerconveyor.com 550-has installed an invalid MX record with
 an IP address 550-instead of a domain name on the right hand side. 550
 Sender address rejected: Domain not found>

0
Dennis JansonIT ManagerAuthor Commented:
OK, after a closer look, I did not fix the MX record host name for that domain. I just changed it and will give it a few minutes to update the DNS records.
0
Alan HardistyCo-OwnerCommented:
Seems like you managed to change it before I could test - should be better now unless the recipient server caches DNS.
0
Dennis JansonIT ManagerAuthor Commented:
Nope. That did not work. Here is the NDR msg.

Reporting-MTA: dns; Edge.GMSMRM.local

Final-recipient: RFC822; stef@mweb.co.za
Action: failed
Status: 5.0.0
Remote-MTA: dns; vpostwall03.mweb.co.za
X-Supplementary-Info: <vpostwall03.mweb.co.za #5.0.0 smtp;550-Verification
 failed for <djanson@pioneerconveyor.com> 550-It appears that the DNS
 operator for pioneerconveyor.com 550-has installed an invalid MX record with
 an IP address 550-instead of a domain name on the right hand side. 550
 Sender address rejected: Domain not found>
0
Dennis JansonIT ManagerAuthor Commented:
The only difference I see is the HELO reply. It is "mail.gmsminerepair.com" instead of "mail.pioneerconveyor.com" though both resolve the same address. Is this causing the NDR? How can you setup 2 FQDNs for HELO?
0
Alan HardistyCo-OwnerCommented:
Change the MX record from priority 0 priority to priority 10 - apparently some servers don't like a zero priority (came from Mestha - EE God!)
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_21358714.html 
0
Alan HardistyCo-OwnerCommented:
If the HELO reply was the problem, you would not be able to send from both addresses.
0
Dennis JansonIT ManagerAuthor Commented:
I just set up the all the MX records in the DNS to the same address as the domain in the HELO response. I dent the troubled e-mail and have not yet received and response.
0
Alan HardistyCo-OwnerCommented:
Still no RDNS setup - did you call your ISP yet?
MX's are now 10's not '0's.
0
Dennis JansonIT ManagerAuthor Commented:
I am calling my ISP now.

You told me to change them to 10's. Should I change them back?
0
Alan HardistyCo-OwnerCommented:
No - 10's are good.  Leave them as they are - just letting you know the world will see the 10's!
Hope the ISP doesn't keep you hanging ;-)
0
Dennis JansonIT ManagerAuthor Commented:
You speak from experience... I called then and told me to submit an email and should hear something back in 24hrs. Wooo whooo.
0
Dennis JansonIT ManagerAuthor Commented:
I was able to successfully send the e-mail message without waiting for my ISP to setup RDNS. However I will follow through with getting that done.
Grandebob was right from the beginning so I had to give him some of the points.
alanhardesty, thank you for hanging in there with me and for your continued, immediate help. For that I give you most of the points.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.