Cannot Send Emails or Invoices in Sage 100 Due to TLS Errors
Description
Cause
The email engine in Sage 100 2018 and earlier requires TLS 1.0.
TLS secures network communication, but versions 1.0 and 1.1 contain known security vulnerabilities. Major providers, including Microsoft, Google, Apple, and Cisco, no longer support these older protocols. They now require TLS 1.2 or higher for email transmission.
Resolution
Identify affected scenarios
You experience this issue if Sage 100 displays any of the following errors:
“Failed to read TLS record”
“Failed to read beginning of SSL/TLS record”
“Failed to establish TLS connection”
“Failed to read incoming handshake messages”
“Timeout waiting to read socket or accept connection”
You also experience issues when sending emails through Paperless Office Electronic Delivery under these conditions:
The SMTP provider disables TLS 1.0
You use Sage 100 2018 or an earlier retired version
Understand provider requirements
Most modern email providers now enforce TLS 1.2 or higher. This change started between 2020 and 2021 and continues across services.
Note: External links can change. Sage does not maintain third-party content.
Microsoft TLS 1.0/1.1 deprecation for Office 365
Microsoft Exchange Team Blog on TLS enforcement
Upgrade Sage 100
Sage 100 2018 and earlier
These versions do not support TLS 1.2 and cannot meet modern email security requirements.
Upgrade to a currently supported version of Sage 100
Sage 100 2019 and newer
These versions support TLS 1.2.
No additional downloads are required
Check other possible blockers
Other factors can prevent successful email delivery:
Unsupported TLS version
SMTP server configuration issues
Firewall or antivirus blocking required ports
Anti-spam or security policy restrictions
CAUTION:
Sage does not test every email provider or configuration. External systems control email delivery and can change without notice.