Bug 230390 - Messages are not properly deleted from POP3 server
Summary: Messages are not properly deleted from POP3 server
Status: RESOLVED DUPLICATE of bug 230072
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.13.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-12 00:55 UTC by Michael Schuerig
Modified: 2010-03-13 18:13 UTC (History)
1 user (show)

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 Michael Schuerig 2010-03-12 00:55:17 UTC
Version:           1.13.1 (using 4.4.1 (KDE 4.4.1), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.32-3-686

Since my upgrade from KDE 4.3.4 to 4.4.1 and the respective versions of KMail, I'm having trouble with messages not being properly deleted from the POP3 server. As a result, the affected messages are retrieved from the server again and again on each periodic mail check. This only stops when I delete these messages from the server by some other means. KMail is configured to immediately delete fetched messages from the server.

It is not the case that no messages are deleted from the server. Things work correctly for a period, then suddenly, messages are not deleted properly anymore and in turn are retrieved endlessly. A way to provoke this behavior is to suspend the computer and later resume it.

As far as I can tell, enabling or disabling pipelining doesn't have an effect; the server reports that is supports pipelining. Normally, I'm using SSL, but with it switched off, I noticed that apparently KMail does send DELE messages, however they are ineffectual. I've only been able to observe anything after things already were broken. I've not been able to observe the breaking itself.

This might all sound like the POP3 server is at fault. However, it is a widely-used server at my ISP, other users I know of don't have similar problems -- and my trouble started exactly when I updated to KDE 4.4.1.
Comment 1 Björn Ruberg 2010-03-13 18:13:39 UTC

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