Sending emails stopped working today - basic authentication disabled error in log

[crmscot]

Thanks guys. Your quick response is very much appreciated. It must be like chasing a moving target trying to work with Microsoft products these days!!

[macistda]

New Release available 1.3.5 seems to work. Wow what a patch speed. Notes: Mail: Does not connect to the deprecated v2 API anymore.

[macistda]

Same Problem here. I think Microsoft set depricated and maybe Espo Plugin needs an update.

Error 500
Outlook Oauth: Error after requesting GET https://outlook.office365.com/api/v2.0/me/; Reason: The API version 'V2' has been deprecated.. Code: 410.

"Old" accounts are still running, I guess until the token will get a timeout. Setup of new accounts is not possible at the moment.

[victor]

I will duplicate. To be able to connect using the Outlook integration extension, the email address you're trying to connect (for example, xxx@outlook.com) must meet the following criteria:
- xxx@outlook.com must be a Microsoft 365 member.
- In Administration > Integrations > Outlook > Tenant should be set to common.

[crmscot]

Sorry for being a pest Victor, I really appreciate your help but I'm unable to follow your link to the answer - ...448#post110448

[victor]

The answer to your misunderstanding of the existing situation is already here: https://forum.espocrm.com/forum/gene...448#post110448.
Why it worked for you for the usual xxx@outlook.com, which is not a Microsoft 365 member - remains a mystery.

[crmscot]

I've spent hours trying to resolve this issue and believe it's down to a change that Microsoft has made because it used to work just fine. I've set up 2 personal email accounts in Espocrm (the first to my domain works correctly) but the second (using my outlook.com email address fails). I've turned on debug in Espocrm and get the following error:-

[2024-09-24 16:32:54] ERROR: Email sending error: 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant. Visit https://aka.ms/smtp_auth_disabled for more information. [LO2P265CA0325.GBRP265.PROD.OUTLOOK.COM 2024-09-24T16:32:56.522Z 08DCDB6B3050BD3A]
[2024-09-24 16:32:54] WARNING: Email sending:unknownError; 0
[2024-09-24 16:32:54] DEBUG: API (500) sendingFail; POST /Email/sendTest; Input data: {"server":"smtp.office365.com","port":587,"auth ":f alse,"security":"TLS","username":"david@kelimar.co .uk","password":null,"authMechanism":"login","fro m Name":"David Pettigrew","fromAddress":"david.pettigrew@outlook. com","type":"emailAccount","id":"66eee4f9763cbd44 b ","userId":"6151de348f3fcc429","emailAddress": "*** **"}; Route pattern: /Email/sendTest
[2024-09-24 16:32:54] NOTICE: (500) sendingFail :: POST /Email/sendTest

I've set up my outlook.com account as a guest user in Exchange 365 and tried unsuccessfully to send with authentication enabled and disabled for the organisation. If I try to send an email from Outlook Web Access that also fails if I try to send as the guest (@outlook.com) user.

[Bernhard]

Hi, For some reasons, this just works again. So please ignore this one.

Thanks,

Bernhard

[Bernhard]

Hi Victor, thanks for your help. I do not feel that I confused topics. This topic is the same: Connection to Exchange via the Outlook extension. Have have the latest Espo CRM and the latest Outlook Extensions installed. (Otherwise I would have mentioned it).

This worked all until today morning and there was no change on my side (no updates, no Azure settings, etc.)

The message I posted seems to me like Microsoft has stopped API version V2 and that the Outlook extension is still using this one.

I appreciate your input and I am sorry if somebody got confused with my post.

[victor]

If you don't find a solution in this thread: https://forum.espocrm.com/forum/exte...working-so-far, please , or create your own, or better, write in the subject via the link, specifying the version of EspoCRM and Outlook Integration extension.
Do not confuse topics.

[Bernhard]

My Outlook Extension also stopped working today. When I use the Extensions Connect Button I get:

Error 500
Outlook Oauth: Error after requesting GET https://outlook.office365.com/api/v2.0/me/; Reason: The API version 'V2' has been deprecated.. Code: 410.

[victor]

- xxx@outlook.com must be a Microsoft 365 member.
- In Administration > Integrations > Outlook > Tenant should be set to common.

[crmscot]

Yes, it's a separate account. I have tried deleting the credentials for my kelimar account (in the outlook integration setup) and clearing cache and cookies, then connecting to my outlook azure login. I then used the ID and secret key from there. I've also added the permissions as per the documentation. However, when I try to connect it fails. There is a warning message in the azure account saying there is an unexpected error without any further details. I'm still checking this out but it looks like a Microsoft issue.
Am I correct in thinking once I've connected the kelimar account and got that working with the first personal email account setup, I should delete the ID and secret key from the outlook integration screen then enter the ID and key from the outlook account before finally setting up the second personal email account?

[victor]

Do you have a separate Personal Email account set up for xxx@outlook.com? If so, can you connect to xxx@outlook.com Personal Email Account?

[crmscot]

Thanks for your help and sorry for any confusion. There is only one personal email account set up in Espocrm. I have the outlook extension set up and working correctly for my email account xxxx@kelimar.co.uk. I can send and receive emails using the personal email account settings in the screenshot.

In my Espocrm user record, I have also entered a second email address that I use, xxxx@outlook.com. I have always been able to select either email account as the sender when composing a new email in Espocrm and I had accepted that this is the way it is meant to work. I thought that the xxxx@outlook.com was being treated as an alias. It has worked the way I wanted for ages and I didn't think any more about it.

Two days ago, I started getting errors if I tried to send an email if I select the xxxx@outlook.com as the sender. The xxxx@kelimar.co.uk continues to work as expected.

Perhaps I have been using an "undocumented feature" all along and Microsoft have just tightened up security on this. I am wondering if I need to set up a second personal email account in Espocrm (xxxx@outlook.com) to get this working again.