Jesper Juhl <mailto:[EMAIL PROTECTED]> wrote: > With my setup it goes into a queue, but only if no scanner at all is > available. If clamd dies my setup falls back on using clamscan which > is slower and causes mail to queue up, but it's better than letting it > through unscanned. > > It has only happened once that clamd died, so I don't consider it a > huge problem, but just to be on the safe side I have setup a cron job > to monitor it every 5 minutes and start it up again if it should > happen again - so, that way I should only be relying on clamscan for > a maximum of 5min which is not a problem. And should both fail I'll > queue mail instead of letting it through unscanned (and yes, the size > of the queue is monitored so I > get an alert if it should ever build up).
That's interesting. Would you be willing to share more details of your setup and how it all works? Is this MailScanner you're talking about? -- Michael St. Laurent Hartwell Corporation ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
