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.
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.
Michael Moncur wrote:
>>But it is mutually exclusive. If you use SQL, you can in no way shape or
>>form use AWL, it won't work. You can't use them both at the same time
>>with the current code, so thats mutually exclusive.
>>
>
> This isn't true. I just set up spamd to use SQL for preferences, and it still
> does auto-whitelisting.
>
> It doesn't do PER-USER autowhitelisting - instead I get a sitewide AWL stored
> at ~user/.spamassassin, where user is the user I run spamd under. But it does
> work in some way shape or form.
>
> It would be really nice if I could do per-user AWL with SQL - even if the
> whitelist isn't stored in the database. If it's just stored in path/username,
> where username is the user passed to spamc to look up preferences, that would
> be fine.
>
> I may try to get a true SQL-based whitelist working myself when I have some
> time.
>
> --
> michael moncur mgm at starlingtech.com http://www.starlingtech.com/
> "Nobody can be exactly like me. Even I have trouble doing it."
> -- Tallulah Bankhead
>
>
>
>>On 4 Apr 2002, Craig Hughes wrote:
>>
>>
>>>Not really mutually exclusive, just probably AWL won't behave the way
>>>you expect... It should be pretty easy to create a SQLBasedWhitelist.pm
>>>for people who want AWL to store stuff in the SQL db. I'm really pretty
>>>surprised noone's done it and contributed it back yet.
>>>
>>>C
>>>
>>>On Wed, 2002-04-03 at 21:32, Paul Rushing wrote:
>>>
>>>>no, auto-whitelist does not use the SQL database. (only uses the dbm
>>>>file in the user home directory)
>>>>
>>>>in the current spamd it appears that SQL and AWL are mutually exclusive,
>>>>although that's not in the documentation.
>>>>
>>>>Larry Rosenman wrote:
>>>>
>>>>
>>>>>If you are using SQL, does the auto-whitelist also make it into the SQL
>>>>>database?
>>>>>
>>>>>If you are using the DB version of AWL, is there any way to LIST the
>>>>>contents of the AWL for each user?
>>>>>
>>>>>Thanks,
>>>>>LER
>>>>>
>>>>>
>>>>
>>>>
>>>>_______________________________________________
>>>>Spamassassin-talk mailing list
>>>>[EMAIL PROTECTED]
>>>>https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
>>>>
>>>>
>>>>
>>>
>>>_______________________________________________
>>>Spamassassin-talk mailing list
>>>[EMAIL PROTECTED]
>>>https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
>>>
>>>
>>-----------------------------------------------
>>Brian Feeny, CCIE #8036 e: [EMAIL PROTECTED]
>>Network Engineer p: 318.222.2638x109
>>ShreveNet Inc. f: 318.221.6612
>>
>>
>>
>>_______________________________________________
>>Spamassassin-talk mailing list
>>[EMAIL PROTECTED]
>>https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
>>
>>
>>
>
>
> _______________________________________________
> Spamassassin-talk mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
>
--
=================================
Paul Rushing
[EMAIL PROTECTED]
=================================
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
