On Thu, 2004-05-27 at 14:08, Don Levey wrote: > NOTE: I am not really expecting an answer to this, but didn't find much of a > discussion of these errors in the archive. Therefore, I'm writing my > experiences in the hopes that others with these errors can work around their > problems.
> So far, so good. I then restarted clamd and clamav-milter to make sure I > was running the new version. At this point, mail seemed to be going through > unscanned, with the following lines in my maillog: > > May 27 12:28:06 davinci sendmail[32077]: i4RGS5a2032077: Milter: data, > reject=451 4.7.1 Please try again later > May 27 12:28:36 davinci sendmail[32079]: i4RGSU3h032079: Milter: data, > reject=451 4.7.1 Please try again later > May 27 12:31:27 davinci sendmail[32145]: i4RGVQgi032145: Milter: data, > reject=451 4.7.1 Please try again later > > I isolated these problems to the command-line options being used when > starting up. When I was working properly, I had started manually using: > > clamav-milter --quarantine-dir=/var/run/clamav/quarantine --max-children=10 > --force-scan --local --postmaster-only --server=localhost > local:/var/run/clamav/clamav-milter.sock > > However when running 'service clamav-milter restart' I found I was running: > > clamav-milter --quarantine-dir=/var/clamav/quarantine --max-children=10 > --force-scan --local --postmaster-only --server=localhost > local:/var/run/clamav/clamav-milter.sock --config-file=/etc/clamav.conf --he > aders --noreject --outgoing > > I isolated the problem to the clamav.conf file, but have not delved any > deeper than that I may have found the problem. The clamuko options were enabled by default in the config file, do I hadn't changed them. I disabled all of them, and that appears to have done the trick (though it may be too early to tell). > > This led me to what I think was the problem: I moved the clamav-milter.sock > file out of the way and tried to start again. The milter started normally, > and seems to be processing mail correctly. Eventually I'll get to whatever > is in the clamav.conf file that is causing the hang-up mentioned earlier. > Simply for reference, I'm pasting the options in the conf file below. I did enable the FixStaleSocket, just in case, on Nigel's advice. > # Note: Clamuko/Dazuko is not configured/running > ClamukoScanOnOpen > ClamukoScanOnClose > ClamukoScanOnExec > ClamukoIncludePath /home > ClamukoMaxFileSize 1M > ClamukoScanArchive > Hopefully, this info will help someone else who finds themselves in my position. -Don ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
