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 60780064   
   REPLY: 2:221/1.58@fidonet ef697c7e   
   Hi August,   
      
   On 2021-04-14 18:18:00, you wrote to me:   
      
    MK>>> @MSGID: 1:153/7001 tmCYOYVw   
    MK>>> Please note the MSGID of this reply.   
      
    WvV>> Besides not conforming to the standard, and maybe cosing   
    WvV>> problems in software down the line...   
      
    AA> It seems to be a problem for WinPoint when building a reply   
    AA> message.  The REPLYID seems to result in 00000000.   
      
   So that is the first discovered problem. There are probably more. And probably   
   harder to discover...   
      
    WvV>> Because it doesn't conform to the standard (not strictly   
    WvV>> hex chars),   
      
    AA> You are adding words to the spec.  "strictly" does not appear.   
      
    AA> ;)  However, "may" is very clear.  :D   
      
   I beg to differ...   
      
    WvV>> my tosser uses a different method for calculating a hash   
    WvV>> for this message (for dupe detection), which uses more cpu   
    WvV>> cycles. And thus heating up the planet more than a   
    WvV>> standard conforming MSGID. :-(   
      
    AA> They're all just a bunch of 1's and 0's in the end.  It's all   
    AA> the same stuff.  :D   
      
   But how we get there isn't...   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 1/123 18/200 90/1 105/81 120/340 123/131 124/5016 129/305   
   SEEN-BY: 154/10 203/0 221/0 226/30 227/114 229/101 424 426 452 664   
   SEEN-BY: 229/700 1016 1017 240/5832 249/110 206 317 400 280/464 5003   
   SEEN-BY: 282/1038 288/100 292/8125 301/1 310/31 317/3 322/757 342/200   
   SEEN-BY: 396/45 423/120 460/58 633/280 770/1   
   PATH: 280/464 229/101 426