Option three: setting up multiple smtp connectors, Test outbound mail, Troubleshooting – Google Outbound Services Configuration Guide User Manual
Page 58

62
Outbound Services Configuration Guide
3.
Click OK to save the changes and close the SMTP Connector properties.
Option Three: Setting Up Multiple SMTP Connectors
Another alternative, rather than configuring the smart host in the SMTP Virtual
Server, is to use two or more SMTP Connectors and configure the them to share
the mail flow load in a load-balanced fashion. This is an advanced configuration
and should be carefully considered and thoroughly researched before being
attempted.
Test Outbound Mail
Once you have set up your smarthost, test that your configuration is correct and
mail is flowing normally.
Test the configuration.
1.
Go to the Queues tab in Internet Mail Service Properties. Items with a retry
state could indicate outbound mail delays.
2.
Send a message from a mail client inside your network to an outside address.
You should see a line in the header email which indicates being received and
delivered by
exprodNobM.obsmtp.com
, where N and M are numbers.
3.
Test inbound mail to confirm normal functionality. Send a message from an
outside email address to an address on your service.
4.
In the Administration Console, select your email config organization and click
the Outbound Servers tab. After a minute of successful mail flow, traffic
should display on the graph.
5.
Confirm that your mail server is not an open relay. An open relay will make
your mail server vulnerable to hijacking from spammers and will most likely
cause an interruption in service.
Use an external open relay test, such as
http://www.mxtoolbox.com/
diagnostic.aspx
or
http://www.spamhelp.org/shopenrelay/
. If the result
shows that you have an open relay, correct your private relay settings. If you
see an uncertain response (such as “maybe” or “warning”) then check that
your private relay settings are correct.
See “Set Up Reinjection” on page 57 for the correct private relay settings.
Troubleshooting
Because Microsoft Exchange is a third party product, this document cannot
include complete troubleshooting steps. For further troubleshooting information,
see the Microsoft website: