SMTP modern authentication when sending notifications

Not yet but this should be coming soon, the related improvement ID is 164030. Please see this support article for guidance: Modern authentication in O365 and M-Files notification settings

Hi, Joonas,

Is there any news on this front, specifically for a deadline, as after 12/31/2022 we will not be able to use basic authentication in our organization

Please see the new blog post from our product team here: community.m-files.com/.../mail-notifications-in-on-premise-installations-and-deprecation-of-basic-authentication-in-microsoft-exchange-online

Hi Joonas, can I ask you for an update on this topic? The blog post said first to target the support for OAuth in the March release, than it was changed to May and now I still can't see the support for OAuth.

Thanks in advance

This has taken more effort than originally estimated, thus the delays. The feature is currently in internal testing and we hope to release it in Q3. Please follow the release notes to see when it's available.

Hi Joonas

Despite feature being now implemented since Aug '23 update, somehow still can't get notification service to work with Exchange online.

Am running 23.10.13060.5 and keep getting following event log message when system is trying to send notifications:

M-Files Online

Fehler bei der Authentifizierung.
Silent Microsoft authentication failed. One or more errors occurred. An error occurred while sending the request. The underlying connection was closed: An unexpected error occurred on a send. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host

MailManager.cpp, 715, Fehler bei der Authentifizierung. (0x80040162)
ExternalMailSourceClient.cpp, 232, Fehler bei der Authentifizierung. (0x80040162)
ExternalMailSourceClient.cpp, 232, Silent Microsoft authentication failed. One or more errors occurred. An error occurred while sending the request. The underlying connection was closed: An unexpected error occurred on a send. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host  (0x80040162)
(M-Files 23.10.13060.5 2023-11-09T09:11:31.217Z)

Have allready tried all sorts of things in terms of tenant, client and secret settings - til now to no avail.

Any further ideas?

Brgds

Guido

Hi Joonas

Despite feature being now implemented since Aug '23 update, somehow still can't get notification service to work with Exchange online.

Am running 23.10.13060.5 and keep getting following event log message when system is trying to send notifications:

M-Files Online

Fehler bei der Authentifizierung.
Silent Microsoft authentication failed. One or more errors occurred. An error occurred while sending the request. The underlying connection was closed: An unexpected error occurred on a send. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host

MailManager.cpp, 715, Fehler bei der Authentifizierung. (0x80040162)
ExternalMailSourceClient.cpp, 232, Fehler bei der Authentifizierung. (0x80040162)
ExternalMailSourceClient.cpp, 232, Silent Microsoft authentication failed. One or more errors occurred. An error occurred while sending the request. The underlying connection was closed: An unexpected error occurred on a send. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host  (0x80040162)
(M-Files 23.10.13060.5 2023-11-09T09:11:31.217Z)

Have allready tried all sorts of things in terms of tenant, client and secret settings - til now to no avail.

Any further ideas?

Brgds

Guido

This is likely related to the lack of TLS 1.2 support on the server, please see this support article: Azure AD TLS 1.0 and 1.1 Error: "Silent Microsoft authentication failed"

Thanks a lot for that valuable input, which could indeed be the source of all trouble .. Will check it out and keep you posted ...

Just to let you know .. TLS was indeed THE issue for that matter, as it was somehow only partially activated .. Anyway, after setting it right and in accordance with the respective Microsoft KB article eventaully everything worked smoothly :-)

Thanks for confirming, good to know that it was the usual suspect