Link to home
Create AccountLog in
Avatar of Barnett Computers
Barnett ComputersFlag for United States of America

asked on

Exchange 2010 Setup

We have installed a new SBS2011 Standard server for a customer.  Software installation completed without any known issues.  User accounts and mailboxes have been added.  When their old server crashed, they used the AppRiver Exchange 2010 service to keep e-mail access while the new server was setup and installed.  When the Exchange setup was completed, the AppRiver support team used telnet commands to test sending messages to the new server.  Telnet, “ehlo”, and "mail from:"  commands work OK.  When the telnet "rcpt to:" command is entered, the reply is "550 5.7.1 Unable to relay."  This command has been tried with more than one e-mail address.  We did get the command to work one time when we entered a range of 0.0.0.0-255.255.255.255 in the receive connector.  Is this acceptable or are we opening the door for more problems?

Receive and send connectors have been created.  The receive connector uses I.P. addresses supplied by AppRiver.  We have checked the receive connectors and they appear to be correct.  The permission groups checked are Anonymous and Exchange users.  We are wondering if some question or configuration was missed or entered wrong during the server or Exchange setup.  

What do we need to check to resolve the “Unable to Relay” issue?  Is there a checklist or reference document we can use to verify the Exchange server configuration?  Is there a “tool” that can check Exchange and identify problems?

I would also appreciate any suggestions on testing both receiving and sending messages before the AppRiver service is stopped.  We would like to know everything is working before redirecting the mail to the new server.

Any suggestions will be appreciated.
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Unless you filtered addresses from which SMTP traffic can be accepted there should be no restrictions.  You need to be careful about modifying the receive connectors as you could end up as a mail realy for anoymous senders.  Best bet is to test you configuration with Microsoft's Exchange Connectivity Tester:
https://www.testexchangeconnectivity.com/
SOLUTION
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of Barnett Computers

ASKER

I'm not familiar with the connectivity tester.  We will run this test.  Anything we need to notice while it is running?

The wizard was used for setup.  We thought everything looked good until the telnet test was run.  Is telnet a good test to indicate the e-mail will work?

Thanks for the replies.  We will run the connectivity test but may not be able to post results until after the holiday.
ASKER CERTIFIED SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
I consider all replies helpful in resolving the issue.  Since the tech that helped identify the "A" and "MX" issues did not participate through EE, I'm giving credit in this section.