SpamAssassin 3.2.5 woes

[Julian Field]

Steffan Henke wrote:
> On Tue, 1 Jul 2008, Julian Field wrote:
>
>
>> Can we start collecting evidence to try to discern some commonality 
>> between these systems where it's not working please?
>
> Julian
>
> the only spamassassin part that shows up as modified is:
>
> rpm -qV spamassassin
> S.5....T  c /etc/rc.d/init.d/spamassassin - I usually modify the 
> startup script to use a TMPDIR on /dev/shm.
Just mount /tmp using tmpfs, you don't need to mess with /dev/shm, 
that's only really there as an example, as far as I'm concerned.

Check that whatever user you are running MailScanner as, can actually 
read all the SpamAssasssin rules. Dodgy permissions somewhere near the 
top of the /var/lib/spamasssassin(?) tree would break it fairly well.
>
> Apart from that, I even ran a diff over /usr/lib/MailScanner between 
> the two systems:
> diff -qr /usr/lib/MailScanner /backups/MailScanner
> Files /usr/lib/MailScanner/MailScanner/CustomFunctions/MailWatch.pm 
> and /backups/MailScanner/MailScanner/CustomFunctions/MailWatch.pm differ
>
> - nothing else...
>
> Regards,
>
> Steffan
>

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.