Hi Ronald,
Really, the problem was wich SE policy..
On 7/27/07, Ronald Cole [EMAIL PROTECTED] wrote:
Yup, there's a brain damaged SE policy for clamav in RHEL5, despite there
being no official clamav package in the distro. There also appears to be
some bugs in ClamAV as well, since running
I was reading the archives and it seems that powerpoint files can
cause problems with clamd. I ended up disabling the OLE2 scanning due
to problems with powerpoint files, but has anyone looked into this
further and found a real solution? (I am using clamav 91.1 on an
intel Mac Mini.)
I
On Jul 30, 2007, at 10:24 AM, Oliver Schwarz wrote:
kevin,
i ran into the same problem with clamd, but was able to dig a bit
deeper and figuring out, that as soon as an attachement was encoded
in octet-stream clamd would run nuts. the logs showed it crashed, but
the process was still alive
kevin,
that simply means, that the attachement, which you received with your
server, had another encoding.
ok, had you tried to reproduce this phenomena again, with the same
attachement sent?
it depends on the senders email-program, how those attached files get
encoded for sending via
Hello,
Which clamav file can change the below path ?
ClamAV-autoupdate[27333]: ClamAV updater /usr/local/bin/freshclam cannot be
run
Thx !
-
無限電郵儲存量，你就無需再擔心收件箱儲存空間會否過量! 立即使用Yahoo! Mail
___
