Getting the following - <EXCHANGE.mydomaon.Local> is invalid or DNS says does not exist>

I have a user that is getting the following message when is sending to the an external email address she is using Outlook2003 and we run Exchange 2003:

EXCHANGE.mydomain.Local #5.5.0 smtp;501 <EXCHANGE.mydomaon.Local> is invalid or DNS says does not exist>

Could someone help me out to troubleshoot this issue?

Thank you
llaravaAsked:
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.

Alan HardistyCo-OwnerCommented:
Your send connector / SMTP Virtual Server is advertising itself incorrectly.  You need to change the FQDN to be something like mail.yourdomain.com which resolves in DNS correctly to the world.
.local names are not resolveable / routable across the internet.
What version of Exchange are you on?
0
Alan HardistyCo-OwnerCommented:
0
llaravaAuthor Commented:
We are fine in DNS. All the test came up fine. I have also test via DNSStuff and everything is fine.

I have to appologize because I have changed the domain in the error message in a way that misleaded you.

EXCHANGE.mydomain.com #5.5.0 smtp;501 <EXCHANGE.mydomain.com> is invalid or DNS says does not exist>

NO domain.local

I think this is something on the other end...however I would like to prove it. And I am not sure how?
0
Alan HardistyCo-OwnerCommented:
Can you drop me an email to alan @ it-eye.co.uk please and I will check and test.  Please include your domain name and internet facing IP address.
I guarantee to keep the info private.
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
llaravaAuthor Commented:
Just to update the question since alanhardisty has help me out to do some troubleshooting:

A user is having problems sending e-mail to recipients she sends to every day. The error is:

User@otherdomain.com on 11/26/2005 1:11 PM. You do not have permission to send to this recipient. For assistance, contact your system administrator. ... Relaying denied. IP name possibly forged.(xx.xx.xx.xx)>.

http://searchexchange.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid43_gci1155538,00.html

According to this post and with it could be related to:

It sounds like the recipient's SMTP server is doing a reverse lookup on your domain and failing. You should double-check your public DNS record to make sure that the server's PTR (pointer) record has the servername mapped to the server's correct IP address.

This is our current Exchange setup:

1.) We run an active-passive cluster of Exchange 2003

2.) The MX records are being hosted in Postini (Google)

3.) We are running a load balancing solution for redundancy between 2 ISP providers. So A and PTR records for mail.domain.com have an entry for each the providers in the public DNS.

For example:

ISP1

mail.domain.com - 1.1.1.1

1.1.1.1 - mail.domain.com

ISP2

mail.domain.com - 2.2.2.2

2.2.2.2 - mail.domain.com

We are now using provider one so if any emails are being send they headers of the email show the 1.1.1.1 for mail.domain.com

However if I run a DNS query for A/PTR resolution for mail.domain.com the 2.2.2.2 IP is the one that resolves.

So email is being send like 1.1.1.1 external DNS resolution to mail.domain.com replies on 2.2.2.2

Like I said a couple of users are getting this type of message:

User@otherdomain.com on 11/26/2005 1:11 PM. You do not have permission to send to this recipient. For assistance, contact your system administrator. ... Relaying denied. IP name possibly forged.(xx.xx.xx.xx)>.

Could this setup be the problem since we are sending at 1.1.1.1 but the world resolves mail.domain.com at 2.2.2.2?

Also the FQDN for the cluster is mail.domain.local does the entry need to be changed to mail.domain.com. If we have to change it why should be make the change?

Thank you.

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.