<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Ingo expert mode</title> 
  <pubDate>Fri, 10 Apr 2026 19:46:49 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/8994</link> 
  <atom:link rel="self" type="application/rss+xml" title="Ingo expert mode" href="https://bugs.horde.org/ticket/8994/rss" /> 
  <description>Ingo expert mode</description> 
 
   
   
  <item> 
   <title>It would be very nice to have an expert mode for script gene</title> 
   <description>It would be very nice to have an expert mode for script generation.
Idea: Option to switch to expert mode for editing the script (procmail) by hand.
Also the ability to look at the procmail log for debugging.</description> 
   <pubDate>Wed, 28 Apr 2010 15:12:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8994#t58658</link> 
  </item> 
   
  <item> 
   <title>&gt; It would be very nice to have an expert mode for script ge</title> 
   <description>&gt; It would be very nice to have an expert mode for script generation.
&gt; Idea: Option to switch to expert mode for editing the script 
&gt; (procmail) by hand.
&gt; Also the ability to look at the procmail log for debugging.

I have the same &quot;problem&quot; with sieve.
I&#039;d like to add custom rules that Ingo doesn&#039;t support (rule inclusion, labels, colors, etc.,), but if I do it externally, then Ingo will erase everything the next time I edit some rules using it.

So, script editing would be great if Ingo can leave custom changes alone.
</description> 
   <pubDate>Thu, 29 Apr 2010 16:35:23 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8994#t58666</link> 
  </item> 
   
  <item> 
   <title>Duplicate of request #6375.</title> 
   <description>Duplicate of request #6375.</description> 
   <pubDate>Thu, 29 Apr 2010 16:44:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8994#t58667</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
