Unread email count not synced across devices
-
Just set up Vivaldi Mail (on Vivaldi version 3.5.2115.87).
It seems to work fine, but I have noticed that the count of unread emails does not sync/update with other devices. E.g. if I mark as read a message on my mobile client and/or or another desktop client, Vivaldi does not mark it as read as well. -
Nobody has the same problem or a fix?
Just to clarify, it is not just the count of unread emails... it is just the set of unread emails that does not sync across other clients.
Thanks -
@FCalderoni Vivaldi does not sync anything concerning mail across devices. Various IMAP servers sync "read" status in various different ways (there is not a hard standard) and so Vivaldi mail client cannot always detect on one device that mail was read on another device. But this is not sync via Vivaldi, but rather sync via IMAP servers. Vivaldi's ability to usually detect on Device B when a mail was opened on Device A, may improve over time as the differences in IMAP servers and IMAP methodology from one provider to another are accounted for.
-
Thank you for answering @Ayespy
That is unfortunate. It worked smoothly on M2 and I hope this would also fro Vivaldi. -
Is there any news on this? Still can't see the read status synced from imap servers I'm using.
As much as I can accept that there may be "grey" areas in the implementations, I wonder why it works on any other device in my reach, e.g. dedicated mail clients, Android smartphone with various apps, web mail etc.
-
This issue does not come up on the forum much, it doesn't seem to be a wide spread issue. Without mentioning what lMAP service or IMAP server software is affected, and without a bug report allowing to reproduce the problem (i.e. by giving devs a test account) there will be no fix
-
@wildente said in Unread email count not synced across devices:
This issue does not come up on the forum much, it doesn't seem to be a wide spread issue. Without mentioning what lMAP service or IMAP server software is affected, and without a bug report allowing to reproduce the problem (i.e. by giving devs a test account) there will be no fix
Fair enough! I will try to create some kind of sandbox that reproduces the error.