[Tickets #7611] Re: maildrop destination rules

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7611
------------------------------------------------------------------------------
  Ticket             | 7611
  Updated By         | horde at nospam.obeliks.de
  Summary            | maildrop destination rules
  Queue              | Ingo
  Version            | HEAD
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Chuck Hagenbuch
------------------------------------------------------------------------------


horde at nospam.obeliks.de (2009-05-24 20:53) wrote:

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: "(?:" instead of "("

Since the maildrop driver requires maildrop >= 2.0 anyway, we can use  
this PCRE feature. I just confirmed this on maildrop 2.0.4