<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>Ability to create raw sieve rules</title>
  <pubDate>Fri, 25 Jul 2008 07:13:20 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/6375</link>
  <atom:link rel="self" type="application/rss+xml" title="Ability to create raw sieve rules" href="http://bugs.horde.org/ticket/6375/rss" />
  <description>Ability to create raw sieve rules</description>

  
  
  <item>
   <title>It would be great to have the option of creating a ingo rule</title>
   <description>It would be great to have the option of creating a ingo rule that just accepts raw sieve syntax.
Otherwise, there is no possibility to switch current manual sieve rules to Ingo.

Furthermore it would allow complex rules that include both AND and OR conditions.</description>
   <pubDate>Wed, 05 Mar 2008 05:54:05 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/6375#t43395</link>
  </item>
  <item>
   <title>The goal of Ingo is user-friendly filter frontend that abstr</title>
   <description>The goal of Ingo is user-friendly filter frontend that abstracts from the filter scripting language. Users that can can write raw Sieve rules can upload them on the server too.</description>
   <pubDate>Wed, 05 Mar 2008 19:45:50 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/6375#t43447</link>
  </item>
  <item>
   <title>I could see some arguments for scripting defaults for people</title>
   <description>I could see some arguments for scripting defaults for people, or for allowing advanced users to access a sieve server that is otherwise locked down (and only accessible via ingo).</description>
   <pubDate>Wed, 05 Mar 2008 22:50:36 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/6375#t43457</link>
  </item>
  <item>
   <title>Currently, we're using raw sieve scripts that we can't conve</title>
   <description>Currently, we're using raw sieve scripts that we can't convert to Ingo because some rules have AND and OR conditions mixed. However we'd love to migrate smoothly to Ingo using the old rules as a raw script.</description>
   <pubDate>Tue, 11 Mar 2008 15:23:51 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6375#t43721</link>
  </item>
  <item>
   <title>&gt; Currently, we're using raw sieve scripts that we can't con</title>
   <description>&gt; Currently, we're using raw sieve scripts that we can't convert to 
&gt; Ingo because some rules have AND and OR conditions mixed. However 
&gt; we'd love to migrate smoothly to Ingo using the old rules as a raw 
&gt; script.

Adding AND/OR conditions sounds like a desirable enhancement and maybe not too hard since we already have AND and OR rule types.  What sort of rules do you have like with AND/OR?</description>
   <pubDate>Tue, 11 Mar 2008 16:14:03 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6375#t43723</link>
  </item>
  <item>
   <title>We have simple AND+OR rules like

if allof ( header :conta</title>
   <description>We have simple AND+OR rules like

if allof ( header :contains &quot;Delivered-To&quot; [&quot;a@b.com&quot;,&quot;b@c.com&quot;], anyof(header :contains [&quot;Subject&quot;] &quot;abc&quot;, header :contains [&quot;From&quot;] &quot;x@y.z&quot;)) {...}

or rules with sub-rules like

if header :contains [&quot;to&quot;,&quot;cc&quot;,&quot;resent-to&quot;] &quot;c@d.com&quot; {
        if header :contains [&quot;subject&quot;] &quot;abc&quot; {
                fileinto &quot;...&quot;;
                stop;
        }
        if header :contains [&quot;subject&quot;] [&quot;def&quot;,&quot;ghi&quot;] {
                fileinto &quot;...&quot;;
                stop;
        }
       if ...
}</description>
   <pubDate>Thu, 20 Mar 2008 06:17:49 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6375#t44035</link>
  </item>
  

 </channel>
</rss>
