#3890: mutt_mktime is ambiguous near DST change
---------------------+----------------------
Reporter: vinc17 | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: mutt | Version: 1.7.1
Resolution: | Keywords:
---------------------+----------------------
Comment (by vinc17):
Replying to [comment:11 derekmartin]:
> Replying to [comment:10 vinc17]:
> > And when no timezone information is provided in a mail, assuming the
current local timezone is incorrect.
>
> Is it? Is that stated in the RFC?
I suspect that timezone information is mandatory in general, so that this
is out of scope of RFC's. But there's still the following specific case
([https://tools.ietf.org/html/rfc5322#section-3.3 RFC 5322, 3.3. Date and
Time Specification]):
Though "-0000" also indicates Universal Time, it is
used to indicate that the time was generated on a system that may be
in a local time zone other than Universal Time and that the date-time
contains no information about the local time zone.
which makes the difference between UTC and no timezone information
ambiguous.
But the main problem is the inconsistency / non reproducibility: If you
travel, the dates would appear as different from before.
> I'd guess that the far more common case is for people to receive e-mail
from friends and coworkers who live/work in the same time zone.
In the most common case, the timezone is provided. And I wouldn't deduce
anything from an unusual case where the timezone is not provided.
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3890#comment:12>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
