Spamassassin woes

Scott Silva ssilva at SGVWATER.COM
Thu Oct 6 20:35:32 IST 2005

    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Scott Silva spake the following on 10/6/2005 11:11 AM:
> Julian Field spake the following on 10/6/2005 10:37 AM:
>>Scott Silva wrote:
>>>Scott Silva spake the following on 10/6/2005 9:41 AM:
>>>>>After an extended session in CPAN, things seem OK. I still don't know
>>>>>which module was tanked, but it's fixed!
>>>>>Thank you to all!
>>>>>And greeting from California, USA.
>>>>>Where any actor can aspire to Governor!
>>>>Spoke too soon!
>>>>Although lint tests all work, MailScanner isn't adding the URIBL scores
>>>>into messages.
>>>>If I take the same message and run it through lint, it shows up.
>>>>I guess I'm going to reinstall MailScanner now.
>>>>I think I will diff the config files for the two machines again first,
>>>>just to make sure.
>>>Running MailScanner in debug mode gets entries like this;
>>>rules: failed to run URIBL_BLACK test, skipping:
>>>       (Can't locate object method "check_uridnsbl" via package
>>>"Mail::SpamAssassin::PerMsgStatus" at
>>>/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/ line
>>>But if I pipe the same message into a lint, it works fine.
>>You don't have 2 Perl installations do you?
>>You will need to have added
>>loadplugin Mail::SpamAssassin::Plugin::URIDNSBL
>>to your init.pre file in /etc/mail/spamassassin, or else the SURBL stuff
>>won't work at all.
> One perl, and I have the line to load the plugin.
> Can't figure out why I can lint a message as root, and get different
> results than MailScanner running as root.
> That should eliminate any path or permission problems.
I have found the problem.
For some reason, the local rules directory is getting ignored and either
MailScanner or spamassassin is looking in /usr/etc/mail/spamassassin
instead of /etc/mail/spamassassin
The working system had that directory, and the non working system didn't.
Making a symlink seems to have cured the non-working system, but now I
need to find out why this happened.
All my config files have the proper paths in them, so I do not know
where this /usr/etc/mail/spamassassin came from.


/-----------------------\           |~~\_____/~~\__  |
| MailScanner; The best |___________ \N1____====== )-+
| protection on the net!|                   ~~~|/~~  |
\-----------------------/                      ()

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at with the words:
'leave mailscanner' in the body of the email.
Before posting, read the Wiki ( and
the archives (

Support MailScanner development - buy the book off the website!

More information about the MailScanner mailing list