Hi,

I think i've found it. i followed your suggestion to run spamassassin as the user it normally runs as (user defang), and when i run with --lint, defang can't find the executables anymore. they reside in /usr/local/bin, and that's not in defang's path.

Something has definitely changed here.

I made links for dccproc, razor-check and pyzor  to /usr/bin and reran --lint with user defang. seems to work fine.
then restarted mimedefang and sendmail, but no joy yet...

does this tale sound familiar to anyone ?

I compiled all these progs myself, usually with standard settings, except sometimes specifying it should run as user defang where appropriate.

tom.

---------------------------------------------------------------------------
Tom Van Overbeke - ABSI Unix System Engineer
email: [EMAIL PROTECTED]
Tel: +32 2 333 40 00 - Fax: +32 2 332 34 69
website: http://www.absi.be
---------------------------------------------------------------------------



"Menno van Bennekom" <[EMAIL PROTECTED]>

13/10/2005 15:29
Please respond to mvbengro

       
        To:        [EMAIL PROTECTED]
        cc:        users@spamassassin.apache.org
        Subject:        Re: spamassassin less effective after upgrade to 3.1.0: some                         checks no longer executed ?



Only difference with my 'spamassassin --lint -D' output I saw was that
after the line 'uridnsbl: domains to query' I have a block of 14 lines
with 'dns: checking RBL sbl-xbl.etcetera' that you don't have. Probably
not important. And I can't see your SARE-rules getting loaded, in my
output I see SARE being loaded after the line 'config: using "/<dir>" for
site rules dir'. The v310.pre and init.pre are the same as mine.

Maybe (like already suggested) the user that starts spamassassin could be
checked for having a user_prefs file, or for having permission troubles.
Also with 'cat mail | spamassassin -D' you should be able to see if that
specific mail is checked against DCC and Razor. Again, best to check that
is with the same user that executes spamassassin.
You could also sniff on ports tcp/2703 (razor) and udp/6277 (dcc).

Regards
Menno


Reply via email to