6.0.0-beta1
7/11/25

[#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 slusarz (at) horde (dot) org
Requester vilius (at) lnk (dot) lt
Created 05/03/2005 (7374 days ago)
Due
Updated 05/25/2005 (7352 days ago)
Assigned 05/25/2005 (7352 days ago)
Resolved 05/25/2005 (7352 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
05/25/2005 04:34:23 PM Jan Schneider State ⇒ Resolved
 
05/25/2005 04:10:49 PM Chuck Hagenbuch Assigned to Michael Slusarz
Taken from Horde DevelopersHorde Developers
State ⇒ Assigned
 
05/03/2005 01:56:34 PM Chuck Hagenbuch Assigned to Horde DevelopersHorde Developers
State ⇒
 
05/03/2005 01:00:21 PM 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.

Saved Queries