| Summary | maildrop destination rules |
| Queue | Ingo |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | chuck (at) horde (dot) org |
| Requester | rsalmon (at) mbpgroup (dot) com |
| Created | 10/30/2008 (6102 days ago) |
| Due | |
| Updated | 05/25/2009 (5895 days ago) |
| Assigned | |
| Resolved | 11/07/2008 (6094 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | Yes |
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
Assigned to Chuck Hagenbuch
State ⇒ Resolved
http://cvs.horde.org/diff.php/ingo/docs/CHANGES?r1=1.206&r2=1.207&ty=u
http://cvs.horde.org/diff.php/ingo/lib/Script/maildrop.php?r1=1.23&r2=1.24&ty=u
http://cvs.horde.org/diff.php/ingo/lib/Script/procmail.php?r1=1.99&r2=1.100&ty=u
Priority ⇒ 1. Low
New Attachment: maildrop2.patch
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ maildrop destination rules
Type ⇒ Bug
State ⇒ Unconfirmed
the attached path should fix this.
the same fix should work for procmail :
ticket #7117