Message287166
Neither I found CFWS in rfc2231. In addition, rfc 2045 (Introduction) says that Content-Disposition —where filename is defined— cannot include comments. However, Content-Type can include RFC 822 comments, so the filename should be de-commented in case it is inferred from the name parameter there.
I'm rather new to Python, and sticking to version 2 because of the packages I work with. I see Python3's email has a much more robust design. Does this mean Python2 cannot get fixed?
I attach a de_comment() function, copied from the one I mentioned this morning. The rest of the file shows its intended use. (Oops, it removes comments even from where they are not supposed to be allowed ;-)
Having that kind of functionality in email.utils would make it easier to read Message's, no? |
|
Date |
User |
Action |
Args |
2017-02-06 19:26:07 | ale2017 | set | recipients:
+ ale2017, barry, r.david.murray |
2017-02-06 19:26:07 | ale2017 | set | messageid: <1486409167.7.0.773429692359.issue29462@psf.upfronthosting.co.za> |
2017-02-06 19:26:07 | ale2017 | link | issue29462 messages |
2017-02-06 19:26:07 | ale2017 | create | |
|