Schulz Consulting

Consulting and Upgrades

  • Home
  • Services
  • Contact

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

June 3, 2022 by Wayne Schulz

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

Share this:

Filed Under: Sage 100 ERP

Secure cloud hosting for Sage 100
Call 1-888-244-6559 (toll-free)

About Wayne Schulz

Wayne Schulz is a Sage 100 Consultant located in Connecticut. He has worked with Sage 100 since 1986 and provides advanced support to companies located throughout the United States. If you are experiencing an issue with Sage 100 and would like to schedule a support session - please request assistance here or call 860-657-8544.

Access Sage 100 in the cloud today. 3rd party applications supported Available 24/7 from anywhere. Dedicated hosts

Call 1-888-244-6559 (toll-free)

Search Our Site

Sage 100 Newsletter

Sage 100 News

  • When Will Sage 100 2023 Be Released?
  • Sage 100 Updated TLS 1.2 Licensing Requirements ( February 2023 )
  • Shipment Tracking Functionality Restored to Sage 100
  • How To Edit 1099 Totals In Sage 100
  • How to Reconcile Sage 100 Accounts Payable Detail to the General ledger
  • Sage 100 Year-End 2022 Training Series
  • Minimum Sage 100 Versions for E-Filing for Tax Year 2022
  • What Are The Differences Between These Sage Fixed Asset Versions: Lite, Single-User, Network and Premier?
  • Sage 100 Paperless Email Electronic Delivery Failing With Rackspace
  • How To Check Sage 100 Compatibility with Avalara’s TLS 1.2 Requirement

Contact Us

Schulz Consulting
Connecticut Office
Click Here To Contact Schulz Consulting
Email Us
Available remotely nationwide.
We are a local branch of DSD Business Systems Connecticut.

Copyright © 2023 · Parallax Pro Theme on Genesis Framework · WordPress · Log in