When Declude experiences problems it completely halts all mail going in or out of the mail server. I had too many characters in my SCANFILE line or something and it was trying to have the virus scanner /REPORT to d:\imail\spool\d8cebfc.vir\report.txt and of course F-Prot returned an error because it couldn't report to that directory. Instead of declude letting me know there was a problem, Imail just stopped functioning and I was not notified. If I had not went in to check something else on the server shortly after, I would not have caught Declude reporting errors with the virus scanner until one of our clients called in to report the problem. This has happened a few times before too .. Imail not delivering any mails because Declude was getting errors. I think there should be some sort of notification system to let the postmaster know that Declude and/or Imail is having problems, just so us postmasters catch the problem as soon as it starts happening.
 
One way I was thinking about going about this is to have TWO configuration files for declude, one of them the normal configuration and the other one, an emergency configuration file. In the event declude gets errors from the virus scanner and Imail is unable to send mail, declude switches to the emergency configuration file (which is just bare-bones stuff ... no special reporting options or anything) which should allow Imail to start functioning again (thus delivering all mail for all users) then it sends a mail to the postmaster reporting problems. I do not know the way in which Declude is written, this is just the only thought that came to mind right away when I thought of a way to get past this problem.
 
I also have a question about report.txt, what is directory that Declude looks for report.txt for? I did all that you said Scott but the file does not appear to be reading in at all. I checked the log file produced by F-Prot and the line that you said (Infection:) is correct.
 
Billy Kimble, Webmaster
ebase, LLC

Reply via email to