Troubleshooting maileater connectivity issues when a TLS connection is enabled can be confusing. The purpose of this document is to address specific errors that you may encounter, their causes, and how to resolve them.
If maileater is not connecting when TLS is enabled, the first thing that you should do is to increase the logging level on maileater to get more details during the connection attempt. You can do this by running this command on the command line: "pdm_logstat -n pdm_maileater_nxd VERBOSE". You should run this long enough to see a string of messages beginning with "pdm_maileater_nxd 5784 TRACE pdm_maileater_nxd.c 4767 Scheduled Mail Poll has been signalled.", and ending with "pdm_maileater_nxd 5784 ERROR pdm_maileater_nxd.c 5009 Mailbox 400002 ([email protected]/Inbox) produced error during Mail Poll." Once this is complete, you should run "pdm_logstat -n pdm_maileater_nxd" to disable the logging and prevent excessive messages from being written to the logs. Then you can look for these specific errors in the logs to tell you what issue may be occurring during the connection:
<Please see attached file for image>
src="/servlet/servlet.FileDownload?file=0150c000004AJpXAAW" alt="wireshark CA cert error.JPG" width="623" height="120"><Please see attached file for image>
src="/servlet/servlet.FileDownload?file=0150c000004AJpYAAW" alt="wireshark CA cert good case.JPG" width="656" height="340">
You can verify that the mail server is set up to use STARTTLS over IMAP using the following command: "openssl s_client -starttls imap -connect email_server:143 -showcerts -starttls imap". This should produce about a page of output, including the certificate that you need to use with maileater for TLS to function properly. You can verify that the contents of your certificate file match the output of this command starting with "-----BEGIN CERTIFICATE-----", and concluding with "-----END CERTIFICATE-----"
If you have additional issues that are not addressed in this document, please open a case with CA Support.