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 5fb185e6   
   REPLY: 2:460/58 0000006e   
   Hi August,   
      
   On 2020-11-15 20:06:13, you wrote to me:   
      
    AA> Where the real magic resides, I find, is in a program that can utilize   
    AA> the TZUTC info in such a way it organizes the message in true   
    AA> chronological order in a thread - and not based on arrival time.  For   
    AA> instance, if don't read an echo for days, but different people write   
    AA> messages with true replies prior to that at different times, the   
    AA> actual order of the messages in a thread are connected to a parent   
    AA> message in the time order that people thus spoke.   
      
   I know, and I even thought about implementing such a function in FMail. But it   
   would be difficult to do it right. Because for instance there are messages   
   without the TZUTC kludge. How do you sort those. I you use TZUTC 0000 as   
   default, they will probably end up in the wrong order. I thought about   
   creating a table for this that couples the netnumber to a particular timezone,   
   but there probably are nets, that have nodes in different timezones. And of   
   course there are nodes that are in nets that are not in their timezone. So   
   lots of things that can go wrong, so I never took the time. ;)   
      
   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