I've tried to reproduce your issue by setting up the exact situation where
IREX polls MIS2 and receives two packets of the same filename from different networks. It works just fine. I still cannot get anything to fail with IREX.

I've put a new debug .EXE in the prealpha place again. This doesn't have any changes that should fix anything, but it has even MORE debug logging that might help me find something. If you are willing, please try a connection again with the problem node and submit the logs again.

---------- Mystic v1.12 A36 2017/11/11 Sat, Nov 11 2017 (loglevel 3)
+ 13:14:51 BINKP > Connect on slot 1/5
+ 13:14:51 BINKP 1-Address 127.0.0.1
+ 13:14:52 BINKP 1-Info NDL
+ 13:14:52 BINKP 1-Info TIME 2017/11/11 13:14:52 -5:00
+ 13:14:52 BINKP 1-Mailer Internet Rex 2.29 Win32 (binkp/1.1)
+ 13:14:52 BINKP 1-Authenticating 55:5/3@testnet by CRAM-MD5
+ 13:14:52 BINKP 1-Queued 1 files for 55:5/3@testnet
+ 13:14:52 BINKP 1-Queued 1 files for 100:1/2@testnet2
+ 13:14:52 BINKP 1-Sending:
\testbbs\bbs1\echomail\out\testnet\0000fffe.sa1 (2,893 bytes)
+ 13:14:52 BINKP 1-Sending: \testbbs\bbs1\echomail\out\testnet2.064\0000fffe.sa1 (2,874 bytes)
+ 13:14:53 BINKP 1-Session ended (2 sent, 0 rcvd, 0 skip)

--- Mystic BBS v1.12 A36 2017/11/10 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/11/17, g00r00 said the following...

I've tried to reproduce your issue by setting up the exact situation
where IREX polls MIS2 and receives two packets of the same filename from different networks. It works just fine. I still cannot get anything to fail with IREX.

I've put a new debug .EXE in the prealpha place again. This doesn't
have any changes that should fix anything, but it has even MORE debug logging that might help me find something. If you are willing, please
try a connection again with the problem node and submit the logs again.

---------- Mystic v1.12 A36 2017/11/11 Sat, Nov 11 2017 (loglevel 3)

Honest not sure why folks are still using IREX when mystic is free and can be used for the same purpose. But in saying most folks who use IREX do not have the knowledge to properly set it up correctly either. :/

Cheers!
Pequito

--- Mystic BBS v1.12 A36 2017/11/09 (Linux/32)
* Origin: Twinkle BBS # (21:1/126)

On 11/11/17, g00r00 said the following...

I've put a new debug .EXE in the prealpha place again. This doesn't
have any changes that should fix anything, but it has even MORE debug logging that might help me find something. If you are willing, please
try a connection again with the problem node and submit the logs again. ---------- Mystic v1.12 A36 2017/11/11 Sat, Nov 11 2017 (loglevel 3)

ok, I grabbed the new debug .EXE again the even more debug logging makes them huge.. so I just zipped then (fluph_a36_debug.zip) and emailed it to you.
irex is still spitting out a binkp error message with each connection.
Anyway, the irex here is the same one used a few years back with mystic only now I use it as a frontend for a Reneagde point system. With FE as the tosser

Internet Rex version 2.31 (Windows 32-bit
(C) Copyright 1997-2005 Khan Software
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
°°ÉÍ[þ]µ Front end mailer setup ÆÍÍÍÍÍÍÍ
°°º
°°º Mailer type FrontDoor 2.25+
°°º Netmail directory d:\irex\netmail
°°º Type of .MSGs Opus 1.02
°°º Save inbound mail in .MSGs
°°º Inbound Rex uses Secure inbound
°°º Nodelist directory d:\gold7\
°°º Inbound directory d:\irex\in\
°°º Secure inbound d:\irex\in\
°°º Semaphore directory d:\irex\sem\
°°º Semaphores
°°º FILQUEUE.FD path d:\fd\

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: flupH | fluph.darktech.org (21:1/105)

ok, I grabbed the new debug .EXE again the even more debug logging makes them huge.. so I just zipped then (fluph_a36_debug.zip) and emailed it
to you. irex is still spitting out a binkp error message with each

Thank you very much. Unfortunately that didn't show anything that the other logs haven't already shown.

I made yet another round of mis2 and fidopoll .exe files in the same place. This one won't have as much logging as the last one, but there are some new logging areas that might expose something.

I'm sorry this has been such a pain in the ass its just very hard to fix something that I can't reproduce. :(

--- Mystic BBS v1.12 A36 2017/11/12 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/12/17, g00r00 said the following...

I made yet another round of mis2 and fidopoll .exe files in the same place. This one won't have as much logging as the last one, but there
are some new logging areas that might expose something.

ok I got the new msi2 and did a poll for waiting mail again. email logs to U

I'm sorry this has been such a pain in the ass its just very hard to fix something that I can't reproduce. :(

No worries, I still have a old backup of taurus from 2011 that I might dig
out. I'm also thinking about just sending you my D:\irex zipped up. You might see something that stands out. I did use it with mystic & FE between
2011-2015 I think it was before I went just native mystic.

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: flupH | fluph.darktech.org (21:1/105)

On 11/12/17, Skuz pondered and said...

between 2011-2015 I think it was before I went just native mystic.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I have visions of you running around in a grass skirt right now :)

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 11/13/17, Avon said the following...

On 11/12/17, Skuz pondered and said...

between 2011-2015 I think it was before I went just native mystic.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I have visions of you running around in a grass skirt right now :)

That would make a most excellent youtube video, stay turned ,.the natives are restless (:

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: flupH | fluph.darktech.org (21:1/105)