SA3.0.1 via MailScanner

[Ade Fewings <ad...@informatics.bangor.ac.uk>]

Dear all

Forgive me straight away if any of this has been answered before or is 
stupid on my part.  Going through a bit of a baptism-of-fire at the 
moment with regard to mail servers.

We have two mail servers running on Solaris 9 Sparc.  Sendmail 8.12.10 
utilizing MailScanner to call SpamAssassin 3.0.1.  Earlier today, one of 
our large mailing lists got hit a couple of times and the servers got a 
bit busy.  However, something went wrong and /tmp filled up with 
spamassassin.25755.Bdgxlb.tmp esque files.  Hundred of thousands were 
created in a short time.  Stopping MailScanner, cleaning /tmp and 
restarting would then reproduce the problem again soon after.  I truss'd 
the output of a few of the MailScanner processes that were going bad and 
all they were doing was trying to open new files in /tmp. 

Before my time, SA 2.6 was running and never provided any problems.  Has 
anybody got any ideas?  Are we thinking MailScanner or SA bugs 
possibly?  We certainly are intending to get to SA 3.0.2, but there was 
some problem on out first attempt yesterday so we 're stuck on 3.0.1 for 
a bit.

Regards and Thanks
Ade

Re: SA3.0.1 via MailScanner

[Martin Hepworth <ma...@solid-state-logic.com>]

Ade

might want to ask on the MS list.

There have been some issues with the Perl Mime tools recently so this 
*may* be the issue.

you don't mention which version of MS you are using

--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300


Ade Fewings wrote:
> Dear all
> 
> Forgive me straight away if any of this has been answered before or is 
> stupid on my part.  Going through a bit of a baptism-of-fire at the 
> moment with regard to mail servers.
> 
> We have two mail servers running on Solaris 9 Sparc.  Sendmail 8.12.10 
> utilizing MailScanner to call SpamAssassin 3.0.1.  Earlier today, one of 
> our large mailing lists got hit a couple of times and the servers got a 
> bit busy.  However, something went wrong and /tmp filled up with 
> spamassassin.25755.Bdgxlb.tmp esque files.  Hundred of thousands were 
> created in a short time.  Stopping MailScanner, cleaning /tmp and 
> restarting would then reproduce the problem again soon after.  I truss'd 
> the output of a few of the MailScanner processes that were going bad and 
> all they were doing was trying to open new files in /tmp.
> Before my time, SA 2.6 was running and never provided any problems.  Has 
> anybody got any ideas?  Are we thinking MailScanner or SA bugs 
> possibly?  We certainly are intending to get to SA 3.0.2, but there was 
> some problem on out first attempt yesterday so we 're stuck on 3.0.1 for 
> a bit.
> 
> Regards and Thanks
> Ade

**********************************************************************

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote confirms that this email message has been swept
for the presence of computer viruses and is believed to be clean.

**********************************************************************