Bug 323767 - emails being duplicated repeatedly when selecting a maildir folder after a mail check
Summary: emails being duplicated repeatedly when selecting a maildir folder after a ma...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.11.3
Platform: Debian unstable Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-20 09:58 UTC by Thomas Fjellstrom
Modified: 2017-01-07 22:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot of bug (491.72 KB, image/png)
2013-11-19 16:04 UTC, Thomas Fjellstrom
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Fjellstrom 2013-08-20 09:58:26 UTC
Over time, I see duplicate messages get filtered into folders, even long after the original was received.

The odd parts:

- occasionally an incoming/inbox folder will show a low number of unread messages (< 10) , but upon selecting the folder, one of two things happen:
 1. the unread count goes back to 0, or the proper unread count if there are actually some new messages in that folder.
 2. the unread count jumps to over 30-40 messages very briefly, and messages appear as unread for a short time, then they get filtered into folders. These are almost always duplicates.

Typically this happens after sitting for a while and some new messages have been received and filtered.

Reproducible: Always

Steps to Reproduce:
1. set up one or more pop3 accounts
2. set up some "move into" filters
3. watch as duplicates get filtered into folders
Actual Results:  
Duplicated messages

Expected Results:  
no duplicated messages
Comment 1 Thomas Fjellstrom 2013-10-17 19:56:06 UTC
Is there any chance this is fixed in 4.11? Would a video to show what is happening be useful?

I get hundreds of duplicates a day. every single time it goes to fetch mail, it'll show previously downloaded mail (as unread no less) in the inbox, then re-filter it.
Comment 2 Thomas Fjellstrom 2013-11-19 16:04:20 UTC
Created attachment 83638 [details]
screenshot of bug

In case some proof is wanted, here it is.
Comment 3 Thomas Fjellstrom 2013-11-24 11:09:04 UTC
I've since upgraded to 4.11.3 and I think its actually worse, and leaves some of the copies in the source folders.

I have one folder that has had one new valid email since Tuesday Nov 19th 2013. There are now 295 copies of that one single email in the destination folder. Thats just for one single email. There are many others that are being duplicated like this as well. hundreds of duplicates a day now most likely.

May I ask why it's even putting them in the inbox folders at all at any point? Filters should ideally happen before the emails are even saved to disk.
Comment 4 Thomas Fjellstrom 2013-11-25 10:45:27 UTC
New information.

It isn't just new messages, or even recently new messages being duplicated.

Months old messages, that have been marked as read for ages are being duplicated, and put in their original inbox folder but marked as unread.
Comment 5 yuzyk 2014-01-08 20:17:31 UTC
With 4.11.4 on Fedora 19 I see this every morning when I first check mail after waking up. Opening my Inbox increments the unread counter up, then decrements it to the value I first see, suggesting that mails are re-filtered. Then I find dupes throughout folders that are the destination for my filters. I've learned to check my Inbox first, otherwise mails that are read and deleted in those other folders are put back as dupes marked New.
Comment 6 Denis Kurz 2016-09-24 18:15:06 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 7 Denis Kurz 2017-01-07 22:38:19 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.