I have attached 2 patches that you are looking for that I use in my
install. It removes the restriction for PLAIN from the frontends to the
backends.
Ken Murchison wrote:
Ramya Krishnan wrote:
Michael Loftis wrote:
-nodes IIRC
--On December 15, 2005 12:43:53 PM +0530 Ramya Krishnan
<[EMA
Ramya Krishnan wrote:
Michael Loftis wrote:
-nodes IIRC
--On December 15, 2005 12:43:53 PM +0530 Ramya Krishnan
<[EMAIL PROTECTED]> wrote:
Ken Murchison wrote:
Because the frontends proxy as the user to the backend, the IMAP LOGIN
command can not be used. The only plaintext SASL mechan
Michael Loftis wrote:
-nodes IIRC
--On December 15, 2005 12:43:53 PM +0530 Ramya Krishnan
<[EMAIL PROTECTED]> wrote:
Ken Murchison wrote:
Because the frontends proxy as the user to the backend, the IMAP LOGIN
command can not be used. The only plaintext SASL mechanism that can be
used is
-nodes IIRC
--On December 15, 2005 12:43:53 PM +0530 Ramya Krishnan
<[EMAIL PROTECTED]> wrote:
Ken Murchison wrote:
Because the frontends proxy as the user to the backend, the IMAP LOGIN
command can not be used. The only plaintext SASL mechanism that can be
used is PLAIN, but you can't us
Ken Murchison wrote:
Because the frontends proxy as the user to the backend, the IMAP LOGIN
command can not be used. The only plaintext SASL mechanism that can be
used is PLAIN, but you can't use it unless protected by TLS. Looking
at the CAPABILITY output above, it doesn't look like you've
Ramya Krishnan wrote:
Hii,
I would like to configure a backend server and a frontend server(with
mupdate server). I use LDAP authentication(SASLAUTHD) in both backend
and frontend servers.
I am able to authenticate directly to the backend and select inbox.
When I connect through the frontend,
