[issue11021] email MIME-Version headers for each part in multipart message

2021-01-12 Thread robin
robin added the comment: Propose to close as duplicate of https://bugs.python.org/issue25235 -- nosy: +eriker ___ Python tracker ___

[issue11021] email MIME-Version headers for each part in multipart message

2012-05-23 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- assignee: r.david.murray - components: +email -Library (Lib) nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11021 ___

[issue11021] email MIME-Version headers for each part in multipart message

2011-03-14 Thread David Caro
David Caro david.caro.este...@gmail.com added the comment: Of course, the RFC that discusses the MIME-Version Header is RFC-2045 http://www.ietf.org/rfc/rfc2045.txt Extract of the page 8: Note that the MIME-Version header field is required at the top level of a message. It is not

[issue11021] email MIME-Version headers for each part in multipart message

2011-03-14 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: Yes, if it is not actually an RFC non-compliance I'd rather not backport it, but I'm not averse to changing it. I'm open to argument about backporting though...if you know of spam filters that actually do count it, let me know.

[issue11021] email MIME-Version headers for each part in multipart message

2011-03-13 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: Assuming this is correct (I haven't tried looking for the reference yet), I'm leaning toward it being enough of a behavior change that it should not be backported. -- versions: +Python 3.3 -Python 2.7, Python 3.1, Python 3.2

[issue11021] email MIME-Version headers for each part in multipart message

2011-01-26 Thread David Caro
New submission from David Caro david.caro.este...@gmail.com: When attaching a subpart to a multipart message, python should follow the recomendations of the rfcs and remove the MIME-Version header of each part, leaving only one MIME-Version header at the beggining of the message. from

[issue11021] email MIME-Version headers for each part in multipart message

2011-01-26 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: For the record, can you point to the relevant part of the relevant RFC? -- assignee: - r.david.murray nosy: +r.david.murray stage: - needs patch versions: +Python 3.1, Python 3.2 -Python 2.6