Matt Kettler writes:
> At 04:31 PM 9/30/2004, Arun Bhalla wrote:
> > > >Hi, about a week ago I upgraded to SA 3.0.0 from 2.64.  I run spamd (wit
> h
> > > >options "-d -c"), and call spamc from my .procmailrc.  SA is installed
> > > >systemwide (e.g., local.cf is in /etc/mail/spamassassin), but I
> > > >also have my own user_prefs file that I tweak.
> > >
> > >
> > > Is allow_user_rules set in local.cf? If not, spamd is required to ignore
> > > your rules in user_prefs, and it's a bug that they are being parsed at al
> l.
> >
> >Good question!  I should have mentioned that, but yes, it is.
> >
> >allow_user_rules        1
> >
> >So it's not that.
> 
> Ok, next shot.. any complaints issued when you run spamassassin --lint?

Not now, but there were some warnings a little earlier today that I fixed.
Looks like it was just 2.6->3.0 warnings, and I commented all of the lines
out.  I wouldn't expect that they would cause any trouble.

% spamassassin --lint
config: SpamAssassin failed to parse line, skipping: rewrite_subject           0
config: SpamAssassin failed to parse line, skipping: use_terse_report   1
warning: score set for non-existent rule X_OSIRU_DUL_FH
warning: score set for non-existent rule X_OSIRU_DUL
warning: score set for non-existent rule X_OSIRU_SPAMWARE_SITE
warning: score set for non-existent rule X_OSIRU_SPAM_SRC
warning: score set for non-existent rule RCVD_IN_OSIRUSOFT_COM
warning: score set for non-existent rule X_OSIRU_OPEN_RELAY
lint: 8 issues detected.  please rerun with debug enabled for more information.

Arun

Reply via email to