...

Full details for this configuration can be found in emailAccount Email Account, but in this article we will cover some common examples.

...

Full details for this configuration are in fileCollector File Collector, but in this article we will go through a typical set up which should cover most cases.

...

Anchor
emailAccountTroubleshooting emailAccountTroubleshooting

Troubleshooting

...

Authentication Errors

The error below indicates that a successful connection has been made to the mail server, on the correct port and protocol, but one or more of several possible authentication errors has occurred:

1. Incorrect Password. As well as checking the password is correct, ensure no special characters are being used such as ampersand as these seem to cause this error.
2. Incorrect Username. Double-check that the username is the actual mailbox name as setup on the mail server and not the alias or email address, which may sometimes be different. 
3. Cannot authenticate. In some cases, the details are correct but the server is refusing to allow authentication to take place, due to the authentication protocol being used. This For example, this error is received when attempting to connect to Google Mail because Google requires the username and password to be supplied in an OAuth token.

...

Timeout / Incorrect Port Error

The error below typically appears are after a delay of up to 1 minute and normally indicates the port number being used is the wrong one for the type of operation. For example, you receive this error if trying to send mail using a CenterView Account on port 995 instead of 587.

Incorrect Host or Port Error

The error below appears again if the port number is incorrect, but this is typically if the port is not in use at all. For example, this error is received when attempting to send mail using a CenterView account on port 586 instead of port 587. This error also occurs if the host name is incorrect, for example if attempting to send mail using a CenterView account to smtp.office364.com on port 587, instead of smtp.office365.com.

No Secure Connection

The error below usually occurs if attempting to authenticate without sending the username and password via an encrypted tunnel, when the server requires one. This error is essentially saying says that no authentication details were provided, because the mail server is rejecting to allow not allowing them to be sent in plain text. This can usually be resolved by supplying the two properties in the configuration: 

mail.smtp.auth=true

Which which says that authentication will be used and;

mail.smtp.starttls.enable=true

Which which creates a secure / encrypted connection , before sending the authentication details.

Related articles

...