<?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>maildrop destination rules</title> 
  <pubDate>Fri, 10 Apr 2026 14:37:19 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7611</link> 
  <atom:link rel="self" type="application/rss+xml" title="maildrop destination rules" href="https://bugs.horde.org/ticket/7611/rss" /> 
  <description>maildrop destination rules</description> 
 
   
   
  <item> 
   <title>destination rules like &#039;To,Cc,Bcc,Resent-to&#039;, &#039;To,Cc,&#039; don&#039;t</title> 
   <description>destination rules like &#039;To,Cc,Bcc,Resent-to&#039;, &#039;To,Cc,&#039; don&#039;t work

the attached path should fix this.



the same fix should work for procmail : ticket #7117

</description> 
   <pubDate>Thu, 30 Oct 2008 12:10:44 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7611#t50182</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

http://cvs.h</title> 
   <description>Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/ingo/docs/CHANGES?r1=1.206&amp;r2=1.207&amp;ty=u
http://cvs.horde.org/diff.php/ingo/lib/Script/maildrop.php?r1=1.23&amp;r2=1.24&amp;ty=u
http://cvs.horde.org/diff.php/ingo/lib/Script/procmail.php?r1=1.99&amp;r2=1.100&amp;ty=u</description> 
   <pubDate>Fri, 07 Nov 2008 06:28:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7611#t50438</link> 
  </item> 
   
  <item> 
   <title>Committed, thanks!</title> 
   <description>Committed, thanks!</description> 
   <pubDate>Fri, 07 Nov 2008 06:28:29 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7611#t50439</link> 
  </item> 
   
  <item> 
   <title>While this is a highly unlikely case, this change breaks num</title> 
   <description>While this is a highly unlikely case, this change breaks numerical comparisons for any multi-field conditions. Since numerical comparisons use a numbered subgroup to get the number into a maildrop variable, adding another (capturing) group for the header fields shifts the number to 2 (i.e. $MATCH2 instead of $MATCH1) and thus breaks the comparison (because the value would be compared to the field name instead of the value).



This is easily fixed by using a non-capturing group for the header fields: &quot;(?:&quot; instead of &quot;(&quot;



Since the maildrop driver requires maildrop &gt;= 2.0 anyway, we can use this PCRE feature. I just confirmed this on maildrop 2.0.4</description> 
   <pubDate>Mon, 25 May 2009 00:53:10 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7611#t54292</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
