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?
Regards,
Kevin.
Attachments:
+ http://mailtools.anomy.net/archives/anomy-list//2006-05/63aa3610/01.sanitizer-header-parse-fix-diff.txt