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 5fc7c201
REPLY: 1:153/7001 5fc7b5b0
Hi Maurice,

On 2020-12-02 15:41:36, you wrote to me:

 MK> @MSGID: 1:153/7001 5fc7b5b0
 MK> @REPLY: 2:280/464 5fc76588

 WvV>> I would call it broken, with only the MSGID flag...

 MK> No more broken than with all the additional flags.  Note that this reply
 MK> contains a REPLY flag that matches your MSGID as per specs, as well as
 MK> nonconforming MSGIDs that certain software generates.  Also the hex part
of
 MK> the MSGID can be used to generate a real datetime stamp accurate to the
 MK> second and is vastly more informative than any so-called fix for the
 MK> obsolete MSG header's datetime stamp;

 MK>   $ date --date="@$(printf "%d" 0x5fc6f369)"
 MK> Wed 02 Dec 2020 01:52:41 AM UTC

That's a broken MSGID implementation, because it could be possible your system
generates 2 (or more) messages in the same second (maybe automated ones). In
that case there would be 2 (or more) different messages with the same MSGID...

 MK> ... A Møøse once bit my sister ...

Illegal characters without a CHRS: kludge!

(And yes I know mine isn't correct ;-))

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/1120
SEEN-BY: 240/2100 5138 5411 5832 5853 249/206 317 400 280/464 5003
SEEN-BY: 288/100 292/8125 310/31 317/3 320/219 322/757 342/200 396/45
SEEN-BY: 423/120 460/58 633/280 770/1 2454/119
PATH: 280/464 240/5832 229/426