Mail Fetching Troubleshooting

Mail Fetching Troubleshooting

 

    1. Unable to fetch mails into SupportCenter Plus as the ports are being blocked by Firewall/Antivirus.

    2. Is it important to configure an SSL Certificate to use POPS/IMAPS for fetching mails?

    3. Authentication and Configuration Errors:

    • Settings saved successfully but an error occurred while trying to check the connection with mail server - Authentication Failed using the given username and password.

    • Email settings saved successfully but an error occurred while trying to check the connection with mail server – Problem connecting to the mailbox.

    4. If the mailbox is hidden from the address book, then authentication failure occurs and mails cannot be fetched into the application.

    5. Processing from Mail Server

    • Password length is greater than the expected value.

    • Unable to fetch mail as Plain text authentication is disabled in the mail server

    • Error when encrypted mode is enabled with POP protocol. 

 

1. Unable to fetch mails into SupportCenter Plus as the ports are being blocked by Firewall/Antivirus.

 

Firewall Blocking Ports

 

Possible Causes: (one or many)

 

a. The Software/Hardware Firewall blocks the POP/IMAP port.
b. The IP Address of the server on which SupportCenter Plus is hosted, is blocked by either an anti-virus program or firewall or both.

Error trace in logs:

javax.mail.MessagingException: Connect failed;

nested exception is:

java.net.ConnectException: Connection timed out: connect

 

Solution:

 

You can follow these steps to check if firewall is blocking the port.

  • Open Command Prompt and type,

  • cmd> telnet [mailservername] 110

 

For example,

  • cmd> telnet mail.google.com 110



If you receive an error as in the above image, then port 110 is being blocked by either the anti-virus program or the Windows firewall or both. Also, there possibility of incorrect mail server or port number or both.

 

Information required for analysis:

 

Support Tab --> Support File

 

2. Is it important to configure SSL Certificate to use POPS/IMAPS for fetching mails?

 

Secured Socket Layer

 

Cause:

 

If the SSL Certificate in the mail server is a self-signed certificate, then it is not imported into SupportCenter Plus Java environment when using the POPS/IMAPS protocol.

 

Error Trace in logs:

 

javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target|

 

Solution:

    1. Download the file from the link given below and extract it to the SupportCenter Plus Home directory.
    https://uploads.zohocorp.com/Internal_Useruploads/dnd/ServiceDesk_Plus/2016_02_03_11_25_23_o_1acqu0dua1tidbq1kni1llri9g1.tar.gz

    2. Run the Extracted batch file from the command prompt using the syntax given below.
    syntax:- gencert.bat (hostname):(port)
    eg:-
    cmd> gencert.bat scpexchnage.com:995

    3. You will receive an exception PKIX. On supplying the value 1, a file called jssecacerts is generated in the SupportCenter Plus Home Directory.

    4. Copy the jssecacerts file under jre\lib\security folder and restart SupportCenter Plus application.

    5. Save the settings and then start the mail fetching.

Information required for analysis:

 

Support Tab --> Support File

3. Authentication and Configuration Errors:

    1. Settings saved successfully but an error occurred while trying to check connection with mail server - Authentication Failed using the given username and password.

    2. Email settings saved successfully but an error occurred while trying to check connection with mail server – Problem connecting to mailbox.

Cause:

The error occurs due to one or both of the following.

  • The configured username or password in the Mail Server Settings is incorrect.

  • the SupportCenter Plus server is unable to communicate with the mail server.

 

Error trace in logs:



javax.mail.AuthenticationFailedException: Bad login

 

Solution:

    1. Check the connection with the mail server.

    2. Check if the given username and password are correct under Admin>> Mail Server Settings>>Incoming >>Save Settings.

    3. Then, cmd> telnet “ip address” “port number”

 

Protocols Used: Incoming are POP – 110, IMAP- 143

 

cmd>telnet sdplinmail 110 (POP)
>user "sd-test2"
>ok
>pass "scp"
>ok

Incorrect password when using POP



cmd> telnet 192.168.113.120 143 (IMAP)

> a1 capability
> a2 login "username" "password"
> a3 inbox mail-box-name

 

Incorrect password when using IMAP

 


 

cmd> telnet 192.168.113.120 993 (IMAPs)

> a1 capability
> a2 starttls
> a3 login "username" "password"
> a4 inbox mail-box-name

 

Information required for analysis:

 

Support Tab --> Support File

 

4. If the mailbox is hidden from the address book, then authentication failure occurs and mails cannot be fetched into the application.

 

Hidden Mailbox

 

Cause:

 

The mailbox is hidden from the address book which leads to failure in Authentication and hence mails cannot be fetched into SupportCenter Plus.

 

Error trace in logs:

 

