Bug 296889 - KMail reports wrong number of received messages
Summary: KMail reports wrong number of received messages
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: UI (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-27 15:54 UTC by Cláudio F. Gil
Modified: 2017-01-07 21:50 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 Cláudio F. Gil 2012-03-27 15:54:31 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Build Identifier: 

I've configured KMail to show a window notification when new mail arrives. The notification works but reports the wrong number of received messages. The notification can say something like "Received 7 messages in Inbox" but the unread count is 2 (were previsously it was 0 and not shown) and the Inbox count is way above 7.

Reproducible: Always

Steps to Reproduce:
1. Activate notifications for new mail and show notification in a new window (i)
2. Mark all mails as red.
3. Receive new mail.
Actual Results:  
KMail shows a notification say I received more messages than I actually received.

Expected Results:  
KMail should show a notification saying "X messages were received" when "X messages were received".

I have no filters. The account is a GMail IMAP. The messages are being received in the Inbox. No other messages were received and filtered on GMail side.
Comment 1 Denis Kurz 2016-09-24 18:21:37 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 2 Denis Kurz 2017-01-07 21:50:37 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.