Mailscanner incoming directory..to many directories

[Julian Field]

That's the internal cvs version number of the file. MailScanner logs its
version number to your maillog when it starts.

What to so long to get it running to start with? I am interested if I can
try to ease the installation process.

At 17:54 26/01/2004, you wrote:
>Mailscanner is running on a Solaris 2.7 box. Version of Mailscanner is
>1.142.2.66.
>We are all afraid of upgrading at this time because of how long
>it took to get the program running correctly in the first place.
>-----Original Message-----
>From: Lindsay Snider [mailto:lindsay at pa.net]
>Sent: Monday, January 26, 2004 10:10 AM
>To: MailScanner mailing list; taz at aztek-eng.com
>Subject: Re: Mailscanner incoming directory..to many directories
>
>
>On Mon, 2004-01-26 at 11:49, Travis Zadikem wrote:
> > It appears that the mailscanner incoming directory
> > "/var/spool/MailScanner/incoming" on our server never removes the
> > directories that are created in what appears to be the pid numbers of
> > the running processes.  We now have about 700 directories and think
> > this is starting to get annoying.  Can someone please tell me how to
> > fix this and prevent it in the future.
>
>You could run:
>/usr/sbin/tmpwatch 1 /var/spool/MailScanner/incoming
>from cron.
>
> >   We had a similar problem with quarantine directory
> > but with another script calle quarantine cleaner was able to get a
> > handle on it.
>
>What version of MailScanner are you running?  I think I remember seeing
>this with an older version.  Perhaps upgrading would help.
>
> >
> > thanks.

--
Julian Field
www.MailScanner.info
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654