Message358395
Yes, google should fix their bug. However, the python email package tries very hard to interpret even RFC-non-compliant emails when there is a way to do so. As I said, the package already tries to interpret headers such as google is generating, it's just that there is a bug in that interpretation: it is keeping the blank between then encoded words when it should not be. That bug can be fixed, in get_raw_encoded_word and/or get_parameter, in email._header_value_parser. |
|
Date |
User |
Action |
Args |
2019-12-14 15:28:49 | r.david.murray | set | recipients:
+ r.david.murray, barry, mkaiser |
2019-12-14 15:28:49 | r.david.murray | set | messageid: <1576337329.72.0.249558361184.issue39040@roundup.psfhosted.org> |
2019-12-14 15:28:49 | r.david.murray | link | issue39040 messages |
2019-12-14 15:28:49 | r.david.murray | create | |
|