REPLY: 2:333/808.7 5faeca5b   
   MSGID: 1:153/7001.2989 5faed519   
   CHRS: UTF-8 4   
   RFC-3339:  2020-11-13 10:48:57-08:00   
   Hey August!   
      
    AA> OpenXP does a fine job of it.   
      
   I'd like to see the routine.  Best I can think of is to combine the MSG header   
   datetime stamp with the TZUTC and then use that resulting string to make the   
   adjustment.  Your combined msg header date and TZUTC string would be "13 Nov   
   20  18:58:54+0100" which requires extra steps to assemble as well as to tack   
   on the '+' character onto the TZUTC which is lacking and NEEDED to do proper   
   conversions.  A rfc-3339 datetime stamp is vastly superior and contains   
   everything needed.  In your case it would be "2020-11-13 18:58:54+0100" which   
   is the same as "2020-11-13 09:58:54-08:00" relative to 1:153/7001.2989.   
      
   Anyhow it is doable but requires additional processing in order to honour an   
   obsolete datetime stamp (two digit year) and a corrupted utc offset which   
   lacks the required '+' prefix for timezones east of prime meridian.   
      
   Life is good,   
   Maurice   
      
   ... Freond deah feor ge neah; byð near nyttra.   
       A friend is useful, far or near; the nearer the better.   
   --- GNU bash, version 5.0.18(1)-release (x86_64-motorshed-linux-gnu)   
    * Origin: Coffin Point - Ladysmith BC, Canada (1:153/7001.2989)   
   SEEN-BY: 1/123 18/200 90/1 120/340 123/131 124/5016 153/105 135 757   
   SEEN-BY: 153/802 6809 7001 154/10 203/0 221/0 1 6 360 226/30 227/114   
   SEEN-BY: 229/101 424 426 452 664 1016 230/0 240/1120 2100 5138 5411   
   SEEN-BY: 240/5832 5853 249/206 317 400 261/38 280/464 5003 288/100   
   SEEN-BY: 292/8125 310/31 317/3 320/219 322/757 335/364 342/17 200   
   SEEN-BY: 396/45 423/81 120 633/280 770/1 2454/119 4500/1   
   PATH: 153/7001 757 221/6 1 280/464 240/5832 229/426