[issue35342] email "default" policy raises exception iterating over unparseable date headers

Irit Katriel added the comment: I get the same result on macOS as on Windows, it seems this was fixed in https://github.com/python/cpython/pull/22090, there are unit tests there for invalid dates passed to parsedate_to_datetime. -- status: pending -> closed _

[issue35342] email "default" policy raises exception iterating over unparseable date headers

Irit Katriel added the comment: I get this. Was the bug fixed? >>> email.message_from_string('Date: not a parseable date', >>> policy=email.policy.default).items() [('Date', 'not a parseable date')] -- nosy: +iritkatriel status: open -> pending __

[issue35342] email "default" policy raises exception iterating over unparseable date headers

R. David Murray added the comment: This is effectively a duplicate of #30681, which has a solution, although it is not yet in final form per the last couple of comments on the issue and the PR. -- resolution: -> duplicate stage: -> resolved superseder: -> email.utils.parsedate_to_d

[issue35342] email "default" policy raises exception iterating over unparseable date headers

Change by Richard Brooksby : -- versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue35342] email "default" policy raises exception iterating over unparseable date headers

Change by Richard Brooksby : -- versions: +Python 3.6 -Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue35342] email "default" policy raises exception iterating over unparseable date headers

New submission from Richard Brooksby : It is not possible to loop over the headers of a message with an unparseable date field using the "default" policy. This means that a poison email can break email processing. I expect to be able to process an email with an unparseable date field using