Hi, Mark-

ml> they had used this setting for his system... apparently he had been using 
ml> IREX and then switched... so the problem was that the MBSE systems were 
ml> forcing binkp 1.0 but still indicating binkp 1.1 and his binkd was not 
ml> switching to binkp 1.0 because of this false indication... he was finally 

That wouldn't surprise me.  MBSE's author even coded in the Y2K bug present
in the Blue Wave format that it uses and Andrew Leary wrote a patch to fix

ml> things have been fine ever since... he's asked several times for a similar 

ml> switch in binkd to force binkp 1.0 capability on a system so that one can 
ml> at least connect and exchange mail to tell them of the problem... without 
ml> this capability, it is possible that some system will be cut off and 
ml> assume the worse and have no way of contacting the other operator to try 
ml> to resolve it...

In my case, I was able to resolve the issue and was in contact with the
nodes in question.  If anyone is set up in my system, I make sure to have at
least two other methods of contact in case something like the above happens. 
I've seen weird things happen before and you learn when you get burned.

This might be something for someone to fix in MBSE.  I just don't know
enough about C to even attempt to fix something.

Later,
Sean

ml> to resolve it...


--- MBSE BBS v1.0.1 (GNU/Linux-x86_64)