Sam Varshavchik wrote: > Markus Warg writes: > >> Hi, >> >> >> I removed all CRAM* options from ESMTPAUTH and ESMTPAUTH_TLS and it >> works. I really don't know why CRAM does not, but it seems that this >> was the problem. > > CRAM authentication has some additional requirements, besides just > listing it as an available authentication method. If you have not set > up CRAM authentication accordingly, clients will try, fail, and > fallback to regular authenication. The failed authentication attempt, > like any other failed authentication attempt incurs a forced penalty, > an enforced delay, before the server will accept another login attempt.
Interesting. I verified that CRAM authentication was failing on both of my Courier systems. Disabling it made them both much more responsive. What additional requirements does CRAM have? I looked in the INSTALL document, the courier man page, and the esmtpd config file. None of them said anything other than that you have to use a compatible authentication method, which I am (authuserdb). -- Bowie ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
