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

* Your Email Address
* Spam protection	Enter the letters below: . ..___.__.. __ \|\/\|[__ \| \|\| / ` \| \|[___\|__\|\|___\__.
Comment	> Care to explain why you're trying to shift the blame on somebody > else, rather than reading and understanding what is presented? > > > > Why/how this would be a Cyrus bug if (1) Horde/Ingo creates invalid > sieve scripts through improper input validation or output generation > (excess colon) and (2) some glue then silently drops the error > message to the floor? > > > > That makes two bugs in Horde here and zero in Cyrus timsieved - even > if you cannot reproduce the "dropped error message" part (No. 2 > above), the other bug remains.
Attachment
Watch this ticket