Dear Maintainer,

I would like to support, bump, and extend on original request by OP.
Although there are various *nix email clients, Evolution is one of the few that 
offers all classic "email client things in one place", i.e. email, calendar, 
contacts, tasks. Hence it is used a lot, especially by professionals, who 
subsequently need to connect up to a Microsoft email service. And due to this I 
would like to urge you to carefully reconsider the Evolution version available 
with Forky.

The current version in testing/unstable (3.56.x) is no longer suitable for the 
primary use case of connecting to Microsoft 365. Microsoft is in the process of 
*completely disabling EWS* in Exchange Online. This process already began in 
October 2026, ongoing currently. EWS will be fully and permanently disabled on 
1 April 2027. Organisations that have already completed migration to O365 can 
have their EWS access cut off at any time, and temporary allowlists will also 
become ineffective after April 2027 
(https://support.cloudm.io/hc/en-us/articles/29978164191644-Microsoft-365-EWS-retirement-keeping-your-migrations-running)

Evolution's Microsoft 365 (Graph API) account type is the only alternative, but 
developers *explicitly recommend 3.60.x and above* for a relatively stable 
experience. The existing 3.56.x is severely inadequate in terms of OAuth2 
authentication and synchronisation reliability, and users have no way to 
migrate normally before EWS is disabled.

In the GNOME Discourse thread, developer response confirms evolution-ews 
provides both "Exchange Web Services" and "Microsoft 365" account options; the 
latter is the intended path, though feature parity with EWS is not complete. 
(https://discourse.gnome.org/t/is-microsoft-365-graph-api-expected-to-be-available-in-evolution-3-60-x/36019/3)

It is understood that the real obstacle to the upgrade is the 
'evolution-data-server' library transition. But please consider the special 
nature of this issue: this is not a routine version update, but rather 
Evolution, as an email client on Debian, will completely lose its ability to 
connect to the mainstream enterprise email platform Microsoft 365. *For 
enterprise and organisational users who rely on Debian desktop for work, this 
directly affects usability*. Requesting to prioritise scheduling this 
transition before the Forky release, or at least provide a clear timeline.

Reference (Debian library transition precedent for evolution-data-server):
Debian Bug #1070462, "transition: evolution-data-server 3.52", documents that a 
soname bump in evolution-data-server libraries triggers a coordinated 
transition.
URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070462

Reference (current Forky version status):
Freexian package tracker for evolution shows Forky at 3.56.2-10.
URL: https://deb.freexian.com/extended-lts/tracker/source-package/evolution
Kind regards,

Bella

Reply via email to