FYI Office 365 only allow TLS 1.2 via SMTP connections now!

[chazzy2501]

We've been having issues scanning to email recently from our Sharp Multifunction Printers "network timeout errors". I just happened to find the answer on youtube of all places. It seems that Office 365 changed their logins to only accept the latest TLS1.2 connections. Something to keep in mind if your having email issues with devices that are not updated frequently. I've had to call support for a firmware update of our printers.

 

[Arthur]

It seems that Office 365 changed their logins to only accept the latest TLS1.2 connections.

I thought the switchover date was meant to be 31st October?

 

• https://dirteam.com/dave/2018/01/10/office-365-only-allows-tls-1-2/
   
   
  
• https://support.microsoft.com/en-gb/help/4057306/preparing-for-tls-1-2-in-office-365
   
  

  As of 31 October 2018, Microsoft Office 365 will remove support for TLS 1.0 and 1.1. This means that if you have issues connecting to Office 365 services because of weaker protocols, no support tickets would be generated.
   
  Please note: This is NOT when Microsoft Office 365 will officially deprecate TLS 1.0 and 1.1.
   
  By 31 October 2018, all client-server and browser-server combinations should use TLS version 1.2 (or a later version) to ensure connection without issues to Office 365 services. This may require updates to certain client-server and browser-server combinations.
   
  If you do not update to TLS version 1.2 (or later) by 31 October 2018, you may experience issues when connecting to Office 365. If you experience an issue related to the use of an old TLS version after 31 October 2018, you will be required to update to TLS 1.2 as part of the resolution.

Previous thread: www.edugeek.net/forums/cloud-services/195017-office-365-will-allow-tls-1-2-only-31st-october-2018-a.html

[chazzy2501]

 

some of the commenters have ended up like me..

[MatthewL]

This might be of interest to you.

 

Scan to Office 365.pdf

[free780]

If your a global adnin you should get the weekly updates where this has been listed.. You can use a SMTP relay to work around old equipment which won't support TLS 1.2.

[MatthewL]

The Sharp kit will work providing that guide is followed and the machine has had the firmware updated depending on its model as some of the older kit didn't support till this is upgraded.

[synaesthesia]

We gave up trying to get our printers speaking to 365 for various reasons and ended up using our sophos firewall as a relay. Works wonders

[chazzy2501]

Yes the printers have been scanning to email for almost 2 years with O365 (staff really like the feature). The new hack for the sharp printers has you put brackets around your email address. Not sure what the angled brackets do or how long the hack will work.

[chazzy2501]

@MatthewL Ha! the document showed me that I was still using the non-ssl port. (changed to 587) That probably has more to do with it!

[FishCustard]

Just a thought - if you can't get them talking to 365 again, how about having docs scanned to users' home folders (or, better, a folder within it). That's what we do now and users much prefer it to having to retrieve the thing from their email.

[MatthewL]

I've had an issue today where the account used for scanning had to be granted send on behalf rights for it to work. Tested by scanning to my gmail ok so knew that worked but internally it wasn't due to this.