REPLY: 2:280/464 5fb00830   
   MSGID: 2:280/464.113 5fb0536c   
   CHRS: UTF-8 4   
   TZUTC: 0000   
   RFC-3339: 2020-11-14 22:00:12+0000   
   Hallo Wilfred!   
      
    MK>> UTC is correct for this node.   
      
    WvV> Is that node located in the 0 meridian timezone?   
      
   Nowhere near prime meridian but UTC is still the benchmark for syncing   
   networks.  All the system's times here are still UTC which makes things vastly   
   easier for sorting and other pruposes such as scheduling network events and   
   the such.   
      
    WvV> I'm guessing it's not, so that wouldn't be correct...   
      
   It is correct.  Saying otherwise would be wrong such as "TZUTC: 0000" instead   
   of "TZUTC: +0000".  FTS-4008 is wrong, wrong, wrong and is the source of   
   corruption for those east of prime meridian.  The RFC-3339 flag addresses this   
   particular major flaw in FTS-4008 and covers ALL the datetime issues including   
   the obsolete MSG datetime stamp.   
      
   So now that I've included TZUTC in all of the MSGs originating from here has   
   it made any difference there in any meaningful way?   
      
   Het leven is goed,   
   Maurice   
      
   ... ðone wisdom ðe ðe God sealde ðær ðær ðu hiene befæstan mæge,   
   befæste.   
       Wherever you can use the wisdom God gave you, use it.   
   --- GNU bash, version 5.0.18(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 120/340 123/131 124/5016 154/10 203/0 221/0   
   SEEN-BY: 226/30 227/114 229/101 424 426 452 664 1016 240/1120 2100   
   SEEN-BY: 240/5138 5411 5832 5853 249/206 317 400 280/464 5003 288/100   
   SEEN-BY: 292/8125 310/31 317/3 320/219 322/757 342/200 396/45 423/120   
   SEEN-BY: 633/280 770/1 2454/119   
   PATH: 280/464 240/5832 229/426