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 – just freaking out and using slowly all > available cpu-cycles until nothing was left. the kernel process was > getting a bit stressed and used around 30% (DC 1.66 here) and clamd > the rest. > > please just look into your logs and report back, if these > attachements were sent encoded in octet-stream.
The attachments in the email were encoded in base64. I grep'd the logs for amavis and didn't find anything that said octet, so I'm not really sure if that answers the question or not. I also tried upping the logging in clamd.conf, but the best I could get was pass/fail messages. No additional details show up in the clam log. Maybe there is some option I am missing. LogVerbose was set to yes. Kevin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
