Bug 186202

Summary:	emails are redownloaded and marked as "new" after changing login security method
Product:	[Unmaintained] kmail	Reporter:	Simon Schmeisser <mail_to_wrt>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	bjoern
Priority:	NOR
Version:	1.11.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Simon Schmeisser 2009-03-05 11:50:45 UTC

Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

I changed the login security for my gmx.net email account (using pop3) from CRAM-MD5 to APOP. I used the "Determine server capabilities" button to check which one I should use. (BTW, this didn't find CRAM-MD5 even though it is still supported on the server side till 10.3.09)
After a short delay kmail started downloading all the messages I had in my inbox again (ca. 5000).
Expected Behavior:
Download no mails, because all of them are remembered as already read.
Observed Behavior:
Downloads all mails again. I then have every mail twice in my local inbox, one read and one marked as new.

Comment 1 Jaime Torres 2009-03-05 12:45:02 UTC

There is a new warning shown when the "Determine server capabilities" is used and the server does not seem to support unique message numbers.

This is in kmail 1.11.90 (kde 4.2.65) svn trunk r933886.
Without the unique message numbers, the probability to get duplicated messages is very high.

The server does not seem to support unique message numbers, but this is a requirement for leaving messages on the server; therefore, this option has been disabled.
Since some servers do not correctly announce their capabilities you still have the possibility to turn leaving fetched messages on the server on.

Comment 2 Simon Schmeisser 2009-03-05 13:41:24 UTC

I have written the GMX.net team and requested feedback from them ... let's see if anything happens ...

Comment 3 Björn Ruberg 2010-03-09 09:51:57 UTC

Do we have a bug here? I think not.

Comment 4 Laurent Montel 2015-04-12 10:18:57 UTC

Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.