Is there a way to change the timeout setting on the MailEater setup? We are getting an error that could possibly be from a timeout on our Office365 setup.
I think the Connection is dropped if the Client (ie., maileater in this case) doesn't start the TLS connection with in the "connect_timeout" period established on the Mail server. If you look into detailed traces, I'm guessing it would be 30 seconds or 60 seconds after the connection initiation, that you would see the Connection dropped error.
I believe 993 is SSL port, where as we need a non-SSL port for us to start communication and then start TLS encryption (if you have enabled TLS on the maileater). If you can get the non-SSL port, you can use that in the option maileater options.
Hope this helps
Can you clarify as to what timeout you are looking for specifically?
What is the error you are getting?
We've attempted setting up these settings twice with support and we're getting the same errors consistently. Support thinks it's something on our side, but everything on our side works outside of this SDM setup. We tried the settings that the Outlook365 setup says we should use, but they don't work either. If we put in the wrong credentials, we get an error of "System failure in Connect operation", but if we do our "outlook.office365.com" port 993 with TSL checked, we get "Connection Dropped". I didn't know if this could be related to a timeout issue.
08/21 16:10:12.08 LKMVBKGSDMTST1 pdm_maileater_nxd 1484 ERROR pdm_maileater_nxd.c 9590 Imap Mail: Failed to connect to IMAP server outlook.office365.com at port 993. Error (8) Connection dropped
08/21 16:10:12.08 LKMVBKGSDMTST1 pdm_maileater_nxd 1484 ERROR pdm_maileater_nxd.c 8375 Failed to connect to IMAP server outlook.office365.com at port 993.
08/21 16:10:12.08 LKMVBKGSDMTST1 pdm_maileater_nxd 1484 ERROR pdm_maileater_nxd.c 5003 Mailbox 400003 (*******@******.email@example.com/Inbox) produced error during Mail Poll.
Thank you Raghu for your response. I'm not sure what the setting exactly was in our environment that was making it difficult for us to connect to Office 365, but we have since moved it to an on-premise hosted email account and the issue doesn't persist. I'm assuming it was some setting we had blocking the connection.
Hi Kenneth - Did Raghu's response help you resolve your issue? If so please mark as Correct Answer. Thanks! Chris
Retrieving data ...