Hi Uzoma,
We had issues with the maileater in the past after our smtp security and port usage was changed in our exchange environment.
Issues remain even after upgrade SDM to 14.1
After all I found the root cause to our problem in researching following CA Support technical documents:
http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec489174.aspx
Additional Information:
TEC1867631
Unable to connect Maileater to mail server via SSL Port 995
TEC1911912
Connecting Maileater to Office 365 Mail
TEC1701083
Using MS Office 365 with SDM Maileater functionality.
http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1911912.aspx
Save the root certificate from the post-login page as a base 64 encoded .cer file, and copy it to the primary server
http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1867631.aspx
SDM 14.1, Windows/Linux environment, connecting to a mail server over POP3/IMAP on SSL Port 995
Maileater (even in SDM 14.1) cannot use ports 993 and 995.
For Maileater and Service Desk, the correct port to use is port 110 or 143 for TLS.
Port 995 for SSL is not supported for Maileater.
The reason is because Maileater is designed to initiate a non secure based connection, then start a TLS connection.
In our exchange environment we cannot use port 110 but 143 and TLS MUST be used.
Maileater worked again after defining the following in SVD/Administration – Email – Mailboxes settings:
- Name : ITServicedesk.MailEater@barco.com
- Email Type : IMAP4 (must be IMAP4)
- Hostname : .....barco.com
- Port Override : 143 (must be port 143)
- User Name : …SDMAILEATER…
- Security Level : NTLM (must be NTLM)
- Allow Anonymous : No
- Use TLS : Yes (must be Yes)
- CA Certificate Path : D:/.../BarcoCertificate/root.cer (must use forward slash, naam of the file must be in the path)
Hope this helps,
Regards,
Jan.