Sage 100

 View Only
Expand all | Collapse all

Electronic Delivery broken after client email provider disabled TLS 1.0

  • 1.  Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 05-01-2019 15:12
    Company Maintenance email settings:
    SMTP Encryption = SSL
    User ID, Domain, pw are all configured.
    Use 128-bit Encryption for password protected documents is checked.

    Tried changing SMTP encription to TLS/STARTTLS, but error log is the same.

    Unable to verify SMTP connection.

    ChilkatLog:

      VerifySmtpConnection:

        DllDate: Jan 19 2012

        UnlockPrefix: SBestSoftMAILQ

        Username: VIPSERVER:Administrator

        Architecture: Little Endian; 32-bit

        Language: ActiveX

        Checking TCP/IP connectivity to the SMTP server.

        This does not check the login/password.

        Checking connectivity to SMTP server viptrellis.mail.pairserver.com:465

        smtp_host: viptrellis.mail.pairserver.com

        smtp_port: 465

        ConnectTimeoutMs_1: 30000

        calling ConnectSocket2

        IPV6 enabled connect with NO heartbeat.

        connectingTo: viptrellis.mail.pairserver.com

        dnsCacheLookup: viptrellis.mail.pairserver.com

        Resolving domain name (IPV4)

        GetHostByNameHB_ipv4: Elapsed time: 15 millisec

        maxTimeMs_connect: 30000

        myIP_1: 10.1.10.13

        myPort_1: 53823

        connect successful (1)

        clientHelloMajorMinorVersion: 3.1

        buildClientHello:

          majorVersion: 3

          minorVersion: 1

          numRandomBytes: 32

          sessionIdSize: 0

          numCipherSuites: 10

          numCompressionMethods: 1

        --buildClientHello

        numBytesRequested: 5

        Connection closed by server.

        Failed to read beginning of SSL/TLS record.

        Failed to read incoming handshake messages. (1)

        Client handshake failed.

        Failed to connect to SMTP server.

      --VerifySmtpConnection

      Failed.

    --ChilkatLog



    Client IT (separate from email provider) is asking if Sage supports only certain TLS versions.

    Any thoughts on next step before I open a case with Sage?

    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    San Jose CA
    800.627.9032 x221
    ------------------------------


  • 2.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 05-01-2019 17:28
    I had a client with the same issue that started yesterday mid-morning. Worked earlier in the day, then just stopped working. Same error. They claimed they didn't change anything. I don't have a solution either.

    ------------------------------
    Bill Pfahnl
    Nims & Associates
    ------------------------------



  • 3.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 05-01-2019 17:34


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 4.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 05-01-2019 17:52
    Edited by Barbara Goldstein 05-01-2019 18:31
    Good catch Kevin.  I hate the Sage KB sometimes.

    Does Sage officially acknowledge other TLS versions?  Never mind.  Looks like client has an upgrade in their future anyway - they are on v2016.

    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    San Jose CA
    800.627.9032 x221
    ------------------------------



  • 5.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 05-01-2019 20:42
    Am I reading this correctly and only 2019 has the TLS 1.x capability? 
    I don't see it in the 2018.6 What's New notes as being added and I don't see a TLS specific hotfix

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 6.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 05-02-2019 08:10
    So much for "compliance" support from Sage.   TLS1.0 has only been deprecated as basically useless for several years...

    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------



  • 7.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 05-02-2019 08:24
    Remember Sage says they only technically offer hotfixes to versions not on the PU schedule at their discretion. I think only 2018 + 2019 are getting product updates and IIRC 2018 stops in September.

    I’ve been advising customers to start thinking about more frequent upgrades ( at least every other year ) and to consider the “true” supported versions to be the versions eligible to receive scheduled product updates.



    ---------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ---------------------------------





  • 8.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 05-02-2019 10:41
    "Compliance" and "Technology Updates" on "Sage 100 Road Ahead" charts for 2019.1 (June) and 2019.2 (Sept).

    Lee Graham

    Friendly Systems, Inc.

    Sage 100 (Mas90/200), Sage 300 (Accpac), SageCRM
    Visit us on the web at www.friendlysystems.com
    Office:?? 678.273.4010 ext 4
    Mobile: 404.202.9065
    Fax:?????????? ??678.273.4012
    See our blog at www.friendlysystems.com/blog



    ------Original Message------

    So much for "compliance" support from Sage.   TLS1.0 has only been deprecated as basically useless for several years...

    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------


  • 9.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 07-23-2019 07:45

    Sage updated their KB after @Kevin Moyes questioned the older KB in Sage City. It looks like only Sage 100 2018 ( signed agreement required )​ and Sage 100 2019 ( new TLS included in upgrade ) will receive TLS 1.2 compliance.

    Microsoft says O365 will drop TLS 1.0 June 2020.

    This may catch 2017 and earlier users who are using O365 and paperless document emailing

    Here's the Sage KB which has been updated to clarify the above -  https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=93322&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=9509&cmd=displayKC&dialogID=457459&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true



    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 10.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 07-23-2019 07:45


    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 11.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 09-17-2019 14:07
    Edited by Rhonda McNamara 09-17-2019 15:46
    Call me Henny Penny - yes,I am that person.  But I am nervous about what happens when O365 completes the deprecation of TLS 1.1 and below.  And I don't think this is limited to O365, really, at least not for long.
    Have I thought of everything?  Has anyone done this legwork?  Hopefully I'm missing some reason this is no big deal.

    Email through Sage 100 - will break if they use TLS encryption and aren't on Sage 100 2018 (patched) or 2019.
    Email through Sage Alerts - will break if not on 9.x (patched) or 10.
    Aatrix - I believe Aatrix also uses TLS encryption to get PII data up to it's cloud.  What version of TLS, I don't know.
    Paya - forced updates to resolve this.
    What about other CC processors?
    What about Sage AP Automation?
    Sage Business Intelligence?
    Any enhancement involving encryption or email may be at risk.
    #Sage100 #Security 
    ​​

    ------------------------------
    ==================
    Rhonda McNamara
    Customer Success Manager
    Stewart Technologies, Inc.
    rsm@stewarttechnologies.com
    ------------------------------



  • 12.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 12-06-2019 11:03
    This KB has changed, and I don't see evidence of 2018 getting a PU that supports TLS 1.2.  I think it's still a patch.  I'm actually opening a case because I need to get this figured out before June 2020.

    Cannot send email from Sage 100 when TLS 1.0 is disabled

    Products
    Sage 100

    Country
    North America

    Description
    <content>

    Cannot send email from Sage 100 when TLS 1.0 is disabled.

    </content>

    Cause
    <content>

    Sage 100 email engine uses TLS 1.0

    </content>

    Resolution
    <content>
    • Upgrade to Sage 100 2019.
    • Contact Customer Support to obtain a PreRelease Correction for Sage 100 2018. You will be required to sign an end user agreement document to obtain the correction.
    • There are no plans to make a correction available prior to the Sage 100 2018 release.
    </content>

    Related resources
    Download Sage 100 2019 Full Product
    Category
    Configuration

    Defect ID
    <content>109844</content>



    ID:93322Last Modified Date:12-5-2019  

    ------------------------------
    ==================
    Rhonda McNamara
    Customer Success Manager
    Stewart Technologies, Inc.
    rsm@stewarttechnologies.com
    ------------------------------



  • 13.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 03-02-2021 13:18
    Did anyone ever receive a 2018 patch for TLS 1.2? 
    I just received one call from a customer who says their paperless email is suddenly not sending
    I can't test the email either without receiving an error 

    Connection closed by server.

    Failed to read beginning of SSL/TLS record.

    Failed to read incoming handshake messages. (1)

    Client handshake failed.

    Failed to establish TLS connection.

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 14.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 03-02-2021 13:23
    We just had an O365 customer complain about Paperless email stopping.  I recommended an SMTP relay until their planned upgrade gets done.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 15.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 03-02-2021 13:25
    How do they setup the SMTP relay? Is that on their existing 0365 or are you suggesting use a third-party SMTP server outside of their normal email?

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 16.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 03-02-2021 13:27
    Their IT will be setting up an external SMTP relay service, then we'll just point Sage to that.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 17.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 03-02-2021 13:36
    I have another customer on 2018 their email connection is smtp.office365.com with port 587 and that is working. I'm not sure why one would work and the other not unless it's an internal email configuration or Microsoft is disabling TLS 1.0 gradually.

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 18.  RE: Electronic Delivery broken after client email provider disabled TLS 1.0

    Posted 03-03-2021 18:02
    Update: switching to smtp.office365.com resolved the issue for this customer

    ---------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ---------------------------------