TID: FMail-lnx64 2.1.0.18-B20170815   
   RFC-X-No-Archive: Yes   
   TZUTC: 0200   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 5ca4da1e   
   REPLY: 1:153/7001 5ca4d3f4   
   Hi Maurice,   
      
   On 2019-04-03 15:40:36, you wrote to me:   
      
    WvV>> 2 Different node/point numbers?   
      
    MK> Why not?  As far as I can tell there could be 65536 different node/point   
    MK> numbers if the MSGID were to use them for different processes and/or users   
    MK> while the Origin only uses the actual address of the node wrt the   
   nodelist.   
    MK> I don't see where that breaks with current standards.  If it does please   
    MK> feel free to illuminate.   
      
   I just don't think it's good practice. It's confusing to both humans and   
   software. For instance if someone wants to send a reply by netmail which of   
   the two should be used?   
      
    MK> Speaking of standards, what about "CHRS: UTF-8 2"?  Even in the pure   
    MK> fantasy land of fts-5003.001 that appears to be bogus.  :-)   
      
   Yeah, I know, it's been pointed out to me before. I use a more or less default   
   golded configuration regarding charsets. I'll have to look into this to fix it   
   somewhere. But I don't care too much, most of my messages just contain plain   
   ascii, so there's nothing to translate for software on receivers systems   
   anyway that need the CHRS kludge for this.   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 15/2 18/200 123/1970 154/10 203/0 221/0 226/17 229/107 354   
   SEEN-BY: 229/426 452 1014 240/5832 249/206 317 400 280/464 5003 310/31   
   SEEN-BY: 317/3 322/757 342/200 393/68 396/45 423/120 633/280 770/1   
   PATH: 280/464 229/426