REPLY: 3:633/280 697bfa41   
   MSGID: 2:221/1.1 697c6a0e   
   PID: GED+W64 1.1.5-b20250409   
   CHRS: CP437 2   
   TZUTC: 0200   
   TID: hpt/w64-mvcdll 1.9 2024-03-02   
   Hi Stephen.   
      
   30 Jan 26 10:55:02, you wrote to me:   
      
    TK>> I know that PyGate will adjust the message count by one every time   
    TK>> it sends a message to news server but it is possible "own" messages   
    TK>> to come back other route.   
    SW>   
    SW> INN should take care of that,   
      
   Nope. I'm talking about the situation when I send a message from fido to news.   
   It has a MSGID:   
      
    @MSGID: 2:221/1 697c6658   
      
   It appears at INN like this:   
      
    Message-ID: <697c6658.2.221.1@fidonet.fi>   
    X-FTN-MSGID: 2:221/1 697c6658   
      
   But when I fetch the same message from INN to fido, it has a MSGID like this:   
      
    @MSGID: <697c6658.2.221.1@fidonet.fi> d604975d   
      
   So it wont be detected as a dupe.   
      
   The original fido MSGID is saved in the nntp-message. Maybe that should be   
   used as a fido MSGID if it exists?   
      
   'Tommi   
      
   ---   
    * Origin: Point One (2:221/1.1)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 305 153/757   
   SEEN-BY: 153/7715 154/10 30 110 201/0 203/0 218/700 221/1 6 226/30   
   SEEN-BY: 227/114 229/110 112 134 206 300 307 317 400 426 428 470 616   
   SEEN-BY: 229/664 700 705 240/1120 5832 263/1 266/512 280/464 5003   
   SEEN-BY: 291/111 292/854 8125 301/1 310/31 320/219 322/757 341/66   
   SEEN-BY: 341/234 342/200 396/45 423/81 120 460/58 633/267 280 384   
   SEEN-BY: 633/410 414 418 420 422 509 2744 712/848 770/1 902/26 5020/400   
   SEEN-BY: 5075/35   
   PATH: 221/1 280/464 633/280 229/426