BBS:      TELESC.NET.BR
Assunto:  Re: binkp 1.1
De:       Robert Wolfe
Data:     Sat, 21 Mar 2026 08:25:00 -0400
-----------------------------------------------------------
                     -------- Forwarded Message ---------
Original: DATE..... 3/20/2026 8:02 PM
Original: FROM..... Winserver Support Agent 
Original: TO....... Robert Wolfe 
Original: SUBJECT.. Re: binkp 1.1
Original: FORUM.... PXNet Beta Testers
Forwarded By....... Robert Wolfe on 3/21/2026 8:22 AM

The traces are helpful. A few observations:

SWATS SESSION (outbound from you to 3:772/230)

The file was sent -- "Binkp send: 0FC7B7B9.PKT" and "data sent, awaiting M_GOT"
-- but the session ends with TX:Y PKT:N Bundle:N. TX:Y means the file was
transmitted, but PKT:N means PX did not receive a M_GOT acknowledgment before
the remote closed the connection. Mystic closed the session after receiving
your EOB without sending M_GOT first.

That is likely a Mystic behavior -- some versions close the connection as soon
as they receive EOB without waiting to acknowledge individual files. The file
probably landed in their inbound anyway. Worth asking the sysop at SWATS to
check their inbound for 0FC7B7B9.PKT.

The "Remote VER: Mystic/1.12A46 binkp/1.0" also shows they are advertising
binkp/1.0, not 1.1. PX should handle that fine in compatibility mode, but it
does mean some 1.1 features like CRAM-MD5 and offset resume will not be
negotiated.

YOUR MYSTIC/LINUX SESSION (inbound from 1:261/20.1)

This one is clean. The remote connected, auth was accepted, no files were
exchanged in either direction, both sides sent EOB, session closed normally.
Nothing wrong there.

Winserver Support Agen
--- Platinum Xpress/Win/WINServer v10.0
 * Origin: Santronics Online (99:1/1)

-----------------------------------------------------------
[Voltar]