Using Microsoft Exchange As An Smtp Server - Geist Upgradable PDU Instruction Manual

Using Microsoft Exchange as an SMTP server

If your facility uses a Microsoft Exchange email server, it can be used by the IMD PDU to send Alarm
and Warning notification emails if desired. However, the Exchange server may need to be configured
to allow SMTP connections from the unit first, as later version of Exchange often have SMTP services or
basic authentication disabled by default. If you encounter difficulties in getting your IMD PDU to send
emails through your Exchange server, the following notes may be helpful in resolving the problem.
First, since the IMD PDU cannot use IMAP or Microsoft's proprietary MAPI/RPC Exchange/Outlook
protocols to send messages, you will need to enable SMTP by setting up an "SMTP Send Connector"
in the Exchange server. More information on setting up an SMTP Send Connector in Exchange can be
found at this Microsoft TechNet article:
Next: Your Exchange server may also need to be configured to allow messages to be "relayed" from
the monitoring unit. Typically, this will involve turning on the "Reroute incoming SMTP mail" option in
the Exchange server's Routing properties, then adding the IMD PDU's IP address as a domain which
is permitted to relay mail through the Exchange server. More information about enabling and
configuring SMTP relaying in Exchange can be found at this Microsoft TechNet article:
http://technet.microsoft.com/en-us/library/dd277329.aspx
The SMTP "AUTH PLAIN" and "AUTH LOGIN" authentication methods (also known as "Basic
Authentication) for logging in to the server are often no longer enabled by default in Exchange; only
Microsoft's proprietary NTLM authentication method is enabled. The AUTH LOGIN method which the
IMD PDU requires can be re-enabled as follows:
1. In the Exchange console under server configuration, select hub transport.
2. Right-click the client server, and select properties .
3. Select the authentication tab.
4. Check the Basic Authentication checkbox.
5. Uncheck the Offer Basic only after TLS checkbox
6. Apply or save these changes, and exit. Note that you may need to restart the Exchange service
after making these changes.
Finally, once you have enabled SMTP, relaying, and the AUTH LOGIN Basic Authentication method, you
may also need to create a user account specifically for the IMD PDU to log into. If you have already
created an account prior to enabling the SMTP Send Connector, or you are trying to use an already-
existing account created for another user, and the IMD PDU still cannot seem to connect to the
Exchange server, the account probably did not properly inherit the new permissions when you enabled
them as above. This tends to happen more often on Exchange servers that have been upgraded since
the account(s) you are trying to use were first created, but can sometimes happen with accounts when
new connectors and plug-ins are added regardless of the Exchange version. Delete the user account,
then create a new one for the monitoring unit to use, and the new account should inherit the SMTP
authentication and mail-relaying permissions correctly.
If none of the above suggestions succeed in allowing your Geist IMD PDU to send mail through your
Exchange server, then you may need to contact Microsoft's technical support for further assistance in
GM1157
NOTE
These suggestions only apply if you are using your own, physical Exchange
server! Microsoft's hosted "Office365" service is not compatible with the
IMD PDU using firmware versions prior to v3.0.0, as Office365 requires a
StartTLS connection. Firmware versions 3.0.0 and beyond have support for
StartTLS and are compatible with Office365.
http://technet.microsoft.com/en-us/library/aa997285.aspx
Chapter 4 - Final Checkout 71
© 2017 Geist