Hello g00r00,

On 24 Nov 15 20:43, g00r00 wrote to Nicholas Boel:

 NB>> To be completely honest, the most problems I've had with Mystic
 NB>> systems is that option. I think we should ditch the "FORCE
 NB>> cram-md5" option but keep the optional "yes/no"
one per link.
 NB>> Much less confusion that way.

 gr> You don't want the option to require your links to use encrypted
 gr> passwords in order to exchange mail?  What part is the confusing part
 gr> again?  Sorry I know we discussed this in the past but its been a long
 gr> time and I can't remember.

I would rather there not be an option to force *every* connection to use
CRAM-MD5. It should be on a per-link basis instead (which that option is
already there also).

 gr> Lets get it sorted out.  I think when we talked about it before I was
 gr> in the middle of 1001 other BINKP builds so it just sort of got
 gr> forgotten.

For some reason, and I'm not sure what combination is used each time it
occurs, but when the "FORCED" option is used in the binkp server
settings, even though my system is setup to use cram-md5 with theirs, it
causes connection errors.

I don't know if they have it enabled in the binkp server settings, and NOT
in the link configuration, or have both enabled or what. Usually disabling
the "FORCED" option in the server settings  and enabling the link
option of cram-md5 fixes the bad connections, though.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20150715