[cvs] [Wiki] changed: DefaultFilterRules

Wiki Guest wikiguest at horde.org
Fri Sep 18 16:16:16 UTC 2009


guest [95.222.139.51]  Fri, 18 Sep 2009 12:16:16 -0400

Modified page: http://wiki.horde.org/DefaultFilterRules
New Revision:  1.4
Change log:  missed a '{' and language

@@ -28,13 +28,13 @@
  I think this is self explaining. The **$_prefs['rules']** defines  
that there is a rule and **$_prefs['spam']** configures this rule  
(with spamlevel 6, move to folder spam). I just like to take a look on  
the **value** elements.  
[http://lists.horde.org/archives/ingo/Week-of-Mon-20051031/000954.html  
Kevin M. Myer] has explained how to get the content of this array  
elements.
  # create a fresh user account in you horde installation
  # log on using this account and create the rules that you want to  
have as you default fules and save them
  # go to you horde preferences backend (or what ever backend you use  
to save you rules) and find the info preferences that match this user;  
for me this were the {{pref_name}} //spam// and //rules// of the  
{{pref_scope}} //ingo//
-# copy the content of {pref_value}} into you value elements of the  
spam and rules array in ingo/config/prefs.php
+# copy the content of {{pref_value}} into you value elements of the  
spam and rules array in ingo/config/prefs.php

  To test this I deleted all user data ( Horde -> Administration ->  
Users ) of this testuser and logged on again. I now saw the fules that  
I just defined in the prefs.php file.

-So we have made the hardest part. This rules inside ingo are only  
used by sieve if ingo does actually create a script. Until then the  
global sieve file is used. To have exactly the same behaviour, I  
copied the sieve script that ingo creates from my default rules into  
the global sieve rule file
+So we have made the hardest part. This rules inside ingo are only  
used by sieve if ingo does actually create a script. Until then the  
global sieve file is used. To have exactly the same behaviour, I  
copied the sieve script that ingo created into the global sieve rule  
file
  <code type="sieve">
  require "fileinto";
  # Spamfilter
  if header :comparator "i;ascii-casemap" :contains "X-Spam-Level" "******"  {



More information about the cvs mailing list