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

[Irit Katriel]

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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Irit Katriel]

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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[R. David Murray]

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_datetime() should return None when 
date cannot be parsed
versions: +Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Richard Brooksby]

Change by Richard Brooksby :


--
versions: +Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Richard Brooksby]

Change by Richard Brooksby :


--
versions: +Python 3.6 -Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Richard Brooksby]

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 
the "default" policy.

$ python3 --version
Python 3.6.7
$ python3
Python 3.6.7 (default, Oct 22 2018, 11:32:17) 
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import email
>>> import email.policy
>>> email.message_from_string('Date: not a parseable date', 
>>> policy=email.policy.default).items()
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3.6/email/message.py", line 460, in items
for k, v in self._headers]
  File "/usr/lib/python3.6/email/message.py", line 460, in 
for k, v in self._headers]
  File "/usr/lib/python3.6/email/policy.py", line 162, in header_fetch_parse
return self.header_factory(name, value)
  File "/usr/lib/python3.6/email/headerregistry.py", line 589, in __call__
return self[name](name, value)
  File "/usr/lib/python3.6/email/headerregistry.py", line 197, in __new__
cls.parse(value, kwds)
  File "/usr/lib/python3.6/email/headerregistry.py", line 306, in parse
value = utils.parsedate_to_datetime(value)
  File "/usr/lib/python3.6/email/utils.py", line 210, in parsedate_to_datetime
*dtuple, tz = _parsedate_tz(data)
TypeError: 'NoneType' object is not iterable
>>> 

Related: 
https://docs.python.org/3/library/email.headerregistry.html#email.headerregistry.DateHeader
 does not specify what happens to the datetime field if a date header cannot be 
parsed.

Related: 
https://docs.python.org/3/library/email.utils.html#email.utils.parsedate_to_datetime
 does not specify what happens if a date cannot be parsed.

Suggested tests: random fuzz testing of the contents of all email headers, 
especially those with parsers in the header registry.

--
components: email
messages: 330621
nosy: barry, r.david.murray, rptb1
priority: normal
severity: normal
status: open
title: email "default" policy raises exception iterating over unparseable date 
headers
type: behavior
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com