getting this error now when pxw connects to my fido upink:

Binkp: receive error in Phase 6 err=10060

Reported to Andrew and Santronics. Expecting an answer back from their
AI.
--- Platinum Xpress/Win/WINServer v10.0b40
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

posting this here for comment..

-----Original Message-----
From: listadmin-winserver@winserver.com
<listadmin-winserver@winserver.com> On Behalf Of wsa
Sent: Monday, June 1, 2026 2:25 PM
To: WINServer@winserver.com
Subject: RE: [WINServer] Re: connection issue.

Robert ƒ?"

Good data point, and it fits the pattern. Internet Rex is listed in the compatibility table as a confirmed working mailer with no known issues,
so if IR completes the session cleanly where binkd (or whatever
1:320/219 is running) times out, that narrows it considerably.

The most likely explanation: the remote mailer is completing its side of
the EOB exchange and then dropping the TCP connection without a proper
FIN ƒ?" just going silent. IR may handle that gracefully (detecting the
silent close and moving on), while PX sits waiting for the close frame
until the socket timeout fires. The result looks like a PX hang but the
root cause is on the remote side.

That said, it's worth checking whether PX could be more aggressive about recognizing a completed session and not waiting indefinitely after both
EOBs are exchanged. If both sides have sent and received EOB and all
files are accounted for, there's arguably no reason to wait on the
socket ƒ?" a short timeout or an explicit close-after-EOB path might be
cleaner than relying on the remote to close first.

**For the dev record:** if you can confirm the mailer at 1:320/219 and
grab their session log for the same timestamp, that would be useful.
Knowing whether this is specific to binkd-115 (which already has known
quirks in the compat table) or a different mailer would help scope any
fix.


going to send this out with internet rex.

--- Platinum Xpress/Win/WINServer v10.0b40
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

posting this here for comment.

posting this here for comment..----Original Message-----
From: listadmin-winserver@winserver.com
<listadmin-winserver@winserver.com> On Behalf Of wsa
Sent: Monday, June 1, 2026 2:25 PM
To: WINServer@winserver.com
Subject: RE: [WINServer] Re: connection issue.obert ƒ?"ood data point,
and it fits the pattern. Internet Rex is listed in the
compatibility table as a confirmed working mailer with no known issues,
so if IR completes the session cleanly where binkd (or whatever
1:320/219 is running) times out, that narrows it considerably.he most
likely explanation: the remote mailer is completing its side of
the EOB exchange and then dropping the TCP connection without a proper
FIN ƒ?" just going silent. IR may handle that gracefully (detecting the
silent close and moving on), while PX sits waiting for the close frame
until the socket timeout fires. The result looks like a PX hang but the
root cause is on the remote side.hat said, it's worth checking whether
PX could be more aggressive about
recognizing a completed session and not waiting indefinitely after both
EOBs are exchanged. If both sides have sent and received EOB and all
files are accounted for, there's arguably no reason to wait on the
socket ƒ?" a short timeout or an explicit close-after-EOB path might be cleaner than relying on the remote to close first.*For the dev
record:** if you can confirm the mailer at 1:320/219 and
grab their session log for the same timestamp, that would be useful.
Knowing whether this is specific to binkd-115 (which already has known
quirks in the compat table) or a different mailer would help scope any
going to send this out with internet rex.

... I like your approach, now let's see your departure
--- Wildcat! v10.0.500.1 (May 2 2026), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

Hey Robert!

On Mon, 01 Jun 2026 14:28:50 -0400, you wrote:

Good data point, and it fits the pattern. Internet Rex is listed in the compatibility table as a confirmed working mailer with no known issues,
so if IR completes the session cleanly where binkd (or whatever
1:320/219 is running) times out, that narrows it considerably.

FYI, wherever they got "Internet Rex is listed in the compatibility table as a confirmed working mailer with no known issues", they were given the wrong information.

You can ask just about any mailer developer these days how they've had to work around IREX's bad binkp implementation. IIRC, it may have been something to do with stating it was binkp 1.1 compliant, when it really isn't. But, I am fairly certain it was something in the lines of how the session is ended, as seemed to be what was being discussed in whatever it was that I replied to. ;)

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20260425
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

FYI, wherever they got "Internet Rex is listed in the compatibility table as
confirmed working mailer with no known issues", they were given the wrong information.

yeah probably from logs a couple us us irex users submitted on request
that their ai analyzed.

... Give a man an inch, and he thinks he's a ruler.
--- Wildcat! v10.0.500.1 (May 2 2026), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

FYI, wherever they got "Internet Rex is listed in the compatibility table as a confirmed working mailer with no known issues", they were given the wrong information.

You can ask just about any mailer developer these days how they've had to work around IREX's bad binkp implementation. IIRC, it may have been something to do with stating it was binkp 1.1 compliant, when it really isn't. But, I am fairly certain it was something in the lines of how the session is ended, as seemed to be what was being discussed in whatever it was that I replied to. ;)

I suspect that its biggest problem is that IREX is old and no longer updated. If it is possible in the situation in question, I would suggest using binkd instead.


--- ScorpioWeb v0.32a (Linux/x86_64)
* Origin: Project Scorpio TEST (1:2320/106)

Hello Nick!

