Jim Maul wrote:
Actually, it technically is clamscan, but for the installation i used
(www.qmailrocks.org) a step in there says to copy clamscan to clamdscan so
running clamscan and clamdscan effectively means the same thing. So yes
technically you are correct, but for my setup, my statement is co
Quoting Jim Maul <[EMAIL PROTECTED]>:
> Actually, it technically is clamscan, but for the installation i used
> (www.qmailrocks.org) a step in there says to copy clamscan to clamdscan
Arrr! Why are they advising to do such a stupid thing.
> so
> running clamscan and clamdscan effectively means
Actually, it technically is clamscan, but for the installation i used
(www.qmailrocks.org) a step in there says to copy clamscan to clamdscan so
running clamscan and clamdscan effectively means the same thing. So yes
technically you are correct, but for my setup, my statement is correct as
well.
Hi all,
I think you should say clamscan with --mbox because I haven't found
--mbox flag for clamdscan isn't it?
Nevertheless if a similar flag exist flag exist for clamdscan (0.65
release) I will be very interrested in.
Best regards,
Jose THOMAS.
Le 28 janv. 04, à 16:47, Jim Maul a écrit :
Sorry to have bothered everyone with my problem here but i have found the
resolution.
using the --mbox flag on the command line with clamdscan correctly
identifies about 95% of all viruses in email in my quarantine directory.
Thanks to all for the hints (changing softlimit and restarting clamd).
