Re: mupdate - GSSAPI authentication

2009-05-12 Thread Brian Awood
On Friday 08 May 2009 @ 06:59, David Mayo wrote: > Relevant lines from config files: > > sauber imapd.conf: > > admins: cyrus imap/sauber.bath.ac.uk > sasl_pwcheck_method: saslauthd > sasl_mech_list: plain gssapi > mupdate_server: tyrrell.bath.ac.uk > mupdate_config: standard > mupdate_authname: m

Re: mupdate - GSSAPI authentication

2009-05-12 Thread Dan White
David Mayo wrote: > Hi guys, > > This morning we created a principal "mupd...@bath.ac.uk" and added that > to the key tab on sauber for the IMAP server, and it authenticated fine. > > It would appear there is a bug somewhere meaning that > "primary/insta...@realm" style principals cannot be used

Re: mupdate - GSSAPI authentication

2009-05-12 Thread David Mayo
Hi guys, This morning we created a principal "mupd...@bath.ac.uk" and added that to the key tab on sauber for the IMAP server, and it authenticated fine. It would appear there is a bug somewhere meaning that "primary/insta...@realm" style principals cannot be used as clients to mupdate. Regar

mupdate - GSSAPI authentication

2009-05-08 Thread David Mayo
Hi guys, We are upgrading to cyrus-imap-2.3.14 and are looking at using mupdate for the first time, but we are having problems with the GSSAPI authentication between mupdate hosts. We have two servers - sauber and tyrrell. sauber is one of the backend hosts and tyrrell is the mupdate master. We h