On Wed, 2004-02-18 at 14:09, Prentice Bisbal wrote:
> Jim,
>
> Thanks for the response. Unfortunately, that's not my problem:
>
> # mupdatetest -p 3905 -u mupdater 128.6.239.23
> S: * AUTH "PLAIN"
> S: * STARTTLS
>
I've Cc'd the list, but I don't think it is working at the moment. So I
hope you
My sasl_mech_list is set to plain:
sasl_mech_list: PLAIN
Which is working for me, as shown in the previous post. The question is
why can I authenticate from Cyrus and postfix (smtp auth), but not mupdate?
Prentice
Rob Siemborski wrote:
On Wed, 18 Feb 2004, Jim Levie wrote:
I don't see a way
Jim,
Thanks for the response. Unfortunately, that's not my problem:
# mupdatetest -p 3905 -u mupdater 128.6.239.23
S: * AUTH "PLAIN"
S: * STARTTLS
Prentice
Jim Levie wrote:
On Tue, 2004-02-17 at 15:59, Prentice Bisbal wrote:
Im setting up Cyrus on a SAN where /var/spool/imap is shared via the
On Wed, 18 Feb 2004, Jim Levie wrote:
> I don't see a way of limiting the mupdate server's allowable auth mechs
> in the imapd.conf, but I found that renaming the
> /usr/lib/sasl2/libgssapiv2* plugins and restarting Cyrus on the mupdate
> server is a workable solution.
sasl_mech_list should be as
On Tue, 2004-02-17 at 15:59, Prentice Bisbal wrote:
> Im setting up Cyrus on a SAN where /var/spool/imap is shared via the
> san. I'm using the unified-imap branch as suggested by Ken Murchison.
> Everything seems to be working except mupdate. When I try to create a
> mailbox, I get the followin
