Either none of the images i have saved from spam match that database (quite
possible) or clamscan works slightly differently than clamd while scanning
emails.
Is it possible that clamscan requires and exact match while clamd/clamav-milter
only requires a partial match because its testing each a
Carl Thompson wrote:
making the signature isnt the problem. the problem is that clamav
will only identify the signature if its on its own (such as the
signature is a file all its own) it will not identify email with the
signature information in it.
as an example i took a spam based email image
making the signature isnt the problem. the problem is that clamav will only
identify the signature if its on its own (such as the signature is a file all
its own) it will not identify email with the signature information in it.
as an example i took a spam based email image and made a signature
making the signature isnt the problem. the problem is that clamav will only
identify the signature if its on its own (such as the signature is a file all
its own) it will not identify email with the signature information in it.
as an example i took a spam based email image and made a signature
Carl Thompson wrote:
> I have followed the documentation i've found and created custom database
> files that identify files that stand alone without a problem using sigtool
> --md5 > /path/to/custom.db
Try:
sigtool --md5 > /path/to/custom.hdb
--
Best regards,
Christoph
