#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 derekmartin):
Replying to [comment:10 vinc17]:
> But when the offset is provided, there is no ambiguity and it is not the
local timezone that should be used.
I agree, but AFAICT in many of these cases, Mutt is treating the time as
GMT when it is in fact not.
> 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? It seems pretty unintuitive that
assuming the local time zone is wrong... 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. Assuming GMT will guarantee that most of
their mail will be treated as having a wrong time.
> It would be simpler to remove the {{{local}}} argument.
Local is only used in a couple of spots, and I *think* it's used
appropriately. So I don't believe that helps the situation at all. I'd
really need to analyze how the time_t's that are produced are being used a
bit more carefully than I have, to be sure.
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3890#comment:11>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
