Bug 341134 - Does not update read count from IMAP server
Summary: Does not update read count from IMAP server
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.13
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on: 156548
Blocks:
  Show dependency tree / graph
 
Reported: 2014-11-20 16:26 UTC by Alexander Potashev
Modified: 2017-01-07 22:18 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Potashev 2014-11-20 16:26:33 UTC 
+++ This bug was initially created as a clone of Bug #156548 +++

Version:           1.9.7 (using KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I have kmail configured for online imap, checking all folders every few minutes, I also have another mail client configured with the same IMAP server.

If I mark email as read with another client while kmail is running, the messages are marked correctly on the IMAP server but kmail does not update the message status displayed, even if I force kmail to check messages on the server.
Comment 1 Alexander Potashev 2014-11-20 16:27:46 UTC 
To make it clear, there are still two problems (not fixed since KMail1 age):
 1. Unread messages counter is not updated,
 2. Messages becoming unread on the server are not marked as unread in KMail after syncing.
Comment 2 Denis Kurz 2016-09-24 20:35:36 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:18:26 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.