Re: [Nmh-workers] proposed patch for shell metacharacter failure in nmh-1.7

[Andy Bradford]

Thus said Ken Hornstein on Sat, 20 Jan 2018 13:59:20 -0500:

> Forgive me if  this is a dumb  question, but ... why do  you care what
> the timezone is in your Date: headers?

Personally,  I've always  found the  timezone in  the Date  header quite
useful to convey a  sense of time. If all timezones  in Date headers are
UTC, then it  becomes difficult for interlocutors to  to predict whether
or not they're likely to receive a response to an email.

For example, the Date header in your  email indicates to me that you are
somewhere in EST and if I were  respond to this email at 22:00 MST time,
I wouldn't likely expect an answer until the next morning.

Indeed, his script does include this comment:

#  it's annoying to view Date: headers marked in a different time zone;
#  that annoyance wasn't important in a world where invalid time zones were
#  infrequent, but EVERY SINGLE MESSAGE from Concordia's new Exchange
#  servers is stamped in UTC :-(

I  too have  been extremely  annoyed by  the fact  that Outlook/Exchange
emails are all in UTC as it destroys the abovementioned utility.

Had your Date header  been in UTC, I could not  make any such inference,
however, given the  current state of communicating  with Exchange users,
would converting the Date  header to my local time be of  any use to me?
Yes, because at least now I can gauge it relative to my local time.

Fortunately, my  email client (exmh)  does this for me  without actually
altering the message itself. Your Date header in (exmh) shows up as:

Date: Sat, 20 Jan 2018 13:59:20 -0500 (11:59 MST)

While on disk it remains:

Date: Sat, 20 Jan 2018 13:59:20 -0500

Andy
-- 
TAI64 timestamp: 400000005a63b250