Hi > Because clamscan and clamd are different programs. clamd.conf is the configuration file for clamd, the clamav daemon. clamscan is another program entirely configured from the command line.
Sorry, but re-read my mail please. I know that these are two very different beasts. However not having ScanMail in clamd.conf should do the same to clamd, that --no-mail does to clamdscan. I have no problems using clamscan --no-mail, but I do have problems using clamdscan without ScanMail in clamd.conf. So my question is still unanswered. Regards, Steffen Steffen Heil schrieb: > Hi > > I came across a .eml file once again, that causes a segfault in clamd. > However, since I had that issue a few days ago and the clamav team > corrected that bug aleady, I did not post a bug report. > > However, since about a week, my mail servers are configured NOT to use > ScanMail. > > If I use clamscan to scan the .eml-File, I get a seg-fault. > If I use clamscan --no-mail to scan the .eml-File, I get "ok", which > is correct - the file is NOT infected. > > Anyway, clamd produces a segfault entry in the log, when I scan the > file with clamdscan. > I do not understand that, since I have ScanMail option DISABLED in > clamd.conf. > > Why is it ignoring ScanMail ? > Or is there something else, I forgot? > > Regards, > Steffen
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
