Amavisd-New ignores a lot of the options in local.cf and ignores all of the user_prefs files except for its own.
See: http://www.ijs.si/software/amavisd/#faq-spam I wanted the same control, so I separated spamassassin from amavisd-new completely and only use it for virus scanning. I then use procmail delivery for SA to implement this functionality. --JM Prentice Bisbal said: > I'm using spamassassin from amavisd-new. Some of my users would like to > user their own user_prefs file. I created my own user_prefs file > ~/.spamassassin/user_prefs, but SA seems to be ignoring it. Is there > anything special I need to do to get SA to look at user_prefs when > called from amavisd-new? > > I added "allow_user_rules 1" to my /etc/mail/spamassassin/local.cf: > > more /etc/mail/spamassassin/local.cf > # These values can be overridden by editing ~/.spamassassin/user_prefs.cf > # (see spamassassin(1) for details) > > # These should be safe assumptions and allow for simple visual sifting > # without risking lost emails. > > required_hits 5 > rewrite_subject 1 > subject_tag [SPAM] > report_safe 0 > allow_user_rules 1 > > my user_prefs file: > > ls -l .spamassassin/user_prefs > -rw------- 1 prentice staff 78 Mar 30 15:03 > .spamassassin/user_prefs > > more .spamassassin/user_prefs > # How many hits before a mail is considered spam. > required_hits 3.8 > > The comments in the file /etc/mail/spamassassin/local.cf indicate that > the user prefs file should be named ~/.spamassassin/user_prefs.cf, but > the manpage refers to it as user_prefs. Which is it? I copied user_prefs > to user_prefs.cf, so both files exist, but it's still not using them. > > Prentice > > > > > > > > > >
