|
|||
|
|||
Alright Commit... what's the plan?
https://techcommunity.microsoft.com/...er/ba-p/805892 https://office365itpros.com/2020/02/...uthentication/ IMAP4 and POP3 Microsoft says that they have completed work on modern authentication for these obsolete access protocols and are rolling out the code within Exchange Online. They make the point that modern authentication has been available for IMAP4 in Outlook.com for some years, which begs the question why it’s taken so long to appear in the commercial service. Documentation for developers is being completed, which will allow companies who write the IMAP4 and POP3 clients people use to connect to Exchange Online mailboxes to upgrade their code before October. Some work will be needed to test and deploy updated clients. With that in mind, the question must be asked if it is time to retire these protocols and use something more modern. Remember, IMAP4 and POP3 were created at a time when a separate protocol was needed (SMTP) to send messages. These protocols can only download messages. OWA is a good replacement for PCs while Outlook Mobile should replace mobile clients that use IMAP4 and POP3. I don’t underestimate the pain and disruption caused when users are forced to switch clients, but we have arrived at a crunch point where the need for security trumps personal preference for antiquated protocols. SMTP Microsoft says that they are nearly finished work to implement modern authentication for SMTP. When Microsoft switches off basic auth for SMTP, this is likely to disrupt connectivity for mail-enabled devices that use SMTP to send notifications and other information. It’s unclear how many manufacturers will upgrade the software running on these devices to use modern authentication, especially for older devices. It might be the case that no solution will be available to allow devices to continue connecting to Exchange Online unless customers pressurize manufacturers to create patches. |
|
|||
|
|||
This should have already been addressed. The deadline is Oct 13th for the typical Office 365 user. If you are a Microsoft Partner or a CSP the deadline was last week or you are in breach of your Partner Agreements.
I don't understand why it hasn't already been looked into. |
|
|||
|
|||
There are 3 solutions.
1. CommitCRM to use the MS Graph API to connect to the Office 365 Tenant using this API call. https://graph.microsoft.com/v1.0/users/{user}/SendMail OR 2. For CommitCRM to connect to our Jupiter Server product via our API call http://localhost:11111/MicrosoftGrap...endMailRequest Request) {or https://hostname:22222/.... if that is required} which will also provide CommitCRM the ability to integrate with Naverisk, Webroot and ITPortal....just saying. OR 3. Some other solution I am not aware of. :-) |
|
|||
|
|||
Thank you for following up on this.
This change is pending and will enter work at a slightly later time. It seems that the Microsoft has postponed the changes, originally planned for October of this year, to latest in 2021: https://techcommunity.microsoft.com/...e/ba-p/1275508 Hope this helps. |
|
|||
|
|||
Update: Support for Microsoft 365 modern authentication for Email (OAuth) was introduced in RangerMSP 30.
|