[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages
Roundup Robot devnull@devnull added the comment: New changeset 5a2602939d5d by R David Murray in branch 'default': #1874: detect invalid multipart CTE and report it as a defect. http://hg.python.org/cpython/rev/5a2602939d5d -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages
R. David Murray rdmur...@bitdance.com added the comment: Thanks for the patches. I didn't use them, but they were helpful references. This is in a grey area between a bug and a feature request. The fact is, though, that for the most part the email module currently doesn't make extra effort to detect defects, it just reports the ones it has to work around. The only exception I found to this was taking an extra step to report a defect that represented a defect in the constructed model of the message. Now, in the next version of email (targeted for 3.3), one of the design goals is to detect as many RFC conformance defects as practical. So, I'm treating this as a feature request, and have checked it in to 3.3 (default). -- resolution: - accepted stage: - committed/rejected status: open - closed type: behavior - feature request versions: +Python 3.3 -Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: +r.david.murray versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5, Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages
Sergio Oliveira Campos [EMAIL PROTECTED] added the comment: Added check to conform RFC2045 (section 6.4) for Python 2.6 -- nosy: +seocam Added file: http://bugs.python.org/file10275/issue1874-fixed-2.6.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1874 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages
Changes by Vinicius Baggio Fuentes [EMAIL PROTECTED]: -- nosy: +vinibaggio __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1874 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages
Changes by Christian Heimes: -- keywords: +easy, patch priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1874 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages
New submission from Jonathan Share: Although the documentation of FeedParser states that It will populate a message object's defects attribute with a list of any problems it found in a message. no defect is found in the test case I am about to upload. The message in the test case is broken because it specifies a Content-Transfer-Encoding that is not valid for multipart/* messages[1]. I've spent some time today looking at the parser and cannot see where the parser is doing anything with the Content-Transfer-Encoding of a multipart message, leading me to believe that there might be another bug here with regards to not honoring Content-Transfer-Encoding at all for multipart/* messages but I don't have any more time today to look at it, I'll have to go away and read the rfc really well. If someone can guide me on how to get this test to pass then I can probably get a good test case and fix written for issue1823 as well. [1] http://tools.ietf.org/html/rfc2045#section-6.4 -- components: Library (Lib) messages: 60207 nosy: Sharebear, barry severity: normal status: open title: email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages type: behavior versions: Python 2.5, Python 2.6, Python 3.0 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1874 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages
Changes by Jonathan Share: Added file: http://bugs.python.org/file9227/issue1874.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1874 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
