x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 108 subscribers
  • Views 6149 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
44
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Kevin M

TLS 1.0 and emailing from Sage 100

SUGGESTED
Posted By

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").

Parents
  • 0
    SUGGESTED

    I have sent a request to our Customer Experience team to have this Knowledge Base Article updated.  By the looks of the truncated line, it appears that the article did not update properly prior to being published.  

    The updated resolution section should appear as follows:

    1. Upgrade to Sage 100 2019.
    2. Contact Customer Support to obtain a PreRelease Correction for Sage 100 2018.  You will be required to sign a PreRelease Agreement document to obtain the correction.
    3. There are no current plans to make a correction available prior to the Sage 100 2018 release. 

    In Sage 2019 we retooled Paperless Office to use the newer ChilkatDotNet47.dll.  The older Chilkat components are no longer being installed.  

    For our Sage 100 2018 users we have a PreRelease correction available for this issue by requesting it from Sage 100 support.

Reply
  • 0
    SUGGESTED

    I have sent a request to our Customer Experience team to have this Knowledge Base Article updated.  By the looks of the truncated line, it appears that the article did not update properly prior to being published.  

    The updated resolution section should appear as follows:

    1. Upgrade to Sage 100 2019.
    2. Contact Customer Support to obtain a PreRelease Correction for Sage 100 2018.  You will be required to sign a PreRelease Agreement document to obtain the correction.
    3. There are no current plans to make a correction available prior to the Sage 100 2018 release. 

    In Sage 2019 we retooled Paperless Office to use the newer ChilkatDotNet47.dll.  The older Chilkat components are no longer being installed.  

    For our Sage 100 2018 users we have a PreRelease correction available for this issue by requesting it from Sage 100 support.

Children

*Community Hub is the new name for Sage City