f1a0fd20d6
If a message date would fail to parse, the worker would never receive the MessageInfo it asked for, and so it wouldn't display the message. The problem is the spec for date formats is too lax, so trying to ensure we can parse every weird date format out there is not a strategy we want to pursue. On the other hand, preventing the user from reading and working with a message due to the error format is also not a solution. The maildir and notmuch workers will now fallback to the internal date, which is based on the received header if we can't parse the format of the Date header. The UI will also fallback to the received header whenever the date header can't be parsed. This patch is based on the work done by Lyudmil Angelov <lyudmilangelov@gmail.com> But tries to handle a parsing error a bit more gracefully instead of just returning the zero date. |
||
---|---|---|
.. | ||
format | ||
sort | ||
templates | ||
ui | ||
uidstore | ||
dirstore.go | ||
history.go | ||
keystore.go | ||
messageview.go | ||
msgstore.go | ||
oauthbearer.go | ||
open.go | ||
open_darwin.go | ||
socket.go | ||
structure_helpers.go |