TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 5fb5449d
REPLY: 2:280/464.113 5fb53d4d
Hi Maurice,

On 2020-11-18 07:27:09, you wrote to me:

 WvV>> I'm talking about localtime not UTC, but you knew that. ;)

 MK> Which is the same thing here.  /etc/localtime = /usr/share/zoneinfo/UTC.

That you set your local time to UTC, doesn't make it the real world localtime
where your equipment is located. Men you are stuborn. :-/

 MK> Also;

 MK> -={ ':read !date' }=-
 MK> Wed 18 Nov 2020 03:29:48 PM UTC

 MK> Note the UTC at the end of the localtime date string.  hwclock shows
 MK> "2020-11-18 15:34:08.481082+00:00" as we speak.  Everything that matters
is
 MK> UTC as it should be.  I made the adjustment for the msg header's datetime
 MK> stamp and the TZUTC flag in the code but am thinking of a per user setup
 MK> configuration set to whatever the user's localtime is instead of the
 MK> system's localtime.  As you can plainly see they are different.

 MK> Anyhow this is the best this can possibly be all things considered.  I
plan
 MK> to continue ignoring the TZUTC and CHRS flags

As you please...

 MK> but I can assure you that the ones you see are indeed accurate albiet
 MK> useless for any meaningful deployment.

Fine...


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 18/200 90/1 105/81 120/340 123/131 124/5016 154/10
SEEN-BY: 203/0 221/0 226/30 227/114 229/101 424 426 452 664 1016 240/5832
SEEN-BY: 249/110 206 317 400 280/464 5003 288/100 292/8125 310/31
SEEN-BY: 317/3 322/757 342/200 396/45 423/120 633/280 770/1
PATH: 280/464 229/101 426