NB> I'm unsure as to if or when the issue has ever stopped, but I don't
 NB> think this particular issue I'm describing had anything to do with IREX,
 NB> since I'm using binkd here, and pretty sure the issue was when trying to
 NB> connect to Mystic's binkp server. Whether the other system was

No, I am talking about connecting to Mystic.  There were problems during
development in that area that have been fixed as development went on.

For example, IREX when acting as a client to Mystic, used to fail
authentication because IREX adds null characters to the MD5 calculation and
Mystic didn't account for it.  There was another one where some systems sent
the MD5 equiv password of "-" instead of a blank, and Mystic
couldn't handle
it. I can't remember them all but there were plenty of little things like that
back then when BINKP was in development that caused problems with CRAM and
some mailers.

--- Mystic BBS v1.12 A1 (Windows)