Microsoft 365 TLS 1.0 Relay from Evolution via SMTP

Hi All,

As you may or may not know, Microsoft 365 has decomissioned TLS1.0 unless you opt in for legacy support by enabling it via PowerShell.

Sage 200 Evolution does not have an option to adjust the TLS version (1.0, 1.1, 1.2, 1.3) under the System Wizard which leads me to believe it still uses TLS1.0 only.
We have been successful in enabling legacy support for M365 and allowing TLS1.0 support however a Wireshark interrogation of the traffic indicates that outbound mail relay still occurs via TLS1.2, causing it not to work by means of a "Socket Error".

Thus, Microsoft 365 Exchange Online is no longer a valid SMTP configuration for Evolution? It works by selecting the "Outlook" option via the System Wizard but for some of our use cases "Outlook" is not an option, only SMTP.


Both SMTP relay and the "Send As" function under the Microsoft Admin panel has been enabled too and works perfectly when testing via PowerShell or a TLS1.2 enabled device/service.
This used to work without issue prior to January 2022 before 1.0 was decomissioned.

Microsoft 365 announced in 2018 already the intent to decomission TLS1.0 but "Office 365" still remains an option under Evolution's SMTP configuration? 

Anyone facing the same problem?

Parents
  • 0

    Hi Armand, 

    What version of Evo are you running, my understanding is that this is resolved in V10 and higher. The alternate solution you highlighted (enabling legacy support) should work, are you using the legacy smtp server settings - smtp-legacy.office365.com

Reply
  • 0

    Hi Armand, 

    What version of Evo are you running, my understanding is that this is resolved in V10 and higher. The alternate solution you highlighted (enabling legacy support) should work, are you using the legacy smtp server settings - smtp-legacy.office365.com

Children
  • 0 in reply to DeepakN

    Hi Deepak, 

    Thank you for the prompt response.  Yes I tried smtp-legacy but on wireshark it still indicates that we are breaking out via TLS1.2 which is surprising.
    What prompted me to post my message was due to the use case being on Evo 7.2.9.  I have not tried V10 which I will do very soon no doubt.
    Will post my findings.