Re: Sanitizer dropping content-transfer-encoding?

From: Kevin Shanahan (
Date: Thu 11 May 2006 - 21:16:40 GMT

  • Next message: Paolo: "Re: Sanitizer dropping content-transfer-encoding?"

    On Wed, 2006-05-10 at 14:07 +0930, Kevin Shanahan wrote:
    > I've discovered a problem that seems to be triggering for us on emails
    > from particular organisations. Something about the message formatting is
    > causing the sanitized email to lose the content-transfer-encoding that
    > is present in the original. Staff then see all the '=0D=0A' characters
    > in their messages.

    Okay, I think I found where the header parsing was getting confused. As
    far as I can tell, RFC2045 doesn't require a space between the
    "Content-Transfer-Encoding:" and the mechanism. Does the attached patch
    look okay?



    hosted by