Bug 279073 - IMAP e-mails get marked read with delay
Summary: IMAP e-mails get marked read with delay
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-01 19:17 UTC by Silver Salonen
Modified: 2017-01-07 21:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Silver Salonen 2011-08-01 19:17:28 UTC 
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

I have set e-mails to get marked as read after "0 seconds", but actually there's a delay of about 1 second after I select an e-mail. Sometimes it's more, sometimes less, so maybe it's just the "slowness" of the Akonadi IMAP resource?

Reproducible: Always

Steps to Reproduce:
Select an unread e-mail

Actual Results:  
The e-mail gets marked as read with a delay of 1-3 seconds

Expected Results:  
The e-mail should get marked instantly (was working fine in KMail1)
Comment 1 km 2011-08-06 22:25:56 UTC 
I can confirm the delay when marking as read manually.
Comment 2 Silver Salonen 2012-01-31 11:05:22 UTC 
Still relevant in 4.8.0.
Comment 3 Bernd Oliver Sünderhauf 2012-11-26 20:20:36 UTC 
Can't reproduce in 4.9.3. Do you still experience this delay?
Comment 4 Silver Salonen 2012-11-27 08:09:04 UTC 
Yes, I do. Sometimes some e-mails don't get marked read at all, but I guess that's another issue.
Comment 5 Denis Kurz 2016-09-24 18:03:10 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 6 Denis Kurz 2017-01-07 21:50:00 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.