[#1904] regex bug in sieve driver
Summary regex bug in sieve driver
Queue Ingo
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners Michael Slusarz <slusarz (at) horde (dot) org>
Requester vilius (at) lnk (dot) lt
Created 05/03/2005 (1344 days ago)
Due
Updated 05/25/2005 (1322 days ago)
Assigned 05/25/2005 (1322 days ago)
Resolved 05/25/2005 (1322 days ago)
Attachments
Milestone
Patch No

History
05/25/2005 Jan Schneider State ⇒ Resolved
 
05/25/2005 Chuck Hagenbuch Assigned to Michael Slusarz
State ⇒ Assigned
Taken from Horde DevelopersHorde Developers
 
05/03/2005 Chuck Hagenbuch Assigned to Horde DevelopersHorde Developers
State ⇒
 
05/03/2005 vilius (at) lnk (dot) lt Comment #1
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ regex bug in sieve driver
Queue ⇒ Ingo
Reply to this comment
Ingo incorrectly sends commas in regex expression to sieve backend. 
For example I wanted to create rule that filters all letters with more 
than 10 recipients. Regex for such rule looks like this: (@.*){11,0}. 
When I click "Save" sieve throws an error: {39}script errors: line 71: 
Unmatched \{.
This is because Ingo somehow thinks that this is two blocks: (@.*){11 
and 0}. Escaping comma with \ solves the problem.