Mail fetching issue_Remote host closed connection during handshake

Mail fetching issue_Remote host closed connection during handshake

GUI Error Trace: 

FAILURE :E-mail settings saved successfully. But error occurred while trying to check connection with mail server - Problem connecting to mailbox.


LOG TRACE:

[16:33:06:197]|[11-09-2018]|[SYSERR]|[INFO]|[120]: javax.mail.MessagingException: Remote host closed connection during handshake;
nested exception is: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake| 

Please check do the basic ping and telnet tests as shown below. If the results are successful, but the issue persists and if you are using Exchange server you can try the below steps to fix it.

ping <incoming server name> -t

telnet <incoming server name> <port>

Open the Exchange Management Console and Execute the following command

Get-ServerComponentState -identity Servername

You will notice that the IMAPProxy state is set as inactive

To resolve this issue you must perform the following

Open the Exchange Management Console and Execute the following command

Set-ServerComponentState -Identity Servername -State Active -Requester HealthAPI -Component ImapProxy

Now, check if you are able to save the mail server settings and start the mail fetching process. If that did not help, restart the application and check the issue.

If the issue still persists, kindly seek assistance from your mail server team to perform the command as, it is a mail server issue and not an application issue..





                    New to ADSelfService Plus?

                      • Related Articles

                      • Mail fetching - deleted flag issue

                        This message will be thrown, when you have provided a shared mailbox. The concept here is, SDP MSP reads the mail from the configured mailbox and adds it as a request. During the time, if some other application fetches the mail from the same mailbox ...
                      • List of mail fetching issues and solutions

                        Scenario 1 : Mail fetching issue due to Invalid or No PKIX certificate .   Log traces for Mail Fetching  issues Exception when connecting to store.|javax.mail.MessagingException: sun.security.validator.ValidatorException: PKIX path building failed: ...
                      • Mail Fetching: Inline Images Dropping Due to Invalid Extension

                        Issue: The inline image's file name from the email doesn't contain the extension. Example: filename = sys_attachment.dosys_id=5bb0751c8303b5dc96a238226daad371 As a result, the inline image gets stripped during the mail fetching process. The sender of ...
                      • EWS Mail fetching issue - Proxy not enabled for ews. isIncoming: true

                        Issue: EWS Mail fetching issue using different tenants Error trace 1: [23:30:20:701]|[01-23-2023]|[com.adventnet.servicedesk.common.MailUtilities]|[INFO]|[73]: Proxy not enabled for ews. isIncoming: true| ...
                      • Failure during Zia Reopen prediction process stops the mail fetching schedule

                        When the requester replies to closed/resolved requests with empty content or if there is no proper content except the content of the parent mail, then no content will be available for zia reopen prediction process and an exception will be ...