Hello g00r00,

On 18 Dec 15 07:10, g00r00 wrote to Nicholas Boel:

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

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

I'm not 100% sure on any of this, to be honest. I get wierd connection
issues with Mystic systems at times, and usually it ends up being a stuck
bundle/packet in their inbound (even though I thought this was fixed as
well, so it's possible those systems haven't upgraded yet, and if that's
the case, obviously it's no fault of the current version).

I can be sure on the fact that I haven't gotten NEARLY as many issues
lately. So, I could just be rehashing old shit. If anything happens, I'll
have to make note of it when it actually happens, rather than try to
reflect on it at a later date. lol

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20151129