Subj : Re: Docker Chat To : Warpslide From : poindexter FORTRAN Date : Fri Jul 26 2024 07:08:00 -=> Warpslide wrote to poindexter FORTRAN <=- Wa> This message ended up in my DUPE base here, presumably due to the Wa> duplicated headers. I'm assuming the message looks fine on your end? Wa> I only see this behaviour with tqwNet, I'm wondering if maybe tqw's hub Wa> 3 has some message corruption? That's odd, my first thought was that it was a duplicate QWK reply packet upload, but I have dupe detection turned on my side and it usually catches those. This message was entered directly on my system using the FSE. Looking at my echo log, I see this: 2024-07-25 17:33:34 Exporting tqw_sug message #1 from poindexter FORTRAN to All in area: TQW_SUG 2024-07-25 17:33:34 Creating outbound packet from 1337:3/178 to 1337:3/100: c:\sbbs\temp\sbbsecho\66a2eede.pkt 2024-07-25 17:33:34 New packet (type 2+) created for linked-node: 1337:3/100 2024-07-25 17:33:34 Adding TQW_SUG message from poindexter FORTRAN (1337:3/178) to packet for 1337:3/100: c:\sbbs\temp\sbbsecho\66a2eede.pkt 2024-07-25 17:33:34 Added TQW_SUG message from poindexter FORTRAN (1337:3/178) to packets for 1 links (exceptions: none) 2024-07-25 17:33:34 Exporting tqw_sug message #2 from poindexter FORTRAN to All in area: TQW_SUG 2024-07-25 17:33:34 Appending outbound packet from 1337:3/178 to 1337:3/100: c:\sbbs\temp\sbbsecho\66a2eede.pkt 2024-07-25 17:33:34 Adding TQW_SUG message from poindexter FORTRAN (1337:3/178) to packet for 1337:3/100: c:\sbbs\temp\sbbsecho\66a2eede.pkt 2024-07-25 17:33:34 Added TQW_SUG message from poindexter FORTRAN (1337:3/178) to packets for 1 links (exceptions: none) 2024-07-25 17:33:34 Exported: 2 msgs tqw_sug -> TQW_SUG 2024-07-25 17:33:34 Exported: 2 msgs total 2024-07-25 17:33:34 Finalizing outbound packet from 1337:3/178 to 1337:3/100: c:\sbbs\ It looks like I may have sent out duplicates with duplicate headers? I'll forward this to Rob. --- MultiMail/Win v0.52 * Origin: realitycheckBBS.org -- information is power. (1337:3/178) .