Esko Logo Back to Esko Support
Choose your language for a machine translation:
Skip to end of metadata
Go to start of metadata

 

Summary

Google changed security settings on its mail service, moving from encryption of type SHA-1 to SHA-256. Unfortunately, Automation Engine is not ready for this yet, hence mails sent through Automation Engine by Google (Gmail) senders will fail if the Google sender account doesn't have the Access for less secure apps option enabled.

Symptoms

Send E-mail task fails either with error "The address specified is not a valid RFC-5321 address" or with the one shown below:

com.barco.bg.core.server.gen.mail.M_EAuthenticationFailedException: 534-5.7.14 <https://accounts.google.com/ContinueSignIn?sarp=1&scc=1&plt=AKgnsbuUw
534-5.7.14 v19gNWjcEurC2eJpwwLYb8gPNkgV0lHSGx9eEh4lYDrIMZoJPC_3cl8Sy2-lOAj6RB5sW1
534-5.7.14 Sa43BfQassU3eM5iWR8JvciGhodf7Vbikkj6tExmZS9sgbB0gZiXM4Jr4c8ZXxXviXbEmt
534-5.7.14 X9Hni9MWOZ6rV11Uvyl1zqq1p0ejOuX6_7xaxo_HQiwQAfkKB6pXKAaxx5_0P6m6N7zWwo
534-5.7.14 AmwlOlU5DSVasvmS77t-YDUz-Y1s> Please log in via your web browser and
534-5.7.14 then try again.
534-5.7.14  Learn more at
534 5.7.14  https://support.google.com/mail/answer/78754 l78sm34247073wmb.5 - gsmtp

Workaround

Enable the setting Access for less secure apps in the sender's (from) Google account.

You can find more information about this setting here.

Article information
Applies to

Automation Engine all versions

Created05-Nov-15
Last revised12-Nov-15
AuthorJOCA
Case Number00556102
Contents