[issue38621] Bad decoding of encoded-words in unstructured email headers

Change by Fred Drake : -- resolution: fixed -> rejected stage: resolved -> ___ Python tracker ___ ___ Python-bugs-list mailing

[issue38621] Bad decoding of encoded-words in unstructured email headers

Fred Drake added the comment: It turns out this was a problem in 3.7.4; Python 3.7.5 seems to have fixed this. Sorry for the noise. Guess it's time to update my application to use 3.7.5! -- resolution: -> fixed stage: -> resolved status: open -> closed

[issue38621] Bad decoding of encoded-words in unstructured email headers

Change by Ned Deily : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38621] Bad decoding of encoded-words in unstructured email headers

Fred Drake added the comment: This problem does not exist in Python 3.6 or Python 3.8; it appears to only exist in Python 3.7. -- versions: +Python 3.7 ___ Python tracker

[issue38621] Bad decoding of encoded-words in unstructured email headers

Change by Karthikeyan Singaravelan : -- nosy: +maxking ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38621] Bad decoding of encoded-words in unstructured email headers

Fred Drake added the comment: It's worth noting that dealing with this header eventually causes the header parser to enter an infinite loop. -- ___ Python tracker ___

[issue38621] Bad decoding of encoded-words in unstructured email headers

New submission from Fred Drake : I've encountered a problem parsing an email with this Subject: header: Subject: Be sure to redeem your =?utf-8?Q?$?=201.71 credit card reward certificate by the end of the year email._header_value_parser.get_unstructured defers to get_encoded_word, passing