Bug 342508 - IMAP based messages not being marked as read when reading done via web gui.
Summary: IMAP based messages not being marked as read when reading done via web gui.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-05 13:21 UTC by Piotr Gbyliczek
Modified: 2018-01-31 16:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr Gbyliczek 2015-01-05 13:21:11 UTC
When using an IMAP account (Google mail) messages are not being synchronised to read state when they were viewed through web gui. 

Before update to Fedora 21 (KDE 4.14.3) reading message in either KMail or web gui resulted in that message being marked as read in the other one after short while. 

Right now reading message in KMail does mark them properly so they are marked read in web gui, but reading message in web gui does not result in it marked as read in KMail. I've tried to synchronize manually, but neither initiating "Update Folder" on specific forder nor "Update folder and all it's subfolders" on any of the folders above worked.

Reproducible: Always

Steps to Reproduce:
1. Read message via web interface
2. Wait for KMail to do automatic synchronization of the IMAP account.

Actual Results:  
Messages read via web interface are not marked as read in KMail

Expected Results:  
Messages read via web interface are marked as read in KMail
Comment 1 Denis Kurz 2017-06-23 19:59:21 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:49:34 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.