Tickets :: Comment on [#8105] sieve driver doesn't check header field validity

Search Results: 19 of 33 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: __.. ..__ .__ __ (__ \|_/ [__)\| \/ ` .__)\| \[__)\|__/\__.
Comment	>> Read again what I wrote. Cyrus/timsieved is already checking the > >> validity of the script and returns an error message where > >> appropriate. If it doesn't do that for your, then your server is > >> broken period. > > > > Cyrus isn't broken, as the error is reported via sieveshell, but not > without Heiko's patch to some part of the Horde framework I do not > see. > > > > The problem remains, generation of invalid scripts. I think Ingo, > being able to generate output for various different filter engines > (sieve only one of them), should normalize these filters - they are > configured by non-technical users, and expecting them to know the > details of Sieve syntax is expecting too much anyways.
Attachment
Watch this ticket