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 5faffc2d   
   REPLY: 1:153/7001 5faf0db8   
   Hi Maurice,   
      
   On 2020-11-13 22:50:32, you wrote to me:   
      
    MK> @TZUTC: 0000   
    MK> @RFC-3339: 2020-11-13 22:50:32+0000   
      
    WvV>> But that's not the TZUTC flag. ;)   
      
    MK> I forgot to turn them both on in the last reply.  Let me know if it   
    MK> actually makes a difference.  Also I took the liberty of dropping the ':'   
    MK> character between hours and minutes in the TZ part of the RFC-3339 flag   
    MK> which now perfectly matches the digits in the TZUTC flag.  It makes no   
    MK> difference to it's enhanced usage over the both the MSG header datetime   
    MK> stamp with the TZUTC and vastly eliminates much code in order to make   
   TZUTC   
    MK> useful.   
      
   It's in UTC on this message, the next one is ok though...   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 1/123 18/200 90/1 114/705 120/340 123/120 131 226/30 227/114   
   SEEN-BY: 229/101 424 426 452 664 1016 240/5832 249/206 317 400 250/5   
   SEEN-BY: 250/8 298/25 305/3 317/3 322/757 342/200 633/280   
   PATH: 280/464 770/1 317/3 229/426