Most recently, when I send a test message and run Synchronet's BINKOUT event, it looks like it connects to the correct address & port, and then immediately afterwards, it tries to connect to the incorrect one noted above.
This past weekend, I got my BBS (Digital Distortion) set up on FSXNet. I'm using Synchronet's BinkIt mailer. I've been seeing an issue.. I've sent a few test messages, and for some packets, it seems it's able to connect to the hub successfully (with the correct address and port), but it also tries to connect to f100.n1.z27.example.com:24554, which is the wrong address and port for the hub. I'm not sure where it's getting that. Are there any other Synchronet sysops on FSXnet who have seen that issue?
Most recently, when I send a test message and run Synchronet's BINKOUT event, it looks like it connects to the correct address & port, and then immediately afterwards, it tries to connect to the incorrect one noted above.
Do you have a stale .*LO file in your outbound? Might be that there's a file left over from when you were configuring binkit?
It looks like your mailer is looking for a node in zone 27.
I suspect a wrong *.?LO as Poindexter suggested.
I was using SBBS and BinkIT a while back (still do). BinkIT is my
favorite of all the mailer we have available today.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 292 |
Nodes: | 16 (2 / 14) |
Uptime: | 181:53:29 |
Calls: | 6,616 |
Calls today: | 3 |
Files: | 12,165 |
Messages: | 5,314,391 |