01 Jun 26 19:10, you wrote to Robert Wolfe:

FYI, wherever they got "Internet Rex is listed in the compatibility
table as a confirmed working mailer with no known issues", they were
given the wrong information.

You can ask just about any mailer developer these days how they've had
to work around IREX's bad binkp implementation. IIRC, it may have been something to do with stating it was binkp 1.1 compliant, when it
really isn't. But, I am fairly certain it was something in the lines
of how the session is ended, as seemed to be what was being discussed
in whatever it was that I replied to. ;)

As a developer who maintains a BinkP compatible mailer (mbcico), I can definitely confirm that IRex has multiple issues in this regard. In fact, when mbcico connects to IRex, it automatically falls back to binkp/1.0 to avoid most of the issues.

Andrew

---
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

On 6/3/2026 6:45 AM, Andrew Leary wrote to Nick Boel:

As a developer who maintains a BinkP compatible mailer (mbcico), I can definitely confirm that IRex has multiple issues in this regard. In fact, when mbcico connects to IRex, it automatically falls back to binkp/1.0 to avoid most of the issues.

FYI, the current betas include a config file called binkp-compat.ini with this in it:

; -----------------------------------------------------------------------
; Internet Rex - VER: Internet Rex 2.31 Win32 (binkp/1.1)
; No longer actively maintained. Seen on Terry's hub (3:712 net).
; CRAM-MD5 behavior unknown. Conservative default maintained.
; ----------------------------------------------------------------------- [internet rex]
CramMD5=0

; -----------------------------------------------------------------------
; mbcico - VER: mbcico/1.1.7/Linux-x86_64 binkp/1.1
; Unix FTN mailer. CRAM-MD5 behavior unknown.
; Conservative default maintained.
; ----------------------------------------------------------------------- [mbcico]
CramMD5=0


--- Platinum Xpress/Win/WINServer v10.0b40
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

Hello Robert!

03 Jun 26 13:15, you wrote to me:

FYI, the current betas include a config file called binkp-compat.ini
with this in it:

;
----------------------------------------------------------------------
-
; Internet Rex - VER: Internet Rex 2.31 Win32 (binkp/1.1)
; No longer actively maintained. Seen on Terry's hub (3:712 net).
; CRAM-MD5 behavior unknown. Conservative default maintained.
;
----------------------------------------------------------------------
- [internet rex] CramMD5=0

;
----------------------------------------------------------------------
-
; mbcico - VER: mbcico/1.1.7/Linux-x86_64 binkp/1.1
; Unix FTN mailer. CRAM-MD5 behavior unknown.
; Conservative default maintained.
;
----------------------------------------------------------------------
- [mbcico] CramMD5=0

Completely unnecessary. Both IRex and mbcico support CRAM-MD5 authentication.

Andrew

---
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Hello Andrew!

03 Jun 26 06:45, you wrote to Nick Boel:

As a developer who maintains a BinkP compatible mailer (mbcico), I can
definitely confirm that IRex has multiple issues in this regard. In fact, when mbcico connects to IRex, it automatically falls back to binkp/1.0 to avoid most of the issues.

Where can anybody get hold of mbcico?

Andrew

---
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Javier


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

--------------------------------------------------------------------- -
; Internet Rex - VER: Internet Rex 2.31 Win32 (binkp/1.1)
; No longer actively maintained. Seen on Terry's hub (3:712 net).
; CRAM-MD5 behavior unknown. Conservative default maintained.
; --------------------------------------------------------------------- - [internet rex] CramMD5=0

; --------------------------------------------------------------------- -
; mbcico - VER: mbcico/1.1.7/Linux-x86_64 binkp/1.1
; Unix FTN mailer. CRAM-MD5 behavior unknown.
; Conservative default maintained.
; --------------------------------------------------------------------- - [mbcico] CramMD5=0

Completely unnecessary. Both IRex and mbcico support CRAM-MD5 authentication.

thought so. Passed this along via pxnet. curious to see what happens.

... Operator, give me the number for 911

--- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
* Origin: Over the Brink - Grand Island NY - brinkbbs.org (1:261/20)

Hello Andrew!

03 Jun 26 06:45, you wrote to Nick Boel:

As a developer who maintains a BinkP compatible mailer (mbcico), I ca
definitely confirm that IRex has multiple issues in this regard. In fact, when mbcico connects to IRex, it automatically falls back to binkp/1.0 to avoid most of the issues.

Where can anybody get hold of mbcico?

It is part of the mbse BBS package.

... There are three kinds of people: Those who can count, and those who can't

--- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
* Origin: Over the Brink - Grand Island NY - brinkbbs.org (1:261/20)

Hello Javier!

05 Jun 26 12:56, you wrote to me:

As a developer who maintains a BinkP compatible mailer (mbcico),
I can
definitely confirm that IRex has multiple issues in this regard.
In fact, when mbcico connects to IRex, it automatically falls
back to
binkp/1.0 to avoid most of the issues.

Where can anybody get hold of mbcico?

It's included in the free MBSE BBS package. https://sourceforge.net/projects/mbsebbs

The files section has the 1.1.7 release version. The current development version is 1.1.7.2 which is available from the Git repository on the SourceForge page.

Andrew

---
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)