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 5fb14122   
   REPLY: 2:280/464.113 5fb0536c   
   Hi Maurice,   
      
   On 2020-11-14 22:00:12, you wrote to me:   
      
    MK>>> UTC is correct for this node.   
      
    WvV>> Is that node located in the 0 meridian timezone?   
      
    MK> Nowhere near prime meridian but UTC is still the benchmark for syncing   
    MK> networks.  All the system's times here are still UTC which makes things   
    MK> vastly easier for sorting and other pruposes such as scheduling network   
    MK> events and the such.   
      
   It is advised that you set the hardware clock of a linux system to UTC. All   
   the systems I run have that too. But they also know their location and offset   
   to UTC, so they can present the correct localtime.   
      
    WvV>> I'm guessing it's not, so that wouldn't be correct...   
      
    MK> It is correct.   
      
   No it isn't.   
      
    MK> Saying otherwise would be wrong such as "TZUTC: 0000" instead of   
    MK> "TZUTC: +0000".  FTS-4008 is wrong, wrong, wrong and is the source of   
    MK> corruption for those east of prime meridian.   
      
   FTS-4008 Is right by definition. It's the fidonet standard. That it's not the   
   same as other standards doesn't matter.   
      
    MK> So now that I've included TZUTC in all of the MSGs originating from   
    MK> here has it made any difference there in any meaningful way?   
      
   Only if it's not 'TZUTC: 0000'. ;)   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   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