TID: FMail-lnx64 2.1.0.19-B20221229   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 63b048bd   
   REPLY: 2:280/464 63b035e9   
   Hi Tommi,   
      
   On 2022-12-31 14:14:40, I wrote to you:   
      
    TK>> But I made some research with GoldED's JAM hexdumps. There are two   
    TK>> ways to store the TZUTC in JAM.   
      
    TK>> 02004 [  4]: "0200"              smapinntpd & gecho   
    TK>> 02000 [ 11]: "TZUTC: 0200"       jamnntpd & golded   
      
    TK>> Maybe there is the reason why FMail strips the TZUTC when exporting?   
      
    WvV> That rings a bell. But I have to investigate...   
      
   Found it! That special jam subfield 2004 is ignored by FMail. Apparently it is   
   hardly ever used by software. Because it was in FMail like this from the   
   start, a few decades ago. Golded knows how to handle it when encountered, but   
   doesn't use it when creating new messages in the jambase...   
      
   It should be an easy fix, but it will have to wait until next year. ;-)   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.19-B20221229   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 1/19 123 15/0 16/0 19/37 90/1 103/705 105/81 106/201 120/340   
   SEEN-BY: 123/130 131 124/5016 129/305 142/104 153/757 7715 154/10   
   SEEN-BY: 203/0 218/700 221/0 226/30 229/110 111 112 113 114 206 307   
   SEEN-BY: 229/317 424 426 428 470 550 664 700 240/1120 5411 5832 5853   
   SEEN-BY: 266/512 280/464 5003 5555 282/1038 292/854 8125 301/1 310/31   
   SEEN-BY: 317/3 320/119 219 319 2119 322/0 757 326/101 341/66 234 342/200   
   SEEN-BY: 396/45 423/120 460/58 633/280 712/848 770/1 2454/119   
   PATH: 280/464 240/5832 320/219 229/426