[09:26:51:740]|[04-09-2009]|[com.adventnet.supportcenter.common.MailUtilities]|[INFO]|[26]|: Obtained mail store from session.|
[09:26:52:068]|[04-09-2009]|[SYSOUT]|[INFO]|[26]|: Check if the username and password are correct|
[09:26:52:068]|[04-09-2009]|[SYSOUT]|[INFO]|[26]|: javax.mail.AuthenticationFailedException: AUTHENTICATE failed.|
[09:26:52:068]|[04-09-2009]|[SYSOUT]|[INFO]|[26]|: at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:474)|
[09:26:52:068]|[04-09-2009]|[SYSOUT]|[INFO]|[26]|: at javax.mail.Service.connect(Service.java:275)|

 

Solution:

 

The mailbox should be found in the address book which will allow mail fetching to start.

 

    1. Open Active Directory Users and Computers.

    2. Open the Properties dialog box for the user account.

    3. On the Exchange Advanced tab, select the Hide from Exchange Address Lists checkbox.

 


 

Information required for analysis:

 

Support Tab --> Support File

 

5. Processing from Mail Server

 

    1. Password length is greater than the expected value.

    2. Unable to fetch mails as plain text authentication is disabled in the mail server

    3. Error when encrypted mode is enabled when using POP protocol.

 

a. Password length is greater than the expected value.

 

Error trace in logs:

 

Error when processing. SO RETURNING...|com.adventnet.authentication.PasswordException: Length of the new password is greater than expected value of : 100

For any Mail fetching issue, check for the string "SO RETURNING..." Few lines above or below the line, which contains this string, should give more information on the error trace.

 

Reason:

 

When a mail arrives, SupportCenter Plus will try to create a new user with the user name and password same as the email address and in this case, since the email address is very long it cannot be added to the database and throws the error message. -- Length of the new password is greater than expected value of :100

 

b. Unable to fetch mail as Plain text Authentication is disabled in the mail server.

 

Error trace in logs:

 

javax.mail.MessagingException: No login methods supported!;

nested exception is:

com.sun.mail.iap.ProtocolException: No login methods supported!|

 

Solution:

 

Enable plain text login in Microsoft Exchange server and follow the steps given below to configure the IMAP service to use Plain Text Login.

 

 

    1. Open Exchange Management Shell from Start -> Programs -> Microsoft Exchange 2007.

    2. Enter the following In the shell,
    set-POPsettings –logintype plaintextlogin

    3. Press Enter.

    4. From the Services panel restart the Microsoft Exchange Information Store service.

Information required for analysis:

 

Support Tab --> Support File

 

c. Error when encrypted mode is enabled with POP protocol.

 

Cause:

 

Unable to fetch email when encrypted mode is enabled when using POP protocol.

 

Error trace in logs:

 

javax.mail.AuthenticationFailedException: Command is not valid in this state.

 

Solution:

 

Reset the password format on the exchange server to the Normal format. This can be done by running a query on the exchange server shell.

 

Follow the steps below to configure the IMAP service to use Plain Text Login:

 

    1. Open Exchange Management Shell from Start -> Programs -> Microsoft Exchange 2007.

    2. Enter the following In the shell,
    set-POPsettings –logintype plaintextlogin

    3. Press Enter.

    4. From the Services panel restart the Microsoft Exchange Information Store service.

 

Information required for analysis:

 

Support Tab>>Support Files

 

 


 

Information required for analysis:

 

Support Tab>>Support File

 


    • Related Articles

    • Mail Server Configuration

      Mail server configuration is essential to receive requests via email, send notifications, surveys etc. This is a portal-specific configuration.  To configure a mail server, go to Admin > Main Settings > Mail Server Settings.   Configuring Settings ...
    • OAuth Authentication for Mail Server

      Introduction   OAuth is a standard authorization protocol that provides delegated access to a protected resource using web tokens instead of passwords. With OAuth, resource owners can configure separate permissions for each client requesting access ...
    • FAQs on OAuth Authentication for Mail Server

      Why should I move to OAuth2.0?  Google and Microsoft will soon withdraw basic authentication support for mail servers by February 2021 and October 2020, respectively. Therefore, it is advisable for users to switch to OAuth authentication. What are ...
    • OAuth for Mail Server Configuration

      Introduction   OAuth is a standard authorization protocol that provides delegated access to a protected resource using web tokens instead of passwords. With OAuth, resource owners can configure separate permissions for each client requesting access ...
    • Database Error Codes and Troubleshooting

      The following table provides common database errors and corresponding troubleshooting tips. Error ID   Error Root cause and troubleshooting steps 1000 ERROR_WHILE_GETTING_CONNECTION Root cause: Connection could not be established with the MSSQL ...