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

* Your Email Address
* Spam protection	Enter the letters below: ._. __ . .._..__. \| / `\|__\| \| \| \| _\|_\__.\| \|_\|_\|__\|
Comment	> Checking for valid characters would work for me, however keep in mind > that some drivers that do raw or regexp matching on full header lines > (for instance, maildrop and procmail) might need the trailing colon > to avoid matching unrelated data on corrupt messages - be sure to > check if the corresponding output drivers in Ingo add those colons.
Attachment
Watch this ticket