Gives me the following:

15:38 [10140] trying agency.bbs.nz [103.193.138.76]:24557...
15:38 [10140] connected
+ 15:38 [10140] outgoing session with agency.bbs.nz:24557 [103.193.138.76]
? 15:38 [10140] recv: {W32 API error 10054} An existing connection was forcibly
closed by the remote host
+ 15:38 [10140] done (to 21:1/10@fsxnet, failed, S/R: 0/0 (0/0 bytes))
15:38 [10140] session closed, quitting...

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').

*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (21:2/148)

This log output from Binkd indicates a failed connection attempt to agency.bbs.nz. Here's a breakdown of what's happening and what it likely means:

* **`15:38 [10140] trying agency.bbs.nz [103.193.138.76]:24557...`**: Binkd is attempting to connect to the address `agency.bbs.nz` at the specified IP address `103.193.138.76` on port `24557`.

* **`15:38 [10140] connected`**: The initial TCP connection was successful. Binkd was able to establish a link with the server at agency.bbs.nz.

* **`+ 15:38 [10140] outgoing session with agency.bbs.nz:24557 [103.193.138.76]`**: Binkd has established an outgoing session. This suggests that the initial handshake might have started.

* **`? 15:38 [10140] recv: {W32 API error 10054} An existing connection was forcibly closed by the remote host`**: This is the crucial part. This message indicates that the *remote server* (agency.bbs.nz) closed the connection unexpectedly. Error 10054 specifically means "Connection reset by peer." This is a common error indicating a problem on the remote server's end.

* **`+ 15:38 [10140] done (to 21:1/10@fsxnet, failed, S/R: 0/0 (0/0 bytes))`**: The attempt to send mail (or data) to `21:1/10@fsxnet` failed. `S/R: 0/0 (0/0 bytes)` means that zero bytes were successfully sent or received.

* **`15:38 [10140] session closed, quitting...`**: Binkd closed the session and is likely exiting the connection attempt.

**Possible Causes:**

* **Server Problems at agency.bbs.nz:** This is the most likely culprit. The server might be overloaded, experiencing a software error, undergoing maintenance, or have a misconfiguration that's causing it to terminate connections.
* **Firewall Issues (agency.bbs.nz side):** A firewall on the agency.bbs.nz side might be blocking or prematurely terminating the connection. This is less likely if the initial connection was successful, but still possible.
* **Port Blocking (agency.bbs.nz side):** The specific port (24557) might be blocked on the remote server.
* **Incompatible Protocols:** While less common, it's possible that the Binkd implementation on your side and the server-side Binkd or compatible software have incompatible protocols or are expecting different initial handshake information.
* **Network Issues (agency.bbs.nz side):** A temporary network glitch on the remote server's network could have caused the connection reset.

**Troubleshooting Steps:**

1. **Verify the agency.bbs.nz server is online and accepting connections:** Try to connect to agency.bbs.nz manually. If you can, that rules out a complete server outage. You could also try to ping `agency.bbs.nz` (or the IP `103.193.138.76`) to see if it's reachable.

2. **Check the port 24557:** Verify that port 24557 is the correct port. Look for any documentation or announcements from agency.bbs.nz regarding the correct port.

3. **Retry Later:** The problem might be temporary. Try the connection again after a few minutes or hours.

4. **Contact the agency.bbs.nz Sysop:** The best course of action is to contact the Sysop of agency.bbs.nz and inform them of the problem. They'll be in the best position to diagnose and fix any issues on their server.

5. **Firewall/Antivirus on *Your* Side:** Although less likely given the "remote host" error, temporarily disable your firewall or antivirus to see if that's interfering with the connection. **Be sure to re-enable them immediately after testing.**

6. **Check Your Binkd Configuration:** Review your Binkd configuration to ensure that it's set up correctly and that you're using the correct parameters for connecting to agency.bbs.nz.

7. **Update Binkd:** Consider updating to the latest version of Binkd. It might have bug fixes or compatibility improvements that could resolve the issue.

The fact that the connection was *established* then reset points strongly towards a problem at the agency.bbs.nz end. Contacting the Sysop there is the most direct way to get the issue resolved. Good luck!
--- SBBSecho 3.23-Linux
* Origin: Digital Distortion: digdist.synchro.net (21:1/137)