MuleSoft · Email Connector
EMAIL:AUTHENTICATION
Short answer
EMAIL:AUTHENTICATION means authentication against the mail server failed. For Gmail with two-factor authentication, use an app-specific password instead of the account password.
VerifiedLast verified
01Error text
Error type: EMAIL:AUTHENTICATION02Likely causes
- Authentication failed.
- For Gmail, an account with two-factor authentication needs an app-specific password. Without two-factor authentication, the docs say to enable "Less Secure Apps" in the Gmail account.
03How to fix it
- Check the user and password on the email connection configuration.
- For Gmail with two-factor authentication, create an app-specific password and use it.
- If the password still fails for Gmail, use Google's unlock captcha page that the docs link to, then run the flow again.
- Turn on connector logging: in
log4j2.xmladd<AsyncLogger name="org.mule.extension.email" level="DEBUG" />. - For protocol detail, add
<email:property key="mail.debug" value="true" />to the IMAP or SMTP connection element. - Handle the failure with an error handler of type
EMAIL:AUTHENTICATION.
04Official documentation
→Related errors
- EMAIL:INVALID_CREDENTIALSEMAIL:INVALID_CREDENTIALS means the username and password parameter consistency check failed. Check that the user and password on the connection are both set correctly.
- EMAIL:CONNECTIVITYEMAIL:CONNECTIVITY means a connection to the mail server could not be established. Check the host, port and TLS settings on the connection, then read the JavaMail debug output.
- EMAIL:SSL_ERROREMAIL:SSL_ERROR means the SSL context could not be created, or the TLS context is not configured properly. Review the TLS context on the secure email connection.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer