Bug 330346 - Multiple notifications etc if message is assigned to multiple IMap folders
Summary: Multiple notifications etc if message is assigned to multiple IMap folders
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.12
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-23 23:00 UTC by Mike Krutov
Modified: 2017-01-07 22:29 UTC (History)
0 users

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 Mike Krutov 2014-01-23 23:00:50 UTC
My mailbox on Gmail is set up on server-side to put some messages into "Important" & "kde".
In case such a message arrives, multiple misbehaviours happen:
1) KMail Notification shows up with 
"New message in Inbox"
"New message in Important"
"New message in KDE"

E.g. multiple times on same message.
--
2) When I read message in Inbox (or KDE or Important) other two directories do not get updated message status, and display that message as unread till I switch to that directory.

Reproducible: Always

Steps to Reproduce:
1. Configure your IMAP provider (not tested with non-gmail account) to deliver message to multiple directories
2. Get such message
3. Read it in 1 directory
Actual Results:  
step2 : multiple notifications appear (each notification is duplicated)
step3: when I read the message, it updates its status only in 1 directory. Amount of read messages in other directories is not updated.
When I switch to other directory in UI, for about a second or two message stays bluish (unread) and then changes it status to read.

Expected Results:  
step2: 1 notification for each unique message
step3: simultaneous updates on unique messages for each directory they are present in.
Comment 1 Denis Kurz 2016-09-24 18:24:20 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 Mike Krutov 2016-09-24 18:52:52 UTC
I'm not using KDE for more then 2 years already so can not confirm.
Comment 3 Denis Kurz 2017-01-07 22:29:24 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.