On Thu, 2002-04-04 at 19:46, Paul Rushing wrote:
> This message pertains to using AWL and SQL options.
> 
> if you will look at the spamd and Conf.pm code, you will see that 
> per-user AWL files are by default defined as ~/.spamassassin/auto-whitelist
> 
> This depends on the setuid code in spamd, so if you specify
>   '-u spamduser' option, you can get a sitewide AWL (assuming spamduser 
> has the proper permissions).  If you do not specify -u then you get the 
> default behavior which is to setuid to 'nobody', and on most systems 
> user nobody doesn't have write privileges anywhere.  Those are the only 
> 2 possibilities.

No they're not.  You can also override the default of
~/.spamassassin/auto-whitelist by setting the auto_whitelist_path in
your local.cf:

       auto_whitelist_path /path/to/file  (default: ~/.spamassas­
       sin/auto-whitelist)
           Automatic-whitelist directory or file.  By default,
           each user has their own, in their "~/.spamassassin"
           directory with mode 0700, but for system-wide SpamAs­
           sassin use, you may want to share this across all
           users.


> What's interesting is this comment in the spamd code:
>     # We'll run handle user unless we've been told not
>     # to process per-user config files.  Otherwise
>     # we'll check and see if we need to try SQL
>     # lookups.  If $opt_x is NOT true, we need to try
>     # their config file and then do the SQL lookup.
>     # If $opt_x IS true, we skip the conf file and
>     # only need to do the SQL lookup if $opt_q IS
>     # true.  (I got that wrong the first time.)
> 
> This comment does not reflect the actual behavior of the spamd code. 
> Which is: If $opt_x is NOT true we load user config files.  If $opt_x is 
> true and $opt_q is true we load SQL.
> 
> What's left out is any method to have user config files and SQL configs. 
>   Which the comment in the code indicates should work.
> 
> 
> 
> 
> ---quick hack----
> 
> You can get per-user AWL working by merging the code in handle_user and 
> handle_user_sql so that handle_user_sql sets the uid like handle_user does.

Can someone just send me a patch?

Thanks,

C

_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to