Bug 198017

Summary:	spamassassin claims 100% CPU when adding imap account
Product:	[Applications] kmail	Reporter:	David Rankin <drankinatty>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Unspecified
Latest Commit:		Version Fixed In:

Description David Rankin 2009-06-27 02:08:09 UTC

Version:            (using KDE 4.2.90)
Installed from:    SuSE RPMs

If kmail is configured to use spamassassin before an imap account is added, spamassassin will claim 100% of CPU when imap account is added.

After shutdown and restart spamassassin claims up to 52% of CPU until all messages on imap server are processed which renders kmail unusable for hours when 50,000+ messages reside on the server

This also causes POP checking to fail, if keep messages on server is configured giving the error:

Your POP3 server (Account: Suddenlinkmail.com) does not support the UIDL command: this command is required to determine, in a reliable way, which of the mails on the server KMail has already seen before;
the feature to leave the mails on the server will therefore not work properly.

UIDL command works fine when spamassassin isn't operating on the imap account.

Spamassassin need to be reniced or reprioritized to prevent brining kde4 to its knees when a large imap account is added.

Let me know if you need anything else.

Comment 1 Laurent Montel 2015-04-12 10:17:34 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.