Hello Daryl,

On 19 Apr 14 11:21, Daryl Stout wrote to ALL:

 DS>   I have IREX set to daemon mode, and to allow "unlisted
systems" to
 DS> connect.

 DS>   However, I'm getting reports of several who try to connect via
 DS> BinkP, and they're getting a "connection refused" message.

 DS>   Am I missing something?? Or should I just have my nodelist entries
 DS> entry of CM changed to MO??

If they're coming to you with the reports, ask them what binkp service
they're using. There was just discussion in the MBSE echo of mbcico having
to have an option set to force a link into binkp v1.0 mode for Irex
connections otherwise there's errors. I think the same kind of stuff
happens once in awhile using binkd to connect with Irex systems as well,
but noone has pinpointed the real problem there.

I move quite a bit of mail here, and use binkd. I've noticed that when I
use the '-nd' option (no dupe mode) it tends to have iffy results with Irex
connections. Instead, I disable that option and use the '-nr' option
(non-reliable link) instead. Tends to work a lot better after I do that.

I know it's not hard evidence, but hopefully that may help you in where to
continue on with this. It has been reported and proven that Irex reports
the wrong version of the binkp protocol, and other mailers have to adjust
for that. While development on Irex has stopped (meaning it will probably
never be "fixed", other mailers have taken that into
consideration and worked around it, though sometimes specific options have
to be set in the other mailer.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910