REPLY: 2:221/1.1 697c6a0e   
   MSGID: 3:633/280 697d6429   
   CHRS: CP437 2   
   TZUTC: 1100   
   TID: hpt/lnx 1.9 2024-03-02   
      
   Hello Tommi!   
      
   30 Jan 26 10:07, you wrote to me:   
      
    TK> Nope. I'm talking about the situation when I send a message from fido   
    TK> to news. It has a MSGID:   
   [...]   
    TK> The original fido MSGID is saved in the nntp-message. Maybe that   
    TK> should be used as a fido MSGID if it exists?   
      
      
   ### Version 1.5.7 (January 30, 2026)   
      
   When converting NNTP to FidoNet, PyGate now checks for the X-FTN-MSGID header   
   first. If present (indicating the   
   message originated from FidoNet), it uses the original MSGID instead of   
   generating a new one. This allows   
   FidoNet duplicate detection to work correctly and prevents message loops.   
      
   The flow is now:   
   1. FidoNet -> NNTP: MSGID: 2:221/1 697c6658 -> X-FTN-MSGID: 2:221/1 697c6658   
   2. NNTP -> FidoNet: X-FTN-MSGID: 2:221/1 697c6658 -> MSGID: 2:221/1 697c6658   
   (same!)   
      
   Duplicate detection will now recognize it as the same message.   
      
      
      
      
   Stephen   
      
      
   --- GoldED+/LNX 1.1.5-b20250409   
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)   
   SEEN-BY: 105/81 106/201 128/187 129/14 305 153/7715 154/110 218/700   
   SEEN-BY: 226/30 227/114 229/110 112 134 206 300 307 317 400 426 428   
   SEEN-BY: 229/470 616 664 700 705 266/512 280/464 291/111 292/854 320/219   
   SEEN-BY: 322/757 342/200 396/45 460/58 633/267 280 384 410 414 418   
   SEEN-BY: 633/420 422 509 2744 712/848 770/1 902/26 5075/35   
   PATH: 633/280 229/426