MSGID: 2:280/464.113 5fdc0851   
   CHRS: UTF-8 4   
   TZUTC: -0800   
   -={ Geloofwaardige datetime-stempel voor Ladysmith BC, Canada: 2020-12-17   
   17:39:29 -0800 }=-   
      
   Hallo All!   
      
   After playing around with two digit years I've discovered that at the zero   
   hour of January 1st 2069 coreutil's date application suddenly reverts back to   
   1969 as shown below;   
      
   -={ date --date='31 Dec 68 23:59:59 +0000' +'%F %T %z' }=-   
   2068-12-31 23:59:59 +0000   
      
   -={ date --date='1 Jan 69 00:00:00 +0000' +'%F %T %z' }=-   
   1969-01-01 00:00:00 +0000   
      
   Note that I am using for input the FTN two digit year with a corrected UTC   
   offset rather than the documented fts-4008 TZUTC flag which will produce an   
   error for all eastern timezones using proper date and time applications no   
   matter if two or four digit years.  I am not aware of any routine that will   
   properly compensate for this obvious flaw other than one I wrote specifically   
   to address the FTSC's obvious handicap when it comes to recognizing reality   
   and their part in the propagation of msg corruption.  :::tsk, tsk:::   
      
   Of further interest is the output of converting 2069 datetime stamps to   
   unixtime will produce negative seconds that will be repeated in reverse in   
   2070 since everything up to 2099 reverts back to the 1900's as shown below;   
      
   -={ date --date='1 Jan 69 00:00:01 +0000' +'%s' }=-   
   -31535999   
      
   -={ date --date='31 Dec 70 23:59:59 +0000' +'%s' }=-   
   31535999   
      
   Not good at all but not as bad as other examples of total two digit year   
   corruption caused by other datetime apps as well as differing OSes and their   
   associated problems with two digit years ... but I won't since they are really   
   depressing to read about to say the least.  Instead I will offer up that the   
   corrected datetime stamp at the start of this message was calculated by the   
   coreutils-8.32 date application as well as the FTN msgHeader's two digit year   
   which is NEVER used again for anything.  The proper solution would be to   
   finally get rid of it which should have happened at least in 2002 when it was   
   declared obsolete in use for digital communications.  If it isn't obvious to   
   you then I am guessing you're a member of the FTSC.  :::snicker:::   
      
   Het leven is goed,   
   Maurice   
      
   ... Gyf þu well sprece, wyrc æfter swa.   
       If you speak well, act accordingly.   
   --- GNU bash, version 5.1.0(1)-release (x86_64-motorshed-linux-gnu)   
    * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)   
   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 460/58 633/280 770/1   
   PATH: 280/464 229/101 426