Message296141
The problem is that if it returns None on parse failure, then you can't tell the difference between the header not existing and the date not being parseable. I don't have a solution for this problem. Suggestions welcome. (Note that this is only a problem in the new policy, where the parsing is done automatically; in the compat32 policy you have to apply parsedate yourself, so you can tell the difference between a non-existent header and a failed date parse). |
|
Date |
User |
Action |
Args |
2017-06-16 01:25:02 | r.david.murray | set | recipients:
+ r.david.murray, barry, timb07 |
2017-06-16 01:25:02 | r.david.murray | set | messageid: <1497576302.61.0.731662822843.issue30681@psf.upfronthosting.co.za> |
2017-06-16 01:25:02 | r.david.murray | link | issue30681 messages |
2017-06-16 01:25:02 | r.david.murray | create | |
|