Hello g00r00!

I've started experimenting with the subject version, and I've come across a problem:

If the password (under EchoMail Nodes, Session Options) is left blank,
CRAM-MD5 sessions fail.  Entering a single dash (-) in the password field
allows the session to proceed correctly.  Mystic should default to using a
single dash (-) as the password when none is defined, as per FTS-1026
paragraph 5.5:

M_PWD 2

           Session password, case sensitive. Only Originating side
           MUST send this message. After successful password
           authentication of the remote, Answering side may proceed
           to the file transfer stage. This command MUST never be sent
           by the Answering side. If no password is available for the
           remote, M_PWD "-" must be sent to indicate that there is no
           password.

I haven't fully tested it yet, but so far your binkp/1.1 implementation
seems to be working properly.  I will let you know if I find any other
issues.

Regards,

Andrew

---