Bug 280154 - A single mail gets duplicate entries in the message list
Summary: A single mail gets duplicate entries in the message list
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-15 20:19 UTC by Albert Astals Cid
Modified: 2017-01-07 21:40 UTC (History)
3 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 Albert Astals Cid 2011-08-15 20:19:52 UTC 
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

Sometimes i get a mail and it shows twice in the message list. Then when i remove one of them the other one gets automatically deleted too. This is on a pop account so it is all local mail (no server involved). If after deleting the email i undo the deletion only one email comes back from the dead.

Reproducible: Sometimes

Steps to Reproduce:
No steps, just happens once a day or so.

Actual Results:  
Two entries appear for the same email

Expected Results:  
Just one entry per email

OS: Linux (x86_64) release 3.0-ARCH
Compiler: gcc
Comment 1 Ian Powell 2012-04-23 21:43:51 UTC 
I get the duplicates when a filter is run automatically on incoming mails.  Turn the auto off and run it manually and you won't get duplicates
Comment 2 Tristan Miller 2016-08-17 19:46:02 UTC 
Ian, you are possibly experiencing Bug 283682.
Comment 3 Denis Kurz 2016-09-24 18:18:54 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:40:14 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.