Hi all,

We have a couple of customers attempting to use our qpsmptd powered smtp
auth server from some relatively ancient software called turnpike. It
appears that when faced with the prospect of having to do AUTH PLAIN or
CRAM-MD5 with a relatively long username/password pair that turnpike
inserts a line break into the base64 encoded string and therefore auth
fails. Apparently the only auth method that will work with turnpike is
LOGIN because the user and password are split on different lines.

With this in mind is it possible without having to patch qpsmtpd to
influence the order that auth methods are presented in from "250 AUTH
PLAIN LOGIN CRAM-MD5" such that LOGIN is the first available option?
Apparently in turnpike you can't specify the method you use and it
always picks the first one in the list.

I appreciate this is a rather odd request and a much better option would
be to not use turnpike, but can anyone help with fixing this at the
server end without resorting to altering the core qpsmtpd code? Altering
plugins is fine.

cheers,
Paul

Reply via email to