KB 109844 indicates that emailing from Sage 100 is limited to TLS 1.0, and we're starting to see email servers stop supporting this insecure protocol. Today, one customer is having problems, using O365 email, and we suspect this might be the cause.
The KB article seems to have it's text truncated. Is there a timeline on when the hotfixes will become available? Looking at the release notes for 2018.6 and I don't see reference to this being corrected in the latest patch.
(I can see v2019 release notes show TLS 1.2 is supported, which is good, but we're wondering about v2017 / v2018 as indicated in the KB article as having a hotfix available "soon").
We have hosted exchange with Microsoft and Office 365 and have no issues.
That is good to know BL. Thanks. I believe today's customer is full O365 (smtp.office365.com) not hosted Exchange, but I don't know enough about M$ services to understand if that makes a difference.
The question to Sage remains though, since TLS 1.0 will eventually be fully depreciated, and some smaller email service providers are already blocking that protocol. I first noticed that KB article 29 days ago, and from what I see it has not been updated since.
outlook.office365.com port 587 TLS/Starttls is our setup
2018.4notes have a reference to updating Sage NA Sync Client to handle TLS 1.2.
I have no idea what the SAGE NA Sync Client is.
That is something else. v2019 release notes reference that, and email, separately.