hello,
on reply indicator (#3207) · Issue · GNOME/evolution
they tell me that i'm on an old evolution version
if i go to Apps/Evolution – GNOME Wiki Archive, there is only reference to 3.50.x
if i go to to GNOME Release Calendar - GNOME Release Notes, it's the same
what is the version they're talking about ?
how can i download it ?
where come from this 3.52.3-0ubuntu1 version i have (zorin OS 18 core) ?
i can't updated it, software say there is no updates
If you want to use a later version of evolution you can install the flatpak.
The installed .deb package is not the latest version of evolution as Zorin is a LTS distribution and the packages are "frozen" and can't be updated.
I believe that this is the link you intended:
That being said: You did not get an answer, you got brushed off.
Notice that Klapper did not say that the issue has been fixed in a later release.
And he didn't, because it hasn't. It has not been fixed because it is not a bug.
Remember, you are combining two very different systems. You are communicating with Microsoft 365, via a Gnome GnuLinux application that relies on API's.
Outlook and 365 do not rely on these same API's; they use the internal Exchange/MAPI extensions and access the active server.
Gnome Evolution is using the backend - tapping on Microsoft and requesting the information.
Mircosofts API does not reliably expose classic Exchange flags such as PR_LAST_VERB_EXECUTED, PR_LAST_VERB_EXECUTION_TIME, so Evolution’s message list “reply indicator” which depends on these MAPI-style properties has nothing to render when they are not exposed. If they are unpopulated on the backend, you see no icons.
thank you for your answers
i uninstalled system version and switched to flathub version
is this the last version ?
i would like to understand better the flow
what are differences in API if i set my account to EWS or microsoft365 ?
why do i have this indicator when i set it to EWS and not microsoft365 ?
correct me if i'm wrong but this is what i have understand :
1/ EWS (for O365) will be deprecated in october 2026
2/ microsoft365 is using graph API, which (currently) don't expose these flags