|
Question : Inbound emails not reaching our Exchange 2003 server.....
|
|
We've got an Exchange 2003 server that will not receive mails from a newly defined email domain, from the outside. In our default recipients policy, we have about six email domains that this exchange server excepts mail for. I've created a new one, the same way that I've created all the rest. I can send/receive mail to/from an account with that new address defined as their default internally, no problem. From that same account, I can send externally to anyone, no problem. When that external account tries to reply, or send fresh, they get this message:
553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)
We have a hosting site that manages an SMTP smarthost, and sends inbound emails to a defined host name, that is NAT'd to our Exchange server. All of the previously mentioned email domains are serviced in the same way. If you do an MX query against all of these domains, including the new one, you get the same server, so it looks like everything is consistent.
Does anyone have any ideas? Questions?
Thanks!
|
Answer : Inbound emails not reaching our Exchange 2003 server.....
|
|
mail.ofc-wic.com is not an Exchange server. It doesn't respond like an Exchange server, it doesn't except the commands an Exchange server does. The error it is giving is not an Exchange response.
telnet to maila.microsoft.com on port 25 - that will show you how an Exchange server should respond.
Simon.
|
|
|
|