Keith Hackworth wrote:
I have the same configuration and I had the same problem with 2.64. I did
a spamassassin --lint and it showed me all sorts of problems in my
local.cf. It was so bad, it just ignored anything beyond x lines in the
file.
spamassassin --lint created a "sample" user_prefs file
Sahil Tandon wrote:
>
snowjack wrote:
Is there any evidence that local.cf is getting read at all?
Good question. Where do I look for such evidence? Logs are hardly
revealing.
If you first log in, or su to be the user amavis is running as, then run
"spamassassin -D --lint" you should see somethi
Quoting Keith Hackworth <[EMAIL PROTECTED]>:
> I have the same configuration and I had the same problem with 2.64. I did
> a spamassassin --lint and it showed me all sorts of problems in my
> local.cf. It was so bad, it just ignored anything beyond x lines in the
> file.
Very plausible - I'll t
Quoting Volker Kindermann <[EMAIL PROTECTED]>:
> if you are running postfix,amavisd-new and spamassassin chrooted be sure to
> not only change /etc/mail/spamassassin/local.cf but also
> /etc/mail/spamassassin/local.cf
I'm not running within a chroot; the cf is in /usr/local/etc/mail/spamassassin.
I have the same configuration and I had the same problem with 2.64. I did
a spamassassin --lint and it showed me all sorts of problems in my
local.cf. It was so bad, it just ignored anything beyond x lines in the
file.
I'm not sure why, but my install of sa was VERY picky about spacing in the
fi
> > Is there any evidence that local.cf is getting read at all?
>
> Good question. Where do I look for such evidence? Logs are hardly
> revealing.
if you are running postfix,amavisd-new and spamassassin chrooted be sure to not
only change /etc/mail/spamassassin/local.cf but also
/etc/mail/sp
snowjack wrote:
Is there any evidence that local.cf is getting read at all?
Good question. Where do I look for such evidence? Logs are hardly
revealing.
--
Sahil Tandon
[EMAIL PROTECTED] wrote:
Quoting snowjack <[EMAIL PROTECTED]>:
...Did you restart amavisd-new after making the change?
Yes. :-)
Is there any evidence that local.cf is getting read at all?
Quoting snowjack <[EMAIL PROTECTED]>:
> ...Did you restart amavisd-new after making the change?
Yes. :-)
--
Sahil Tandon
[EMAIL PROTECTED] wrote on 10/07/2004 03:35:07 PM:
> I am running Postfix 2.1 with a content_filter (latest amavisd-new) which
sends
> all mail through SA 2.64. I understand *some* variables that are defined
> explicitly in amavisd-new are "special", and thus have no effect when
defined
> (di
[EMAIL PROTECTED] wrote:
I am running Postfix 2.1 with a content_filter (latest amavisd-new) which sends
all mail through SA 2.64. I understand *some* variables that are defined
explicitly in amavisd-new are "special", and thus have no effect when defined
(differently) in local.cf. AFAIK, scores
I am running Postfix 2.1 with a content_filter (latest amavisd-new) which sends
all mail through SA 2.64. I understand *some* variables that are defined
explicitly in amavisd-new are "special", and thus have no effect when defined
(differently) in local.cf. AFAIK, scores are not included in this
12 matches
Mail list logo
