Mailman on Red Hat 7.3

Tom.Minchin at Tom.Minchin at
Tue Jun 25 14:08:48 EST 2002

SPEWS is a bit of an unknown though. Some of the subnets they include are designed to cause collateral damage rather than block spam. It used to be a good list to use, but it's heading the same way as ORBS (ie operator insanity).

-----Original Message-----
From: Alex Satrapa [mailto:grail at]
Sent: Tuesday, 25 June 2002 1:50 PM
To: Andrew Pollock
Cc: linux at
Subject: Re: Mailman on Red Hat 7.3

On Tuesday, June 25, 2002, at 11:56 , Andrew Pollock wrote a message 
which was flagged by SpamAssassin:

> SPAM: -------------------- Start SpamAssassin 
> results ----------------------
> SPAM: This mail is probably spam.  The original message has been altered
> SPAM: so you can recognise or block similar unwanted mail in future.
> SPAM: See for more details.
> SPAM: Content analysis details:   (5 hits, 5 required)
> SPAM: Hit! (2.0 points)  Received via a relay in
> SPAM:                    [RBL check: found 
>, type:]
> SPAM: Hit! (3.0 points)  DNSBL: sender is Confirmed Spam Source
> SPAM: -------------------- End of SpamAssassin 
> results ---------------------

I think that's referring to
Received: from (root at 
[]) by

You won't get responses to people who have spam filters in place.  
Consider changing ISPs, or if that network is actually yours,

> It was because /var/log was owned by root:bin and was mode 0700 so the 
> average
> process couldn't get to /var/log to get to /var/log/mailman
> Just wondering if he had an unusual permission set or if the package 
> for Red Hat
> 7.3 is broken in terms of permissions or setuid users or something.

Seems like odd permissions to me.  Someone's tried being too tight with 
permissions - I'd suggest making the directory at least readable and 
executable by the group (make the group "loggers"), and add mailman to 
that group.

More information about the linux mailing list