[issue5277] email message.get_params() and related methods sometimes fail.

R. David Murray added the comment: Thanks Mark and Ryan for the patches, and Shashwat for the review. Committed to trunk in r80062, 2.6 in r80063, py3k in r80078, and 3.1 in r80079. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed

[issue5277] email message.get_params() and related methods sometimes fail.

Shashwat Anand added the comment: According to RFC2231 the named disposition (content disposition field) is provided by the MIME mechanism. The encoded parameter like the following: Content-Disposition: inline; filename*0="Re: [Mailman-Users] Messages shunted with \"TypeError: "; filename*1=

[issue5277] email message.get_params() and related methods sometimes fail.

Ryan Coyner added the comment: Okay, bug confirmed: >>> m = email.message_from_string('Content-Disposition: inline; filename*0="foo >>> \\"test"; filename*1="\\"bar"') >>> m.get_filename() 'foo "test"; filename*1=""bar' And here is the result with the patch applied: >>> m = email.message_fr

[issue5277] email message.get_params() and related methods sometimes fail.

Changes by R. David Murray : -- keywords: +easy priority: -> normal stage: -> test needed versions: +Python 2.7, Python 3.2 -Python 2.4, Python 2.5, Python 3.0 ___ Python tracker __

[issue5277] email message.get_params() and related methods sometimes fail.

New submission from Mark Sapiro : The message method get_params() and the related get_param() and get_filename() do not properly decode an RFC 2231 encoded parameter such as the following: Content-Disposition: inline; filename*0="Re: [Mailman-Users] Messages shunted with \"TypeError: "; filena