Often, on new installations, there are issues with OTM sending out email notifications to implementers, carriers, etc. In order to help troubleshoot these, I usually test the email relay server manually via telnet in order to ensure it is working.
First, get the email server that OTM is configured to use from the glog.properties file on the OTM app server. Look for the following parameter:
Code:
glog.mail.smtp.host=smtp.company.com
Also get the user that the OTM server is configured to send mail as from the same file:
Code:
glog.workflow.notify.advisor.email=GLogAdvisor@otm.company.com
For this example, we'll send a test email to
mavenwire@gmail.com. To test via telnet, run the following commands (marked in bold) from a DOS or Unix command prompt. Make sure to run these commands from the OTM App server, to test the connection as if OTM you were the OTM server.
Code:
telnet smtp.company.com 25
Connected to smtp.company.com.
Escape character is '^]'.
220 smtp.company.com ESMTP Sendmail Switch-2.2.8/Switch-2.2.8; Thu, 7 Jun 2007 01:01:01 -0500
HELO company.com
250 smtp.company.com Hello [otm.company.com], pleased to meet you
MAIL FROM: GLogAdvisor@otm.company.com
250 2.1.0 GLogAdvisor@otm.company.com... Sender ok
RCPT TO: mavenwire@gmail.com
250 2.1.5 mavenwire@gmail.com... Recipient ok
DATA
354 Enter mail, end with "." on a line by itself
Subject: Test email from OTM App server
This is a test email from the OTM App server. Wheeeeeeeee!
.
250 2.0.0 156K62L05857 Message accepted for delivery
QUIT
221 2.0.0 smtp.company.com closing connection
Connection closed by foreign host.
If relaying is denied, you'll see the following error:
Code:
RCPT TO: mavenwire@gmail.com
550 5.7.1 mavenwire@gmail.com... Relaying denied. IP name lookup failed [192.168.1.1]
Alternately, if you don't receive the email at the destined email box, the issue is likely with your mail server or some intermediary mail server and you can begin troubleshooting from there.
Hope this helps!
--Chris