user_prefs file

[Julian Field]

<x-flowed>
Yes, I see the problem now.
I have added this to the comment above the setting:
# NOTE: SpamAssassin is always called from MailScanner as the same user,
#       and that is the "Run As" user specified above. So you can only
#       have 1 set of "per-user" files, it's just that you might possibly
#       need to modify this location.
#       You should not normally need to set this at all.

At 18:21 29/09/2004, you wrote:
># The per-user files (bayes, auto-whitelist, user_prefs) are looked
># for here and in ~/.spamassassin/. Note the files are mutable.
># If this is unset then no extra places are searched for.
># If using Postfix, you probably want to set this as shown in the example
># line at the end of this comment, and do
>#      mkdir /var/spool/MailScanner/spamassassin
>#      chown postfix.postfix /var/spool/MailScanner/spamassassin
>#SpamAssassin User State Dir = /var/spool/MailScanner/spamassassin
>
>When I first read this, I thought that MailScanner would look for the
>user_prefs or whitelist files in my home directory and in another specified
>directory (wasn't really sure how this would be implemented but didn't need
>it anyhow). I don't know, the combination of "per-user" and
>"~/.spamassassin/" made me think I could set up per-user rules easily by
>putting user_prefs files in the users home directories. All I'm saying, is
>that before I posted I searched archives for user_prefs (which returned no
>relevant posts) and searched google a bit and it seemed like I had a simple
>config problem - not that it wasn't possible.
>
>Here's another post from someone who read it the same way:
>
>http://www.experts-exchange.com/Operating_Systems/Linux/Q_20904277.html
>
>At any rate, I don't really even need this functionality...I had just wanted
>to test what increasing the scores for a few rules would do to suspected
>spam on my email before I implemented it site-wide.
>
>-----Original Message-----
>Exactly which comments and what wording would you prefer?
>
>At 22:03 28/09/2004, you wrote:
> >You should modify the config file comments as it is misleading. I read a
> >bunch of posts from other sites with admins who misinterpeted the
> >comments as well.
> >
> >-----Original Message-----
> >
> >This has been mentioned many times here. MailScanner always calls
> >SpamAssassin as the same user. The real username to use would only be
> >known
> >at delivery time, which is long after MailScanner has got out of the
> >way. I
> >don't interfere with the delivery process at all as it is far too
> >complicated for most users to be able to setup without lots of help :-)
> >
> >The things that people usually want to configure per-user are
> >configurable
> >via MailScanner instead. This includes the score thresholds and actions,
> >and the white and black lists. And if you want to read these from an
> >SQL,
> >LDAP or other storage system, you can do all of that with simple Custom
> >Functions.

--
Julian Field
www.MailScanner.info
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support
Buy the MailScanner book at www.MailScanner.info/store

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).
</x-flowed>