Bug 179385 - IMAP-Mails duplicating when using built-in spam-assistant
Summary: IMAP-Mails duplicating when using built-in spam-assistant
Status: RESOLVED DUPLICATE of bug 95064
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-02 16:58 UTC by Peter Wendel
Modified: 2009-03-19 00:37 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 Peter Wendel 2009-01-02 16:58:24 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    SuSE RPMs

kmail works fine and stable...

... but on one special email-account kmail begans wondrously copying every mail in the inbox of that IMAP-Account everytime kamil looks for a change or a new mail arrives. This just happens if I use the spam-assistant, which is using spam-assassin.

I don't now exactly, if it reproduces only the original or copies all mails found in there, because all mails are identically the same.

But I think that this is a bug that concerns to a special combination of kmail with the external mail system of my webhosting-account at STRATO-Germany.
I notice the bug ONLY with IMAP-Accounts vom STRATO, all others work fine.

I remember the same bug just a year ago, when i was using an older openSuse-Distribution, but for some work-specific reasons I changed to Thunderbird.

Using Thunderbird, the behaviour is normal.

If I use kmail without spam-assistant, the behaviour is normal too, but unfortunately there's no button to remove the function from one single email-account or stop the spam-assistant in any way.

Reproducing is very easy: Just put an Strato-Imap-Account to kmail and use the spam-assistant with spam-asassin.
Comment 1 Thomas McGuire 2009-01-04 14:13:33 UTC
This is probably fixed with KDE 4.1.4, see bug 95064.

*** This bug has been marked as a duplicate of bug 95064 ***