Subj : Issue with BinkD and outbound attempts. To : Eric Renfro From : Oli Date : Fri Mar 27 2020 08:28 am ER> So, Lately I've noticed that my BinkD, which is configured with 2 domains now, instead of just one. ER> ER> domain fidonet /bbs/mailer/outbound 1 ER> domain gatornet /bbs/mailer/outbound 1 ER> ER> This is causing some interesting issues that, when binkd tries to "call" Z:N/NNN, it first tries to call Z:N/NNN@fidonet, and if that, for any reason fails, it tries to callout to Z:N/NNN@gatornet, which fails IF it connects because the remote end doesn't have that AKA as @gatornet. ER> ER> I was having this issue recently, and I'm not really sure how to... Not cause that to happen because, I see it still happening, however, neither @case connects, but in one case (Tommi knows about this, since he was being called to many times over), one failed, one worked, to resolve, just not establish session. heh ER> ER> So, how can I... Solve this issue properly? This is a pure binkd+huskytools HUB server, no BBS, mail only setup. When I tested hpt last year I had the same problem. I didn't like hpt anyway and switched to Crashmail and 5D again. I might be missing something, but for me this behaviour makes sense. There is a .flo file in the outbound of fidonet _and_ gatornet (both domains use the same outbound config) and of course binkd is trying both networks. What is missing in binkd is a way to map zone numbers to domains. You could try to put the domain in the node line, like node 1:2/3@fidonet ... I haven't tried that, but in theory 1:2/3@gatornet shouldn't match 1:2/3@fidonet and if there is no match, there should be no call. I guess binkd would also try to lookup the binkp.net address for the gatornet domain if you have a "defnode *' line in binkd.cfg. If nothing works you could try a 5D config in binkd and symlinks for the 4D tosser, someting like ../othernet ../gatornet ../outbound ../outbound.002 ../outbound.039 -> ./gatornet ../outbound.fff -> ./othernet Maybe others have better ideas :) --- gossipEd-linux/arm .0.21-18496a58 * Origin: (2:280/464.47) .