MSGID: 2:221/1.58@fidonet ef51437e   
   REPLY: 2:280/464 6072d98e   
   PID: OpenXP/5.0.49 (Win32)   
   CHRS: ASCII 1   
   TZUTC: -0400   
   Hello Wilfred!   
      
   ** On Sunday 11.04.21 - 13:05, you wrote to me:   
      
    AA>> For msgid purposes why not just generate a 6 to 9   
    AA>> character hash based on the content of the message?  That   
    AA>> would ALWAYS be unique and never repeat for a l-o-n-g   
    AA>> time.   
      
    WvV> There are those moderator messages that stay the same for   
    WvV> ages...   
      
   Not if the hash includes the entire msg and the date posted.   
      
    AA>> The current approach for msgid has been to have serial number.   
    AA>> But why can't it be a simple hash?   
      
    WvV> A good secure hash, needs a lot of cpu to be calculated.   
      
   Even a simple random num generator could work.  For example, the     
   following took less than a sec to produce:   
      
   H:\myutils>rando2   
   lfz$bkmcmmg36ye@jll1xpieaats   
      
   H:\myutils>rando2   
   7zc3i6btkuwyax2tpbh814$392c   
      
   H:\myutils>rando2   
   g~zys4kmp$9s0h@4jxp169j##8eskb   
      
   H:\myutils>rando2   
   p67v3h$vy3pdqo9t6rueljbv0qf   
      
   H:\myutils>rando2   
   m0s#trrv~bxjsg0f$mo29q8g$6699l   
      
   H:\myutils>rando2   
   $3111un9@je2dey$jwdehlzk01g   
      
   H:\myutils>rando2   
   q5ur8jolf#@4227~#73g99@lpy0dh@   
      
   H:\myutils>rando2   
   u4iouevy9yrh6~1it~2z$asr5y@   
      
   H:\myutils>rando2   
   cu1#0wqju$11~1lu#gklu52o9#k3v   
      
   So..  why couldn't something like that be implemented? And,     
   instead of limiting the "serialno" to hex chars, use the entire     
   alphabet and throw in some extra chars (# $ ~ % & *)   
      
    AA>> Synchronet systems have come up with another unique   
    AA>> approach to the MSGID line which seems to cooperate with   
    AA>> existing systems quite well.   
      
    WvV> It isn't according to the standard, which might cause some   
    WvV> problems on other systems.   
      
   I thought it was copacetic with other systems. On which ones     
   does it break?   
      
    WvV> And I think it went like this: They miss used the MSGID to   
    WvV> store some internal information for their messagebase, and   
    WvV> came up with an excuse afterwards, when it was difficult   
    WvV> to correct.   
      
   I remember something about the MSGID being referred to as a two-    
   part string with "origaddr" + "serialno", where "origaddr" is     
   intended to be a qualified "address of the originating system".   
      
   Most systems keep it simple:   
      
    z:f/n.p hhhhhhhh   
      
   And some others look like:   
      
    n.areaname@z:f/n.p hhhhhhhh   
      
   --   
     ../|ug   
      
   --- OpenXP 5.0.49   
    * Origin: Mobile? ASIAN_LINK https://preview.tinyurl.com/y6rwskq (2:221/1.58)   
   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/1 6 360 226/30 227/114 229/101 424 426 452   
   SEEN-BY: 229/664 700 1016 1017 230/0 240/5832 249/110 206 317 400   
   SEEN-BY: 280/464 5003 282/1038 288/100 292/8125 301/1 310/31 317/3   
   SEEN-BY: 322/757 342/200 396/45 423/81 120 460/58 633/280 770/1   
   PATH: 221/1 280/464 229/101 426