hi,

in clamav-0.80nb3 the makefile reads

(...)
CONFIGURE_ARGS+=      --disable-clamav
(...)

so after building and installing, clamav is installed but doesn't run 
(see the example below):

> fulcrum: {1} clamscan
> LibClamAV Error: cl_loaddb(): Can't open file _0023_0004_003/daily.cvd
> ERROR: Unable to open file or directory
>
> ----------- SCAN SUMMARY -----------
> Known viruses: 23982
> Scanned directories: 0
> Scanned files: 0
> Infected files: 0
> Data scanned: 0.00 MB
> I/O buffer size: 131072 bytes
> Time: 1.185 sec (0 m 1 s)
> fulcrum: {2}

my question now is, why is clamav/clamscan disabled by default?

not only a cli-based AV-scanner is a nice tool, e.g. amavisd-new relies 
on it (the cli part of e.g. clamav) as a backup scanner in case the 
primary one fails; for clamav this is the daemon, clamd, which listens 
on a UNIX-socket or via IP, running usually as the primary AV-scanner 
for amavisd-new, and clamscan, the cli part as backup.

are there any issues that made disabling clamscan mandatory? if not, 
why not change it?

regards & tia,

-- 
:x!

timo