[New-bugs-announce] [issue1079] decode_header does not follow RFC 2047

Mickaël Guérin report at bugs.python.org
Sat Sep 1 10:56:59 CEST 2007

New submission from Mickaël Guérin:

email.header.decode_header expect a space or end of line after the end
of an encoded word ("?="). There is nothing about that thing in RFC 2047.

Python 2.5.1 ChangeLog seems to indicate that this bug has been solved.
Unfortunately, the function still don't work.

A visible effet of the bad regex used has the consequence found in Issue

it seems there are 2 different regex with the same purpose in two
different files (ecre in header.py & ecre in utils.py). the one in
utils.py seems to give better results.

components: Library (Lib)
messages: 55555
nosy: kael
severity: normal
status: open
title: decode_header does not follow RFC 2047
versions: Python 2.5

Tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list