marking mail read in webmail doesn't mark it read in vivaldi mail
-
@mib2berlin i had tried reloading the yahoo webmail page after marking it read (during my previous tests)- note: I use the advanced (newer) yahoo webmail ui not the simple (older) one
note to self: tomorrow: check if 2nd reminder email is marked read in vivaldi client (maybe there is a time delay)
update: yeah no even next day the read status is not updated in vivaldi for yahoo when it gets marked read in yahoo webmail
and I tried again just now on a few more emails and their read status doesn't get updated in vivaldi
-
@dalinar
I use standard, the other is called basic.
I just checked it again and click on the message in Yahoo Unread move it to Inbox, and make it read in Vivaldi.
I don't even have to mark it as read.
Opensuse Tumbleweed x86_64 KDE 6.2 X11, Windows 11 Pro, Vivaldi latest
HP Probook Intel(R) i5-8350U 16 GB, GPU UHD 620, SSD 256 GB
Miniforum-B550 AMD Ryzen 7 4700G 16 GB, Radeon Graphics
Xiaomi Poco M6 Pro, HyperOS Android 14 -
I have noticed that the read/unread status between my various Vivaldi sessions with mail and my phone (K9 mail) varies a lot. Sometimes things I've dismissed on one machine will still pop up as unread on another... sometimes not. I haven't seen a clear pattern.
Edit: this is for Hotmail - I think my gMail messages are more consistent.
-
@mib2berlin ok we are using the same UII
I mark read either clicking on the message, or selecting the message and marking it unread from the menu.
I was doing that from the inbox folder before in yahoo webmial but now I tried in the unread folder a few times and it also does not refelect in vivaldi mail for that account
note: as mentioned earlier I am not talking about the unified inbox but the individual account (they are located below "All Messages"), it might work in All Mesasges - I haaven't been looking there as my concern is with the individual accounts.
-
Seeing similar issue with Vivaldi email client not reflecting read status of messages for Yahoo account; issue does not occur for Vivaldi and other third-party email accounts.
It is not until Advanced > Re-sync folder with server option is selected by right click on account under All Accounts that the current read status of messages is shown in Vivaldi.
FWIW IMAP debug log not showing expected Fetch on change of message read status for Yahoo account
-
@dalinar
Hm, I rarely use All Accounts but it make no difference, the message is marked as read there too.
Do you use Yahoo Mail Pro?
-
@mib2berlin nope, just the free version.. but i have several yahoo accounts across various vivaldi profiles, and it affects yahoo accounts in other profiles as well. In fact I first noticed it on a different yahoo account in a different vivaldi profile than the account/profile I have been using for this thread.
-
@yojimbo274064400 that resync thing seems to mark them (messages marked read in yahoo webmail) as read in vivaldi (individual yahoo account)
but of course this is just a manual thing... it doesn't fix the problem.. after the resync if you mark something as read in yahoo webmail it still won't update the read status of the newly marked read messages as read in vivaldi mail
-
@dalinar
I added the Yahoo account a week again, maybe this is the reason it is in sync.
@yojimbo274064400 hint seems to solve it for you, nice. -
This post is deleted! -
This post is deleted! -
@whitesmaverick @bodygrooming
Hi, did you test resync Account?
-
This looks more like a Yahoo issue as it occurs in other email client for me as well
FWIW as far as I can tell when client enters idle state server does not send any updates. For example, marking a message as read and then unread in webmail shows the following log entries for:
- Vivaldi email account, where lines 4 and 10 show server communicate change in read status of message
1 Client started idling 2 Entering idle with IDLE 3 C: W63 IDLE 4 S: * 1 FETCH (MODSEQ (1389) FLAGS (\Seen NonJunk)) 5 Idle terminated 6 S: W63 OK Idle completed (60.001 + 59.997 + 60.000 secs). 7 Client started idling 8 Entering idle with IDLE 9 C: W64 IDLE 10 S: * 1 FETCH (MODSEQ (1390) FLAGS (NonJunk)) 11 Idle terminated 12 S: W64 OK Idle completed (60.004 + 60.003 + 60.003 secs).- Yahoo email account, server does not communicate change in read status of message:
1 Client started idling 2 Entering idle with IDLE 3 C: W40 IDLE 4 Idle terminated 5 S: W40 OK IDLE completed 6 Client started idling 7 Entering idle with IDLE 8 C: W41 IDLE 9 Idle terminated 10 S: W41 OK IDLE completed -
@yojimbo274064400 said in marking mail read in webmail doesn't mark it read in vivaldi mail:
FWIW as far as I can tell when client enters idle state server does not send any updates.
I have had some (temporary) errors in my log file. No less than 4 accounts made Vivaldi throw an error when they all went to idle. Something's not right on Vivaldi's end I think
[DEBUG][2024-09-08T13:55:23.430Z][14][[email protected]][imap.gmail.com] Idle terminated background-bundle.js:1 [DEBUG][2024-09-08T13:55:23.809Z][14][[email protected]][imap.gmail.com] S: W118 OK IDLE terminated (Success) background-bundle.js:1 [DEBUG][2024-09-08T13:55:23.886Z][16][[email protected]][imap.vivaldi.net] Client started idling background-bundle.js:1 [DEBUG][2024-09-08T13:55:23.886Z][16][[email protected]][imap.vivaldi.net] Entering idle with IDLE background-bundle.js:1 [DEBUG][2024-09-08T13:55:23.886Z][16][[email protected]][imap.vivaldi.net] C: W87 IDLE background-bundle.js:1 [DEBUG][2024-09-08T13:55:23.996Z][12][[email protected]][mail.lyl-canbys.de] Client started idling background-bundle.js:1 [DEBUG][2024-09-08T13:55:23.996Z][12][[email protected]][mail.lyl-canbys.de] Entering idle with IDLE background-bundle.js:1 [DEBUG][2024-09-08T13:55:23.996Z][12][[email protected]][mail.lyl-canbys.de] C: W89 IDLE background-bundle.js:1 [DEBUG][2024-09-08T13:55:24.233Z][13][[email protected]][login.foobarprovider.com] Client started idling background-bundle.js:1 [DEBUG][2024-09-08T13:55:24.234Z][13][[email protected]][login.foobarprovider.com] Entering idle with IDLE background-bundle.js:1 [DEBUG][2024-09-08T13:55:24.234Z][13][[email protected]][login.foobarprovider.com] C: W103 IDLE background-bundle.js:1 [DEBUG][2024-09-08T13:55:24.820Z][14][[email protected]][imap.gmail.com] Client started idling background-bundle.js:1 [DEBUG][2024-09-08T13:55:24.820Z][14][[email protected]][imap.gmail.com] Entering idle with IDLE background-bundle.js:1 [DEBUG][2024-09-08T13:55:24.821Z][14][[email protected]][imap.gmail.com] C: W119 IDLE background-bundle.js:1 [ERROR][2024-09-08T13:55:50.814Z][16][[email protected]][imap.vivaldi.net] Could not idle (IDLE) Error: Socket closed unexpectedly! a @ background-bundle.js:1 background-common-bundle.js:1 [MAIL - imap-client] Error: IMAP connection encountered an error! Error: Socket closed unexpectedly! at background-bundle.js:1:266354 at Object.error (background-bundle.js:1:62134) at i._onError (background-bundle.js:1:266342) at At._onError (background-bundle.js:1:225864) at background-bundle.js:1:214483 _log @ background-common-bundle.js:1 background-bundle.js:1 [ERROR][2024-09-08T13:55:50.816Z][14][[email protected]][imap.gmail.com] Could not idle (IDLE) Error: Socket closed unexpectedly! a @ background-bundle.js:1 background-common-bundle.js:1 [MAIL - imap-client] Error: IMAP connection encountered an error! Error: Socket closed unexpectedly! at background-bundle.js:1:266354 at Object.error (background-bundle.js:1:62134) at i._onError (background-bundle.js:1:266342) at At._onError (background-bundle.js:1:225864) at background-bundle.js:1:214483 _log @ background-common-bundle.js:1 background-bundle.js:1 [ERROR][2024-09-08T13:55:50.816Z][13][[email protected]][login.foobarprovider.com] Could not idle (IDLE) Error: Socket closed unexpectedly! a @ background-bundle.js:1 background-common-bundle.js:1 [MAIL - imap-client] Error: IMAP connection encountered an error! Error: Socket closed unexpectedly! at background-bundle.js:1:266354 at Object.error (background-bundle.js:1:62134) at i._onError (background-bundle.js:1:266342) at At._onError (background-bundle.js:1:225864) at background-bundle.js:1:214483 _log @ background-common-bundle.js:1 background-bundle.js:1 [ERROR][2024-09-08T13:55:50.816Z][12][[email protected]][mail.lyl-canbys.de] Could not idle (IDLE) Error: Socket closed unexpectedly! a @ background-bundle.js:1 background-common-bundle.js:1 [MAIL - imap-client] Error: IMAP connection encountered an error! Error: Socket closed unexpectedly! at background-bundle.js:1:266354 at Object.error (background-bundle.js:1:62134) at i._onError (background-bundle.js:1:266342) at At._onError (background-bundle.js:1:225864) at background-bundle.js:1:214483 _log @ background-common-bundle.js:1 background-bundle.js:1 [DEBUG][2024-09-08T13:58:19.864Z][17][[email protected]][imap.vivaldi.net] Connecting to imap.vivaldi.net : 993 background-bundle.js:1 [DEBUG][2024-09-08T13:58:19.864Z][17][[email protected]][imap.vivaldi.net] Entering state: 1 background-bundle.js:1 [DEBUG][2024-09-08T13:58:19.865Z][18][[email protected]][imap.gmail.com] Connecting to imap.gmail.com : 993 background-bundle.js:1 [DEBUG][2024-09-08T13:58:19.865Z][18][[email protected]][imap.gmail.com] Entering state: 1 background-bundle.js:1 [DEBUG][2024-09-08T13:58:19.865Z][19][[email protected]][login.foobarprovider.com] Connecting to login.foobarprovider.com : 993 background-bundle.js:1 [DEBUG][2024-09-08T13:58:19.865Z][19][[email protected]][login.foobarprovider.com] Entering state: 1Usually on Win11 running Vivaldi Snapshot builds. Opinionated about working efficiently with email. Folders are evil | Mail workflow: receive, read, reply, mark as read, done.
-
@WildEnte, given previous idles completed without issue the temporary errors seen may not be caused by Vivaldi; local system and / or network instability could be the cause.
