> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Eric Rostetter > Sent: Saturday, October 04, 2008 12:44 PM > To: [email protected] > Subject: Re: [Clamav-users] Handling of unknown > configuration lines (was Re:Stop it!) > > Quoting Charles Gregory <[EMAIL PROTECTED]>: > > > A lot of people seem to think it is 'proper' for a > mis-configured server > > to just "die" or fail to start. > > Yes, a lot of people do... :) > > > This makes sense when the server has an > > *obvious* function/effect and its failure will be noted by > interruptions > > in end-user performance/service. But when a mail filter > 'fails', mail > > goes through UNFILTERED, and UNNOTICED. This is just > WRONG. Sorry, it is. > > The OP was complaining that it did cause the mailer (exim) to stop. [...]
What he actually said was: "This is further aggravated by the fact that Exim does not know how to gracefully handle failures of clamav daemon." It doesn't stop, it issues a temporary local problem deferral, logs the reason in the panic log, and continues along just fine. I cannot think of a more graceful way to handle an issue that is severe and I cannot image a mailer continuing after it finds the A/V solution has gone away. It should *not* reject or accept the mail (deferral is appropriate) until the operator remedies the problem and one should take immediate note of any lines logged in the panic log as only severe issues not related to the actually mail receipt/send/delivery are logged to the panic log. I have a cron job that cats that log every few min and I respond to anything that is in there, and then clear the log. I don't want to beat a dead horse but one of the first responses to the original post was a derogatory comment about exim because the OP thought the way exim handles clam being gone was not "graceful". Rick -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
