This seems like a rather destructive behavior on the part of Qmail-Scanner.
(I haven't seen a comment about this in the archives - I'll admit I didn't go through every month) I've seen this happen several times, and the last time was EXTREMELY bad - happened for a full day. Here's an example @40000000405d336b1c406624 tcpserver: ok 19256 mail.bkwm.com:216.201.150.40:25 c-24-1-180-209.client.co mcast.net:24.1.180.209::1992 @40000000405d33703302307c X-Qmail-Scanner-1.20st:[mail107984982856819257] clamuko: corrupt or unknown clamd scanner error or memory/resource/perms problem - exit status 2 What had happened is that the server's video card had gone out, thus taking the machine down. After replacing the server, and powering back up - I didn't get an error message from clamd - it turns out that the /tmp file wasn't removed by the script (which it is supposed to do), so clamd refused to start up. Okay - that's acceptable. However, what the mail server did is continue to receive messages, and instead of leaving the messages in the queue until the error went away - it would hit the "can't find clamd" and proceed to throw the message away. It seems like it would be more reasonable for the scan process to go 'Process can't work!' and then either feed the mails through (maybe with a message to the admin that the program is buggering up), or store them in queue, again, with a message to the admin. In either case, I'd have spotted it faster than I did. Is there any way around this behavior? Troy Belding ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
