Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 406063 - kde-base/kmail-4.7.4-r1: clamav integration may crash kmail
Summary: kde-base/kmail-4.7.4-r1: clamav integration may crash kmail
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: Gentoo KDE team
Whiteboard: tracking upstream
Depends on:
Reported: 2012-02-27 19:15 UTC by Joerg Schaible
Modified: 2013-09-12 09:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Schaible 2012-02-27 19:15:48 UTC
I have a IMAP resource with offline support. KMail uses clamav with the help of the script to scan the mails on the server by downloading them, adding a virus flag and put them back to the server. Unfortunately this script is buggy and it will double the size of the mail each time it is scanned. One mail that I have in the box since ~3 weeks has meanwhile a size of 540MB causing KMail to crash after allocating more than 4GB of memory and bringing the complete system nearly to halt because of major IO/swapping activity.

Reproducible: Always

Steps to Reproduce:
1. Ensure that you have clamav installed and running
2. Create a resource for an IMAP account with offline support
3. Ensure that you have a mail with a bigger attachment in your inbox
4. Trigger the scan
5. Repeat last step

Actual Results:  
Memory usage is constantly growing, mail on server doubles with each scan.

Expected Results:  
Actually I do not expect KMail to rescan a mail that has already a X-Virus-Flag, nor do I expect the mail to double.

How can I clean up this mess now on my server?
Comment 1 Joerg Schaible 2012-02-27 19:42:52 UTC
Sorry, means kmail-4.7.4-r1 in subject
Comment 2 Joerg Schaible 2012-03-03 23:00:18 UTC
The problem arises with any AV integration filters currently and its not the scripts, it has to be a changed behavior of KMail itself. See upstream bug description.
Comment 3 Michael Palimaka (kensington) gentoo-dev 2013-08-20 13:14:28 UTC
Does this issue persist with a more recent version of kmail?