You can either set up an SQL database for user_prefs to hold both global and user-specific entries - that's how I'm doing it, or according to Theo:
"a quick workaround for this problem, btw, is running spamd with "--max-conn-per-child=1". it essentially reverts spamd to the 2.x way, and each child only processes 1 message before exiting." The doc for SQL user_prefs is here: http://spamassassin.apache.org/full/3.0.x/dist/sql/README In my case, I have no local users (~/ doesn't exist) and I was running MySQL for something else anyway... so it just made sense to put my settings in MySQL rather than using "--virtual-config-dir=". N8 -----Original Message----- From: Randy Gibson [mailto:[EMAIL PROTECTED] Sent: Monday, October 04, 2004 4:31 PM To: 'Marco van den Bovenkamp'; users@spamassassin.apache.org Subject: RE: Global Whitelist_from not working I really like ability to put global whitelist_from's in the local.cf for company wide whitelisting. And put user specific whitelist_from's in their ~/.spamassassin/user_prefs. This allows users to maintain they're personal white and black lists. This also keeps users out of the systems wide configuration file. ~Randy * Don't read everything you believe. -----Original Message----- From: Marco van den Bovenkamp [mailto:[EMAIL PROTECTED] Sent: Monday, October 04, 2004 11:00 AM To: users@spamassassin.apache.org Subject: Re: Global Whitelist_from not working Randy Gibson wrote: > I'm not using SQL so I don't have a place to put the @GLOBAL. Should I put > it in may local.cf? If you're using user_pref files, try putting them in there; if the problem is indeed 'whitelist entries are taken from the last place spamd looks for them' (as it seems to be), that might work. If you're not, run spamd with the '-x' option to disable scanning for user_prefs and only look in local.cf. The latter option worked for me. -- Groeten, Marco.
