Bug 329692

Summary:	New email notification after message state changes
Product:	[Applications] kmail2	Reporter:	artur.glavic
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel
Priority:	NOR
Version:	4.12
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	kmail folder receive email kmail folder reply email KDE message receive email KDE message reply email Notification settings

Description artur.glavic 2014-01-07 14:24:27 UTC

I'm using KMail with an IMAP account together with the DavMail Gateway to access my companies email server. When a state of an email changes in my IMAP account (e.g. when I answered to a mail and the answered symbol shows up) the new email arrived notification is shown.

Reproducible: Always

Steps to Reproduce:
1. Setup KMail to show notifications on new emails (Settings->Configure notifications->New email notify)
2. Receive an email in IMAP account
3. Answer to the email so that the list shows the blue arrow for a message you have answered to
4. The KDE message systems shows a message indicating a new mail arrived although it did not
Actual Results:  
New message notification is shown when email state changes.

Expected Results:  
Only show notifications when new emails arrive.

Comment 1 Laurent Montel 2014-03-23 15:17:35 UTC

it shows that it's arrived where ?
in which folder ?

Comment 2 artur.glavic 2014-03-23 15:22:47 UTC

(In reply to comment #1)
> it shows that it's arrived where ?
> in which folder ?

You can setup the KDE notification system to notify you when new messages arrive, which I did as described in the bug report. 
So shortly after I send e.g. a reply to a message KMail changes the message state to answered and the KDE message for a newly arrived message pops up and the bing sound is played as if I would have received a new message. 

The folder does not show a new message and it does not depend on the folder the email was in before.

Comment 3 Laurent Montel 2014-03-23 15:46:26 UTC

By default it doesn't show change state so I don't know how you can have this bug

Comment 4 artur.glavic 2014-03-23 15:59:39 UTC

(In reply to comment #3)
> By default it doesn't show change state so I don't know how you can have
> this bug

Do you need any additional information, screenshots etc.? I have the same behavior at my other machine which uses googles IMAP account.

Comment 5 Laurent Montel 2014-03-23 16:32:55 UTC

Yes please
Screenshot about notification.
It's google imap account ?

Comment 6 artur.glavic 2014-03-24 13:00:46 UTC

Created attachment 85709 [details]
kmail folder receive email

Comment 7 artur.glavic 2014-03-24 13:01:31 UTC

Created attachment 85710 [details]
kmail folder reply email

Comment 8 artur.glavic 2014-03-24 13:01:52 UTC

Created attachment 85711 [details]
KDE message receive email

Comment 9 artur.glavic 2014-03-24 13:02:23 UTC

Created attachment 85712 [details]
KDE message reply email

Comment 10 artur.glavic 2014-03-24 13:07:46 UTC

(In reply to comment #5)
> Yes please
> Screenshot about notification.
> It's google imap account ?

I have the same issue on my google imap account and at work using imap to connect to a DavMail gateway. Both use the normal akonadi imap account.

I have attached screenshots of the KDE messages and kmail folder view after I actually receive a new message and after I replied to the same message. As you can see the KDE message is exactly the same.
I have also attached a screenshot of the notification options dialog.

My KMail version is now 4.12.3

Comment 11 artur.glavic 2014-03-24 13:08:05 UTC

Created attachment 85713 [details]
Notification settings

Comment 12 Denis Kurz 2016-09-24 18:13:43 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 13 Denis Kurz 2017-01-07 22:41:59 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.