Thanks for your feedback.
Amavisd runs spamassassin from a dedicated (non-root) login and the
user_prefs file is read for that user for all emails processed by amavisd.
This is what I believe, and I have seen results that support this belief.
But this is the area of my problems, so perhaps I am wrong.
I did already move the user_prefs to a .cf file, and I will monitor to see
if that makes a difference.
Thanks for the help!
--------------------
Timothy Burt
Los Angeles, Calif. USA
On Thu, 4 May 2006, Bowie Bailey wrote:
Timothy Burt wrote:
On Wed, 3 May 2006, Matt Kettler wrote:
2) Since your rules are declared in user_prefs, have you declared
allow_user_rules in your local.cf?
Curious that the answer to this is no. I saw this in the docs, after
I had the user_prefs confirmed as working.. I will try adding it
anyway.
There are quite a few things that will work in user_prefs without this
setting. You really only need it if you are defining rules there.
3) Why are you declaring rules in user_prefs anyway, instead of a
.cf file in /etc/mail/spamassassin?
Probably because there was an easy example for the user_prefs file,
and when I tried the example, it worked as advertised. Do you think
this would make a difference?
The main difference between user_prefs and a .cf file is that
user_prefs only applies to that one user while the .cf files are
global. You should try to avoid defining rules in user_prefs since it
can cause some extra overhead as SA has to parse those rules for every
message rather than just parsing all of the global rules on startup.
You can probably just move the user_prefs contents over to your
local.cf (or another .cf file).
Can you do per-user rules with Amavis? I thought it was limited to
global only?
--
Bowie
