Bug 60597 - all emails loaded twice after new security settings
Summary: all emails loaded twice after new security settings
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: pop3 (show other bugs)
Version: 1.5.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2003-07-01 21:57 UTC by Eggert Ehmke
Modified: 2008-11-07 13:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eggert Ehmke 2003-07-01 21:57:57 UTC
Version:           1.5.2 (using KDE 3.1.2)
Installed from:    SuSE
Compiler:          gcc version 3.3 20030226 (prerelease) (SuSE Linux)
OS:          Linux (i686) release 2.4.21

I have kmail configured to leave my mails on the pop3 server. Now I changed the settings in the configuration dialog for the pop3 server (after checking server capabilities, SSL and APOP were enabled, which were disabled before). When I downloaded my mail next time, all mail on the server was fetched again, leaving double entries for each mail. I did not change back to the old configuration, now everything works fine again. So this happens only after change of the settings.
Comment 1 Eggert Ehmke 2003-07-28 11:15:56 UTC
This can be reproduced. It happened again, on a different machine, after a complete SuSE 8.2 
new installation. 
Eggert 
Comment 2 Thomas McGuire 2007-12-12 23:38:35 UTC
Reassigning the bugs of the SMTP, IMAP and POP ioslaves to kdepim-bugs.
Comment 3 Dominik Tritscher 2008-08-31 23:00:43 UTC
Can't confirm that using KMail 1.10.0 from Kubuntu KDE4.1 packages
Comment 4 Michael Leupold 2008-11-07 12:20:10 UTC
I can't confirm using 1.10.1 either. Messages are not reloaded after changing the setting. If the server has trouble supporting the "leave messages on server" feature, kmail will now even warn about it and suggest to disable this option. Lack of support for this feature might have been related to server not properly supporting message ids in the first place.
Comment 5 Eggert Ehmke 2008-11-07 13:50:34 UTC
I suggest to close this bug. It was written 2003 for SuSE 8.2. On my actual system this has not happened again.