SpamAssassin 2.50 Problems

[Gerry Doris]

On Sun, 23 Feb 2003, Julian Field wrote:

> At 17:09 23/02/2003, you wrote:
> >Julian Field wrote:
> >>Another suggestion from the SAtalk list is to place this in your
> >>spam.assassin.prefs.conf
> >>
> >>score HABEAS_HIL 0
> >>
> >>as this is a new RBL they are using (I believe) and it seems to be timing
> >>out a lot.
> >
> >I tried this, but SA 2.50 keeps timing out, where 2.44 doesn't.
>
> What happens if you archive a bit of mail to a text file (not raw queue
> files), and then use "spamassassin -t < your-message-file" to see what happens?
> This is clearly very OS-dependent or location-dependent :-(
> --
> Julian Field

Using 2.50 and running "spamassassin -t < sample-spam.txt > spam" works
perfectly.  In fact, I've turned off MailScanner calling spamassassin
directly and started calling it via procmail.  That also works perfectly.

The 100% CPU utilization only occurs when I call spamassassin from within
MailScanner.  MailScanner sits there waiting and then eventually kills
off the spamassassin process.

It looks to me that the spamassassin 2.50 api is broken.  2.44 works
perfectly with no changes to MailScanner.

--
Gerry

"The lyfe so short, the craft so long to learne"  Chaucer