From: nospam.g00r00@f215.n129.z1.fidonet.org   
      
    St> Mystic at present uses the post number in the message area as the NNTP   
    St> message ID so for example every area with posts in it will each have a   
    St> message with ID 1.   
      
   I'll get you caught up with the latest happenings :)   
      
   Mystic has unique article IDs across all message bases and messages and the   
   server is capable of properly responding to them but its disabled.  For example   
   here is a HEAD command sent to the NTTP server on my test system with this   
   system enabled:   
      
   head <2.7cb38be1.193799f9@mystictestdomain.com>   
      
   And here is the response:   
      
   221 1 <2.7cb38be1.193799f9@mystictestdomain.com> article retrieved - head   
   follows   
   From: g00r00   
   Newsgroups: local.test   
   Subject: msg #0   
   Date: Thu, 13 Aug 2020 18:21:00 GMT   
   Message-ID: <2.7cb38be1.193799f9@mystictestdomain.com>   
      
   The problem I face before I can enable it is this:  JAM message bases do not   
   have any sort of message serialization other than the message number which can   
   change (making it not useful).  Because of this, every message must have a   
   MSGID (even local messages) for this system to work.   
      
   If there is no MSGID, then Mystic NNTP cannot generate a unique Article-ID and   
   by RFC standard it must respond with a <0> for the ID.  This would probably be   
   even worse than the current system.   
      
   The holdup for me to enable this is that I need to ensure every message has a   
   MSGID.  The first step was to build the pack message base function in MUTIL to   
   automatically generate a MSGID for any message that doesn't have one when   
   packing.  I did finish this part.   
      
   The next would be to make sure any message posted in Mystic has a MSGID even if   
   its a QWK network or local post and this part isn't done.  After that I would   
   need to make sure any posts from NNTP, QWK packets, MUTIL Posts etc also   
   generate a MSGID even if local or non-FTN.  The final step would be that the   
   tossers importing into Mystic (MUTIL and QWKPOLL) must also generate a MSGID on   
   the fly for any message sourced outside of your BBS that is missing one.   
      
   Then there is also the problem then with those who may use third party tossers   
   or utilities to post messages since they might not be able to guarantee that   
   every message will have a MSGID.   
      
   Long story longer, that is the challenge: Making sure MSGID exists on every   
   message on your BBS.  The limitation isn't on the NNTP side of things at this   
   point.  I can make sure Mystic does it but for those who use third party   
   utilities that could be problematic.   
      
   I am not sure how various newsreaders treat messages without an article ID (ie   
   an article ID of <0>).   
      
   ... Old computers make great boat anchors   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)