ISPConfig 2.2.13 released

[Xinil]

I just started having this same problem last night. All my incoming e-mails are automatically tagged as spam. If I uncheck "SpamFilter", all incoming e-mails work just fine. Here's the message I get for ALL e-mails if I check "SpamFilter" under an e-mail account:

Spam detection software, running on the system "dedicated145.krypt.com", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
gyssler@gmail.com for details.

Content preview: [...]

Content analysis details: (6.4 points, 6.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
0.0 MISSING_MID Missing Message-Id: header
0.0 MISSING_DATE Missing Date: header
-0.0 NO_RELAYS Informational: message was not relayed via SMTP
1.6 MISSING_HEADERS Missing To: header
2.9 TVD_SPACE_RATIO BODY: TVD_SPACE_RATIO
1.3 MISSING_SUBJECT Missing Subject: header
0.6 EMPTY_MESSAGE Message appears to have no textual parts and no
Subject: text
-0.0 NO_RECEIVED Informational: message has no Received headers
0.0 NO_HEADERS_MESSAGE Message appears to be missing most RFC-822 headers

[Xinil]

Alright, so I figured out the reason behind the e-mail problems. Basically, the /tmp directory on the linux box filled up. This was caused by one of my clients using the "Antivirus" checkbox. My /tmp directory was filled with "clamav" junk. Once I removed all files prefixed with "clamav", spamassassin started working properly again.

Is there a way I can prevent users from checking this box, or is there a method I can implement that will fix this from filling up my /tmp directory? Thanks.

[mlz]

You can change to clamd which is documented (recently) here in the forums. Personally, I'd love to see clamav go away and just have clamd, however there are a few trivial issues with clamd (during definition update, it occassionally hangs, easily rectified by killing the sucker and then restarting it).

Plus scanning is faster because it's not constantly loading/unloading from memory.

[minskog]

Originally Posted by mlz

You can change to clamd which is documented (recently) here in the forums. Personally, I'd love to see clamav go away and just have clamd, however there are a few trivial issues with clamd (during definition update, it occassionally hangs, easily rectified by killing the sucker and then restarting it).

Plus scanning is faster because it's not constantly loading/unloading from memory.

I migrate to clamavd in Sarge and runs without problems, never hangs

[TimeJunky]

Is there still same problems within the version 2.2.13 or do I have to change to clamd yet?

At the moment, I am updating from Version: 2.2.13 to .15 and was suffering with that spam failures of my vhosts.

[till]

You are posting to a very old thread. the Thread about ISPConfig 2.2.15 is here:

http://www.howtoforge.com/forums/showthread.php?t=14229

ISPConfig 2.2.15 uses the latest clamav package, as you can read in the release notes in the first post.