Hello, since we have installed the CU 22 for Exchange:
Changes to Exchange Web Services Push Notifications An architectural change to Exchange Web Services (EWS) Push Notifications authentication is included in all packages released today. KB4490060<https://support.microsoft.com/kb/4490060> outlines the details of the changes made. Customers who rely upon Push Notifications, should understand the important changes made. We have evaluated the changes to push notifications against many commonly used EWS clients, e.g. Outlook Mac, Skype for Business Client, native iOS mail clients and observed no loss of functionality due to these changes. EWS Pull and Streaming Notifications functionality are unchanged by today's updates. The update to EWS Push Notifications is considered a critical security update and customers should deploy the update as soon as they understand and accept any potential impact. The change in Push Notification authentication is a permanent change to the product and necessary to protect the security of an Exchange Server. After applying either the cumulative update or update rollup to a server, customers are advised to force a reset of the Exchange servers' credentials stored in Active Directory. This can be accomplished using the Reset-ComputerMachinePassword<https://docs.microsoft.com/powershell/module/microsoft.powershell.management/reset-computermachinepassword?view=powershell-5.1> cmdlet in PowerShell 5.1 or later. If PowerShell is not an option, netdom can also be used<https://support.microsoft.com/en-us/help/325850/how-to-use-netdom-exe-to-reset-machine-account-passwords-of-a-windows#2>. Microsoft knows of no instances where machine accounts have been compromised. Updating a machine account password is considered a best practice to ensure the security of the server is not compromised. In addition, customers are encouraged to evaluate if their user password expiration policies are appropriate for Exchange enabled accounts. All Evolution Users have authentification <https://en.wiktionary.org/wiki/authentification> problems, and so they could not connect to Exchange with EWS. Have anyone here the same problem or a solution for this? THANKS!
_______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
