000016899 - AxM 6.1.4 - aserver down email notifications do not work

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000016899
Applies ToAny version of AxM 6.1.4 on any platform
Issue
AxM 6.1.4 - aserver down email notifications do not work

After populating the required parameters for email notifications in the dispatcher.conf to notify a selected user when the aserver goes down, those minimum settings, for example:
cleartrust.dispatcher.smtp.hostname=mail.mydomain.com
cleartrust.dispatcher.smtp.port=25
...and restarting AxM, no mail notifications are sent when the aserver is taken offline.
Cause
Your smtp mailhost must be defined as either an mx record in DNS, or with the alias mailhost in the local hosts file.
Resolution
First, check to see if an MX record is defined in DNS by doing the following lookup.  This example demonstrates on unix, but the exact same procedure can be run from the c:\ for windows verbatim.
bash-2.05# nslookup
Default Server:  mydnsserver.mydomain.com
Address:  192.168.131.196
> set q=mx
> mydomain.com
Server:  mydnsserver.mydomain.com
Address:  192.168.131.196
mydomain.com preference = 10, mail exchanger = mymailhost.mydomain.com
cindysworld.com nameserver = mydnsserver.mydomain.com
mymailhost.mydomain.com   internet address = 192.168.131.199
mydnsserver.mydomain.com        internet address = 192.168.131.196
If you do not have an mx record in DNS, you can add an smtp mailhost in the following format to the local hosts file (/etc/hosts on unix or c:\program files\system32\drives\etc on windows) until such time as the MX record is added:
192.168.131.196    mymailhost.mydomain.com mailhost.mydomain.com mailhost
Legacy Article IDa60720

Attachments

    Outcomes