asked on

Certain inbound email getting bounced back with 550 not local host errors

I have a few external customers that are having issues email my company on occasion. When them messages are getting sent back, they are getting the following error:

Remote host said: 550 not local host mydomain.net, not a gateway or similar

My network is configured as follows:
TW Business Class Internet
Cisco ASA 5505
MS Server Standard 2003 SP2 RC2/Exchange 2003 SP2

I've researched, and researched, and researched this. I've seen some stuff about configuring the senders client for SMTP authentication, but this doesn't happen all the time. Any help would be greatly appreciated.

SAPVYK

Hi just go through this link check if they are getting the same error:
https://www.experts-exchange.com/questions/23230783/Email-forwards-no-longer-working.html

If not please paste the exact error they are getting

glenmetz

ASKER

Thanks for your replay SAPVYK. Thats not really the exact issue. Here are some NDRs that have been sent to us in regards to this issue:

Hi. This is the qmail-send program at yahoo.com.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<user@mydomain.net>:
198.87.210.123 does not like recipient.
Remote host said: 550 not local host mydomain.net, not a gateway
Giving up on 198.87.210.123.

Another:

Remote server rejected mail for recipient - 550 not local host
mydomain.net, not a gateway

<user@mydomain.net>

ASKER CERTIFIED SOLUTION

Mestha

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

glenmetz

ASKER

I think you've got this figured out. There are 2 MX Lookups records for my domain (takeform.net). There are 2 IP address listed. 24.105.176.233 is correct and the proper domain, the other one (198.87.210.123) is not. That IP is also the one showing up as bad. Calliing our hosting company now.

glenmetz

ASKER

Thanks so much. Webhosting company had multiple MX records for our domain. Had them remove false ones, and we've been fine since.