Sage 100 Paperless Electronic Delivery Via Gmail Requires App Password or OAuth Starting May 30, 2022

Beginning May 30, 2022 if you are using a non-Workspace GMAIL.COM email account to send forms using Sage 100 electronic delivery then you may need to make a change to your outgoing email SMTP login.

According to the Google website:

To help keep your account secure, from May 30, 2022, ​​Google no longer supports the use of third-party apps or devices which ask you to sign in to your Google Account using only your username and password.

Important: This deadline does not apply to Google Workspace or Google Cloud Identity customers. The enforcement date for these customers will be announced on the Workspace blog at a later date.

If you are using a regular ( non-Workspace ) Gmail.com email then you may need to (A) create an app specific password or (B) use OAuth 2.0 to login to your Gmail.

Errors may not begin exactly on May 30, 2022 as Google will likely phase in these changes. Also, please note that Google is not yet applying these requirements to business Workspace accounts.

Using OAuth 2.0 with Sage 100

If you are using Sage 100 2021+ then the better solution to the above issue is to use OAuth 2.0. This is a more secure way to connect to Google for sending email.

Unfortunately Sage only added this capability to Sage 100 version 2021 and higher and it requires some confusing manual configuration.

To connect your Sage 100 v2021+ to Gmail using OAuth 2.0

• Open Company Maintenance and select Company Code
• SMTP (Mail) Server – Authentication Method = OAuth
• Address = smtp.gmail.com
• Port = 587
• SMTP Encryption = TLS
• User ID = User’s Gmail email address
• Client ID = Client ID obtained from Google Cloud Platform ( See Setting up OAuth 2.0 )
• Client Secret = Client Secret obtained from Google Cloud Platform ( See Setting up OAuth 2.0 )
• Auth End Point = https://account.google.com.com/o/oauth2/auth
• Token End Point = https://oauth2.googleapis.com/token
• Scope = https://mail.google.com/
• Redirect URI = http://localhost
• Redirect Port = 3017
• Code Challenge Method = None
• Select 128-bit Encryption for Password Protected Documents if 128-bit encryption is desired when password-protected documents are e-mailed

For more information on enabling OAuth 2.0 with Sage 100 please visit the following Sage knowledebase articles:

Using OAuth 2.0 with Sage 100