4.10-1: Cannot create + lock headers file ...

[Julian Field]

At 14:01 05/12/2002, you wrote:
>Julian
>
>Running MailScanner 4.10-1 on a RedHat 7.2 system with Sendmail.
>
>It is built from the Unix (non-RPM) tar ball in the same way we have
>done for all the previos versions.
>
>Whenever I do a "/etc/init.d/MailScanner restart" I get a message of the
>form:
>
>"Cannot create + lock headers file
>/var/spool/MailScanner/incoming/28837/gB5123456123.header, at
>/opt/MailScanner/bin/MailScanner/Message.pm line 237".

Did the restart shut down the old version of MailScanner before starting
the new one? With the new "PID File" instead of "PID Dir" it is much easier
to kill MailScanner as you have just 1 pid to kill which will take out the
whole lot, particularly if you do
         /bin/kill -- -12345
where 12345 is the PID you are trying to kill. That will kill the whole
process group at once.

>However I was a little bit surprised that the "Archive Mail" option
>requires that the sub-directories of /var/spool/MailScanner/archive that
>are specified in the ruleset must already be created rather than being
>created the first time a message has to be stored under it. You create
>the date sub-dircetory under that on the fly so why not the parent
>dircetory?

I didn't want to create all the subdirectories in case you typo-ed the
directory in the conf file.

>Related to this option is that I note that "archived" messages are
>stored in separate "df" and "qf" files, presumably because I have
>"Quarantine Whole Messages As Queue Files = no" (the default). I would
>want that behaviour if I was quarantining messages but I want the qf &
>df file combined into one when I am "archiving".

The "archiving" and "quarantining" both use the same code. I'll work on
adding that for the next release, shouldn't be too hard to do.
--
Julian Field
www.MailScanner.info
MailScanner thanks transtec Computers for their support