Kmail + IMAP: Duplicates mails with attachment

[Florian Jensen]

Binary package hint: kdepim

I use an IMAP Server.
All mails with an attachment get duplicated. I think it has something to do with the Filters.

[Daniel Hahler (blueyed)]

You have all your mail twice in your inbox?

Which KDE version are you using?

I've experienced also "endless duplication" for some mails with (large) attachments.

[Florian Jensen (florian.jensen)]

I also have it with mails which have attachments.

KDE Version: 3.5.6
Kmail: 1.9.6

[Florian Jensen (florian.jensen)]

Just wanted to say ... this problem still exists on feisty.

[Sean (svk-sweng)]

I have seen this when I am using IMAP with MS Exchange 2003 XP server. I had to switch to disconnected imap to avoid seeing duplicates.

I am using Feisty.

Sean

[Scott Kitterman (kitterman)]

Do you see this with KDE 3.5.7? It is supposed to have significant IMAP improvments.

[Daniel Hahler (blueyed)]

Scott, there are a lot of improvements and this _may_ be fixed, but unfortunately IMAP filters are quite broken. You can only filter one mail after another and only manually.
See bug 116593.

[Florian Jensen (florian.jensen)]

Haven't encoutered the problem yet. But yes, filters seem to be quite broken. They don't filter automatically anymore.

[Scott Kitterman (kitterman)]

Right and there are other bugs about filters. Does THIS problem happen any more?

[Daniel Hahler (blueyed)]

Scott, with me this problem got triggered by the filters. So when the filters do not work, the "chain" which leads to this bug is broken before already.
I'm not manually filtering often now, but moving the mails manually instead ("m").

It's likely to be fixed, but we cannot say for sure at the moment.

[Launchpad Janitor (janitor)]

[Expired for kdepim (Ubuntu) because there has been no activity for 60 days.]

[Scott Beamer (angrykeyboarder)]

Freaky

[Marcus Asshauer (mcas)]

This bug still exists in KDE 3.5.10.

[Jonathan Thomas (echidnaman)]

How is it with KDE 4.1.1?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!