Date: header should be in user's local timezone, not server's timezone

[ptm]

When about to send an email, RoundCube inserts the Date: header. The timezone used is the server's local time.

The timezone should match the user's preferences instead.

For example, if my server is in the US, but my user is in Australia, the header _should_ read:

Date: Sat, 12 Sep 2009 20:00:00 +1000 <- Australian time

_not_:

Date: Sat, 12 Sep 2009 03:00:00 -0700 <- USA time

[alec]

Is this recommended/required by some RFC? I think it's better to rely on server's time settings than client's.

[ptm]

Replying to alec:

Is this recommended/required by some RFC? I think it's better to rely on server's time settings than client's.

I am not aware of any RFCs that deal with this specifically, however I can offer some better precedents:

1. A multi-user unix host. The server resides in the USA, and the time is kept accurate by NTP. Users in California, USA log on and see the correct time. A user in Sydney, Australia, logs on too, and also sees the correct time... it has been adjusted for local time by setting the TZ environment variable.

The mail user agent for both these users will stamp the _correct_ time on outgoing mail... but in each individual user's timezone.

2. Other webmail clients exhibit the desired behavior. Example: ​SquirrelMail.

So, yes, rely on the server's _time_, but also the user's desired _timezone_. Besides, the default will be the server's timezone anyway...

[alec]

See also #1486786

[alec]

Fixed in [2bf3cc6f].