We have clientes connecting externally via POP3 with Outlook Express. Prior to installing the Edge Transport server the clients could send and receive mail without issue. Once the Edge server was put in place the clients can receive but can no longer send to any external domains. However, clients within the organization connecting to the Exchange Server with Outlook can send mail to external dominas without issue. Clients outside of the organization can connect through OWA and send email to external domains without issue. The clients get the "550 5.7.1 Unable to relay" message. Any suggestions would be appreciated.
We have used the Set-ReceiveConnector permissions and this has not resolved the issue.
What settings should be checked on the send connector. Everything worked up until an Edge Server was introduced. We have since taken the Edge server out but still have the same problem. Thanks!
Posts: 15
Joined: 18.Apr.2005
From: Hong Kong
Status: offline
We are having the same problem. We are using all roles on a single server. How, where we can enable a setting for smtp relay for external POP3 users? Has someone done it?
Error: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)
Can someone please guide how we can allow authenticated users to successfully send the emails externally?
Posts: 15
Joined: 18.Apr.2005
From: Hong Kong
Status: offline
Finally it is working. The client connector for POP3 applications listen by default on port 587. so make sure when you setup the outlook the smtp port is 587. Also use your username and password for the smtp authentication. If you make any changes to the Receive Connector properties, make sure you restart the Hub transport service and test your settings.
Finally... after days of struggling with this I was finally able to get this issue resolved.
I am currently running an Exchange 2007 server as well as an Edge Transport Server.
The problem I was having was a program that we use generates automated notification emails that were being sent to internal email addresses as well as external (hotmail, Gmail, yahoo) email address. The internal address were receiving the notifications without issue, unfortunately the same wasn’t true for the external address. My first troubleshooting step was to check the logs and event viewer to see if I could find some clue as to why these emails were failing. That turned out to be an extreme waste of time. Next, I logged into the server where the emails were being sent from and began using telnet to troubleshoot. This was the biggest help to me in figuring this issue out. Here is the link that I followed: http://support.microsoft.com/kb/153119
Testing with telnet now, as soon as I hit enter on the “RCPT TO:email@domain.com” command I would constantly get the “550 5.7.1 Unable to relay” error message. To fix this I followed the steps in this link that was provided by shijaz. http://msexchangeteam.com/archive/2006/12/28/432013.aspx (I used option 1) The thing that they forget to mention in this article and what I think is critical to your success in this operation is to restart the “Microsoft Exchange Transport” service. If you don’t restart the service this will not work. Trust me, I know from experience. Thanks to hkboy for pointing out that little gem. The restart of this service only takes about 15 seconds so your users shouldn’t notice any interruptions in service. After restarting the service I also did a start-edgesynchronization command from the EMS console on my Exchanges server since I am running an Edge Transport server. I’m not sure if this step is needed but it couldn’t hurt. After all of this, I went back to my telnet client and was able to successfully send external email through Exchange!
Thanks to everybody who posted on this issue. Thanks to your posts I was able to piece together a solution that worked for me. I now hope that my post will help another admin avoid the gray hair that troubleshooting this issued caused me.