Bug 287774 - folder with unread email, even though there is none unread
Summary: folder with unread email, even though there is none unread
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: Git (master)
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-28 17:34 UTC by Milian Wolff
Modified: 2017-01-07 21:28 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milian Wolff 2011-11-28 17:34:03 UTC
Version:           Git (master)
OS:                Linux

Since a few days, I have a folder where kmail keeps insisting that is has an unread email. It has none though. If I use the "jump to next unread email" action e.g. it just picks a random email.

Any idea on what I could debug here? Or at least how to fix it? It's distracting me.

Reproducible: Didn't try

Steps to Reproduce:
sadly, I have no clue what happened here

Actual Results:  
a folder with an unread email, even though there is none

Expected Results:  
if kmail says there is unread mail, I should be able to read this unread mail and make it read :)
Comment 1 Milian Wolff 2011-11-30 11:33:23 UTC
ran kmail1 on a different box today, turns out there is an invalid email there, no headers, no body - nothing. and that was unread :-/

not sure what to do with this report, probably I should make it into a bug that such bogus/broken emails should not be counted in unread status... and of course they should be shown in the list and not occur in the first place :)

Btw here is the raw email content of that broken email:

X-UID: 28458
X-Length: 2
Status: R
X-Status: N
X-KMail-EncryptionState:  
X-KMail-SignatureState:  
X-KMail-MDN-Sent:
Comment 2 ancow 2013-07-25 10:02:59 UTC
Could this be related to bug #279505 ?
Comment 3 Denis Kurz 2016-09-24 18:21:29 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 4 Denis Kurz 2017-01-07 21:28:58 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.