So yes, I understand how the AWL smears your all_spam_to scores all over the place and causes problems. I understand this and the mechanisms behind it QUITE well.
The point is that how does using user_prefs help?
If you invoke SA as root for your first pass, the default user_prefs is /root/.spamassassin/user_prefs and the AWL database is /root/.spamasassin/auto_whitelist.db.
If you invoke SA as a different user for the Cyrus mailbox bit, say for example the user "boss", the user_prefs is going to be /home/boss/.spamassassin/user_prefs and the AWL database is /home/boss/.spamassassin/auto_whitelist.db.
Note that once you have separate user_prefs files, you ALREADY have separate auto_whitelist.db files. No changes to user_prefs needed.
If on the second pass you invoke it as root, instead of boss, both the AWL database and user_prefs files are the same as for the first pass. Changing the user_prefs doesn't help, since it will affect both batches of processing.
So, my question still remains, how does over-riding this setting in user_prefs help you?
At 08:03 AM 11/19/2002 +0100, Jan Schreckenbach wrote:
Matt, did you ever deploy SA system-wide and have all_spam_to for some user set? In the case where you scan a mail once before any delivering, SPAM comes through if only one receiver is in all_spam_to and the spammers address goes into your central AWL file with a very low score. The next SPAM from that spammer goes through even if no receiver is in all_spam_to 'cause of the low score in the AWL. In my case I want to scan mail once and later I need to clean/rescan for the very few users that have it own settings. For the majority of users SPAM goes to a special SPAM folder that will be monitored by one person. For the boss I rescan mails with whitelist*/blacklist* settings and put the mail into his Cyrus mailbox (where sieve sort SPAM out to a subfolder). The reason is that any FP for the boss must not go tho the central SPAM folder. Because he lowers scores I dont want to have these scores in my AWL.cu, Jan Matt Kettler wrote:Ok, I don't know the answer to your question, but I'm wondering why you're even asking it.Note: Emails authored under this address do not reflect the opinions of my employer unless otherwise stated. Facts contained are also prone to human error. If either of these statements are not humanly obvious to you, I suggest careful thought before leaping to any other conclusions.
By default if you have different user_prefs files, then you don't have a global AWL database.
The global AWL case only happens if SA is always run as one user, such as root when run from a milter. In which case it always uses the same awl database, but it also always uses the same user_prefs file. (note that user_prefs is not per user addressed in the email, it's per user invoking SA)
If SA is invoked as different users, the AWL database should be ~/.spamassassin/autowhitelist.db. This places a different database in the home directory of each user running SA.
So to customize it in the user_prefs shouldn't even be necessary by default, but I don't see why it would prevent you from doing so.
At 11:53 AM 11/17/2002 +0100, you wrote:
Hi,Note: Emails authored under this address do not reflect the opinions of my employer unless otherwise stated. Facts contained are also prone to human error. If either of these statements are not humanly obvious to you, I suggest careful thought before leaping to any other conclusions.
what is the reason for auto_whitelist_path being privileged? I want to
overwrite the setting from the global local.cf file in the user_prefs
file. Otherwise whitelist_to will lower scores for SPAM and this will
"poison" my global AWL.
cu,
Jan
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk