Michael Loftis wrote:
I guess that's what CRAM-MD5 is for, but the frontend refuses to talk to
the backend if it is presented with CRAM-MD5 only. Is there any way to do
this or I am doing something really wrong? :)
See earlier in this thread. It's not at all possible in stock Cyrus.
You hav
Andrew Morgan wrote:
Oops, I forgot about that detail. We locally patched referrals out
of our IMAP proxies.
Umm, isn't there an option on the configuration to disable referrals?
If not, do you have that patch available?
I've attached the patch to this message. We use it with Cyrus v2.2.12
--On October 5, 2006 11:42:36 AM +0100 Jesus Roncero <[EMAIL PROTECTED]>
wrote:
Umm, I got it to work using DIGEST-MD5, but apparently, all
communications are encrypted after the authentication. Is there a way in
which all the communications between the frontends and the backends are
*not*
--On October 5, 2006 10:30:55 AM +0100 Jesus Roncero <[EMAIL PROTECTED]>
wrote:
Umm, isn't there an option on the configuration to disable referrals? If
not, do you have that patch available?
Not in 2.0.x for sure. Maybe in newer releases. We're running a 'very
old' release of Cyrus
On Thu, 5 Oct 2006, Jesus Roncero wrote:
Michael Loftis wrote:
Authentication of the user happens at the frontend. The frontend then
uses the proxy credentials to authorize as the user on the backend.
The backends don't need a full user database, just the proxy
information.
Yes and no. I
Jesus Roncero wrote:
Oops, I forgot about that detail. We locally patched referrals out of
our IMAP proxies.
Umm, isn't there an option on the configuration to disable referrals? If
not, do you have that patch available?
Also, one question on the communication between the frontends and
ba
Michael Loftis wrote:
Authentication of the user happens at the frontend. The frontend then
uses the proxy credentials to authorize as the user on the backend.
The backends don't need a full user database, just the proxy
information.
Yes and no. If an IMAP client support referrals, the fro
On Wed, 4 Oct 2006, Michael Loftis wrote:
--On October 4, 2006 10:17:46 AM -0700 Andrew Morgan <[EMAIL PROTECTED]> wrote:
On Wed, 4 Oct 2006, Michael Loftis wrote:
--On October 4, 2006 4:18:41 PM +0100 Jesus Roncero
<[EMAIL PROTECTED]> wrote:
<...>>
So, the question is, isn't the frontend
--On October 4, 2006 10:17:46 AM -0700 Andrew Morgan <[EMAIL PROTECTED]>
wrote:
On Wed, 4 Oct 2006, Michael Loftis wrote:
--On October 4, 2006 4:18:41 PM +0100 Jesus Roncero
<[EMAIL PROTECTED]> wrote:
<...>>
So, the question is, isn't the frontend supposed to contact the backend
respons
On Wed, 4 Oct 2006, Michael Loftis wrote:
--On October 4, 2006 4:18:41 PM +0100 Jesus Roncero <[EMAIL PROTECTED]>
wrote:
<...>>
So, the question is, isn't the frontend supposed to contact the backend
responsible of that mailbox in order to authenticate the user? or it
needs to have "joe"'s pa
--On October 4, 2006 4:18:41 PM +0100 Jesus Roncero <[EMAIL PROTECTED]>
wrote:
<...>>
So, the question is, isn't the frontend supposed to contact the backend
responsible of that mailbox in order to authenticate the user? or it
needs to have "joe"'s password at the frontend as well?
Authent
On Wed, 4 Oct 2006, Jesus Roncero wrote:
Hi,
So I got the whole murder system running. Apparently, both the frontend
server and the backend server can communicate. I have a backend server that
has a couple of mailboxes, one of which is called "joe". I'm using a sasldb
file on both of the mach
12 matches
Mail list logo