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	> What if we just check the user supplied header for validity according > to RFC 2822 section 2.2? > > > > "A field name MUST be composed of printable US-ASCII characters > (i.e., characters that have values between 33 and 126, inclusive), > except colon."
Attachment
Watch this ticket