You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@spamassassin.apache.org by sp...@incubator.apache.org on 2004/04/26 14:31:42 UTC

[SpamAssassin Wiki] Updated: WhereDoLocalSettingsGo

   Date: 2004-04-26T05:31:42
   Editor: 24.156.198.143 <>
   Wiki: SpamAssassin Wiki
   Page: WhereDoLocalSettingsGo
   URL: http://wiki.apache.org/spamassassin/WhereDoLocalSettingsGo

   Can't put *.cf files in users configuration directoryry

Change Log:

------------------------------------------------------------------------------
@@ -7,3 +7,11 @@
 If you are an "end user" and do not have update access to /etc/mail/spamassassin, then your configuration parameters should go into your $HOME/.spamassassin/user_prefs file. Assuming your mail host's configuration allows for individual configurations, this file is read and then merged with (and supersedes) site-specific and distribution parameters. (If your host's configuration does not allow for individual configurations, then chances are you do not have a $HOME/.spamassassin directory.) 
 
 -----
+
+Question:  To clarify the above ...
+
+If you put the *.cf files in /etc/mail/spamassassin theu are applied to all users on the system
+
+If you want to make the rules specific to one user, its different ('''read inconsistent''').  Putting the *.cf files in the user's $HOME/.spamassassin/ directory won't work, they actually have to be in the $HOME/.spamassassin/user_prefs file.
+
+This seems clunky and inconsistent to me.  Could you please confim.