Hey Wilfred!

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

 WvV> That's a broken MSGID implementation, because it could be
 WvV> possible your system generates 2 (or more) messages in the same
 WvV> second (maybe automated ones).

Understood.  I noticed that way back in the 1990's and brought it up back then.
 However for a single user application such as what I am doing this is not an
issue.  Basically all I've done is to write an offline application using a
slightly modified FTN MSG format that generates it's own MSGID so that when
tossed by a regular automated tosser such as hpt (not abandonware ... yet)
there shouldn't be an issue with dupes since there are none.  Right?

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

 WvV> Illegal characters without a CHRS: kludge!

Again it appears to be working without a useless CHRS kludge, especially in the
case of UTF-8 as the above quote clearly demonstrates.  Also with older 16-bit
DOS editors quoting UTF-8 characters works 100% which cannot be said about most
(all?) FTN compliant editors.

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

It doesn't matter since it does nothing.  It's the 8-bit character sets,
especially the so-called LATIN-1 codes, that are totally fscked up.  Ignore it
and there is no problem.  :-)

Life is good,
Maurice

      ^-^-^-@@-^-^-^
           (..)-----;
              ||---||
              ^^   ^^
... A Møøse once bit my sister ...
--- GNU bash, version 5.0.18(1)-release (x86_64-motorshed-linux-gnu)