TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 f3091652   
   REPLY: 1:249/400 03747076   
   TZUTC: -0500   
    St> Yeah third party tossers would certainly throw a monkey wrench   
    St> regardless of  what Mystic does. Without a stored MSGID you could   
    St> possibly use other fields to generate a consistent NNTP message ID on   
    St> the fly but then the question would be what fields are sufficiently   
    St> static and up to the task? Some combination of datewritten + sendername   
    St> + the message base name?   
      
   In the case of the article ID it has to be more than that, since the article   
   ID needs to be able to consistantly resolve to a message.  A date written and   
   name would be too vague.  Sometimes when messages are processed in batch it'll   
   be possible for two messages to have the same datestamp from the same person.   
      
   Mystic uses a unique identifier and some hash values along with the primary   
   key of the message base to generate the article ID.  This way it can figure   
   out the base and then more quickly perform a lookup using the hash first to   
   limit the result set (before loading the full message to check the MSGID for a   
   match).   
      
   The NNTP server can create MSGID on the fly if they are missing so it will   
   always generate an article ID (which I have enabled now).  My concern with   
   doing that was there will be added risk of message base corruption if the NNTP   
   server needs to do massive updates to generate unique IDs at the same time   
   something like message tossing is happening.   
      
   In order to reduce the amount of times the NNTP server needs to generate   
   MSGIDs I went back and changed things (in the next build) so that Mystic will   
   always generate MSGID even if its a local, newsgroup, or QWK networked base...   
      
   The only remaining thing would be to add MSGID on the fly when tossing   
   messages from QWK and Fido networks.  I've added it into QWK tossing now too   
   but for Fido I am a little hesistant to do so.  Technically adding a missing   
   MSGID would be changing message content and anytime Mystic's tosser has the   
   option to do that there is a subset of Fido people who have huge meltdowns   
   over it.    
      
   --- Mystic BBS v1.12 A47 2021/12/06 (Windows/64)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 90/1 103/705 105/81 120/340 616 123/10 131 124/5016   
   SEEN-BY: 129/215 305 153/757 154/10 30 40 50 700 203/0 220/80 90 221/0   
   SEEN-BY: 221/6 226/18 30 227/114 201 229/310 424 426 428 452 550 664   
   SEEN-BY: 229/700 240/1120 5411 5824 5832 5853 5890 6309 249/206 307   
   SEEN-BY: 249/317 400 280/464 5003 282/1038 292/854 8125 301/1 317/3   
   SEEN-BY: 320/219 322/757 341/234 342/200 396/45 633/280 770/1 2452/250   
   SEEN-BY: 2454/119 3634/12   
   PATH: 129/215 154/10 280/464 240/5832 229/426