On Fri, 2019-07-19 at 11:46 +0200, Martin Monperrus wrote:
> - The "mark as read" command was never sent to the server (broken
> connection?)
> - A status is incorrectly cached somewhere.
Hi,
I'd bet on both above, but I've no idea how to reproduce it.
Feel free to file a bug at [1],
Hi all,
Here is a strange behavior. I use evolution-ews to connect to MS Exchange.
After using evolution-ews for some months, I connect to the Exchange Webmail
(aka OWA).
I notice that there are 30 messages marked as unread in OWA, from the past
months, while 1) I read
them all 2) I marked the