Subj : error To : All From : Robert Wolfe Date : Mon Jun 01 2026 02:28 pm posting this here for comment.. -----Original Message----- From: 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) .