Switched from clamavmodule to clamd

Michael Mansour micoots at yahoo.com
Tue May 27 13:00:05 IST 2008


I've just switched from clamavmodule to clamd on one
of my mail servers (trying it before moving the rest).
The delay between the time it takes to patch
Mail::ClamAV is unfortunately too long so decided to
switch finally.

I've gone through and followed this wiki item:


which basically detailed the process for me.

I'm just hoping someone can verify the changes so I'm
comfortable with the way it's working (MailScanner
lint was ok).

I use the clamav, clamav-db and clamd from Dag Wieers'

In the MailScanner.conf:

Virus Scanners = clamd
ClamAVmodule Maximum Compression Ratio = 1000
Clamd Port = 3310
Clamd Socket = /tmp/clamd.socket
Clamd Lock File = /var/lock/subsys/clamd

In the /etc/clamd.conf file:

ScanMail no

# With this option enabled ClamAV will try to detect
phishing attempts by using
# signatures.
# Default: yes
#PhishingSignatures yes

# Scan URLs found in mails for phishing attempts using
# Default: yes
#PhishingScanURLs yes

# Perform HTML normalisation and decryption of MS
Script Encoder code.
# Default: yes
#ScanHTML yes

Do I need to turn off the defaults above as
MailScanner handles these or just leave things as is?

Also, does MailScanner handle the clam definition
updates automatically? or do I need to enable a
freshclam run? or cron freshclam?



      Get the name you always wanted with the new y7mail email address.

More information about the MailScanner mailing list