#360works email plugin upgrade#

While SMTP AUTH specifically is being allowed to keep some legacy items running, the end of Basic Auth is likely going to see 2FA enforced org-wide by some that have been putting it off. My experience with a recent job tells me that the biggest factor here is going to be the individual M365 tenant settings. Other options for sendingauthenticated mail include using alternative protocols, such as the Microsoft Graph API.

However, westrongly encourage customers to move away from using Basicauthentication with SMTP AUTH when possible. The reason SMTP will still beavailable is that many multi-function devices such as printers andscanners can't be updated to use modern authentication.

SMTP AUTH will still be available when Basic authentication ispermanently disabled on October 1, 2022. You should be able to still connect, at least for now.

#360works email plugin upgrade#

Im hoping to convince these clients to upgrade to FileMaker 19, but in the interim does anyone know if FileMaker 17 could naively support OAuth on Microsoft endpoints using Insert from URL script step or using the BaseElement Plugin? In the medium term Im thinking about leveraging the Microsoft Graph API which may work as an alternative and give access to additional features such as outlook calendars. Even if it's possible, I would prefer not to have to move these all to OAuth in a hurry if I can avoid it. Whilst I appreciated the added security aspects, I have multiple scripts using 'Send Mail Send via SMTP Server' connecting to Microsoft 365 accounts running on developments as far back as FileMaker 17. Microsoft (Office365) has recently announced that as of October 1, 2022, it will no longer support Basic Authentication which will be replaced with OAuth authentication.ĭoes anyone know if this will impact the native script step 'Send Mail Send via SMTP Server ' or is this only applicable to the 360Works Email and other similar plugins? Thanks to a heads up from Jesse Barnum at 360Works.