[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now


Unable to get external SMTP relay to work in Exchange 2010

Posted on 2011-02-17
Medium Priority
Last Modified: 2012-05-11

Since migrating to Exchange 2010 a few days ago, I have been unable to get outside SMTP access to work for my smart phone users.  I know it's probably related to the rc've connectors and/ or port forward settings on my firewall.  I have tried a number of things, but have been unsuccessful.  Pop works fine and I have been able to get an outside Outlook client to send SMTP traffic over port 587 succesfully, but haven't been able to get to work on a Windows Mobile, iPhone or Blackberry. Here's my setup and some things I have tried:

Adtran Firewall has a port forward setting to flow Port 25 to a Barracdua and then it flows on to my Exchange 2010 box.  Adtran Firewall has port foward setting to send port 80, 443, 990, and 587 directly to Exchange box.  OWA access, POP and SMTP setup on external Outlook client pointing to port 587 all work fine.  The Default Rc've connector is setup for all IP's.  For authentication, TLS, Basic, Offer Basic after TLS, Exchange, and Integrated Windows authentication are all checked.  For Perm groups, all except Partner is selected.  The Client Rc've connector is setup the same.  I do have another Custom Rc've connector that I setup to allow my App svr to relay mail.  It is limited to rc've only from the IP address of the App svr though and should not be conflicting with anything.

I can send email from my Win Mobile phone to my internal domain successfully, but when I try to send them to other domains, I get the error 550, No such domain at this location.  I would look at using ActiveSync, but I am using a Self-signed cert.  I may get a 3rd party cert in the future, but I just need to get the SMTP working for mobile users for now.  I have tried different SMTP and SSL settings on my phone and have tried to play with settings on the rc've connectors, but have not been able to resolve yet.  I have researched the 550 error, but have not been able to find a solution that has helped me.  Thanks in advance for your help.
Question by:rkarnosh
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
LVL 47

Expert Comment

by:Craig Beck
ID: 34916224
Microsoft recommend creating a new connector for mobile clients... (written for Exchange 2007, but the same for 2010)...

Open the Exchange Management Console (EMC)
Navigate to Server Configuration, Hub Transport and select the HT server
Click New Receive Connector from the Action pane
Give the new Receive Connector a name such as, "Mobile Clients"
Select Client as the intended use for this receive connector and click Next
Click Next to allow all remote networks to use this receive connector
Click New to create the new Receive Connector
Now open the properties of the Mobile Clients connector
Click the Network tab and notice that the port the connector uses is 587
Click the Authentication tab. Ensure that Transport Layer Security (TLS), Basic Authentication, Offer basic authentication only after starting TLS, and Integrated Windows Authentication are checked.
Click the Permissions Groups tab. Ensure that only Exchange users is checked and click OK to close the properties window.

Author Comment

ID: 34916441
It would not complete the creation of the connector using the steps listed above.  The current Client Rc've connector that existed out the box conflicts with it.  When I try to create using the steps above, I get the following error:
Mobile Users

The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MSGSVR\Client MSGSVR". A Receive connector must have a unique combination of a local IP address, port bindings, and remote IP address ranges.

Am I missing something?
LVL 47

Expert Comment

by:Craig Beck
ID: 34916719
The Exchange Management Console is telling you that you have a connector already configured on the same IP with the same port number.

You could try removing the secure SMTP options from the Client Receive Connector and applying to the Mobile Users Receive Connector.
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.


Author Comment

ID: 34916841
I guess I don't understand why the current client connector would not work then versus the one being suggested since the current connector makes available the same IP's and ports, offers the same authentication types (and more), and offers the same permissions (and more, since all except partners is selected).  Is there something I am missing as to why a seperate connector with less authentiction types available and less permissions would help over the current Client connector?


Accepted Solution

rkarnosh earned 0 total points
ID: 34980107
I setup my iPhone users with ActiveSync successfully.  I need to install the cert for WM6 to be able to use active sync.  I will just abandon my attempts to get SMTP to relay and use activesync.

Author Closing Comment

ID: 35015427
No other usable solutions were given

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question