Summary: | Add virus scanning results to fancy header | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | _ <praseodym+kdebugzilla> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | wishlist | CC: | bjoern, gschintgen, luigi.toscano |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
kmail_clamav.sh with X-Virus-Details
ClamAV script called up by kmail filter |
Description
_
2005-01-21 16:17:17 UTC
Created attachment 9204 [details]
kmail_clamav.sh with X-Virus-Details
Comment on attachment 9204 [details]
kmail_clamav.sh with X-Virus-Details
The script probably needs some performance improvements, but it's quite fast
already.
For attachment #9204 [details]: the X-Virus-Details line should read
echo "X-Virus-Details: `echo "$clamoutput" | grep FOUND | sed -e 's/^[^:]*: //' -e 's/ FOUND.*$//'`"
instead - this removes the space before "FOUND".
Another idea would be to detect a possible clamassassin installation. But I agree it would be interesting (but not really useful) to have at least the name of the beast. Well then you at least know that there is a virus detected. As both my spam and virus mails go into one folder I have to check the headers to find out whether the mail is a virus or not. Created attachment 21566 [details]
ClamAV script called up by kmail filter
Comment on attachment 21566 [details]
ClamAV script called up by kmail filter
I think it is important to include the name of the Virus identified. It is
possible that the signature is not selective enough and a clean email is
wrongly labelled. For example I have seen some discussion of this nature
concerning the Email.Faketube virus.
In addition the virus database is updated and names can be changed. I have
enabled manual checking. The current script does not remove the old analysis
results. I offer the following attachment.
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding. Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2. |