Re: Help with xfermailbox

2007-11-19 Thread Wesley Craig
On 19 Nov 2007, at 16:15, Dan White wrote: > kaled (mupdate master and frontend): > none, other than an mupdate_admins entry If it's an mupdate master & frontend, you probably want the mupdate_server configured, and mupdate_config: standard. > Is xfermailbox valid in a standard murder? Yes, yo

Re: Help with xfermailbox

2007-11-19 Thread Dan White
Wesley Craig wrote: > I didn't look too hard at your other errors. Looking back now, I wonder > how you have mupdate_config set? The kick_mupdate error you're getting > isn't associated with the "standard" setting, tho it appears from your > description that you are otherwise using a standard

Re: Help with xfermailbox

2007-11-19 Thread Wesley Craig
On 19 Nov 2007, at 12:57, Dan White wrote: > Regarding the call to kick_mupdate and the attempt to open the file > socket, could I be missing an entry in my cyrus.conf file? When I saw your note included: > Nov 17 09:25:02 neo cyrus/imap[11281]: decoding error: generic > failure; SASL(-1): ge

Re: Help with xfermailbox

2007-11-19 Thread Dan White
Dan White wrote: > Dan White wrote: >> Wesley Craig wrote: >>> If I recall correctly, this is a bad interaction/bug between Cyrus IMAPd >>> and Cyrus SASL. I see you're running IMAP 2.3.10. What version of SASL? >>> >> 2.1.22 from Debian etch with a couple of customizations to >> ldapdb, which

Re: Help with xfermailbox

2007-11-17 Thread Dan White
Dan White wrote: > Wesley Craig wrote: >> If I recall correctly, this is a bad interaction/bug between Cyrus IMAPd >> and Cyrus SASL. I see you're running IMAP 2.3.10. What version of SASL? >> > > 2.1.22 from Debian etch with a couple of customizations to > ldapdb, which itself it compiled aga

Re: Help with xfermailbox

2007-11-17 Thread Wesley Craig
If I recall correctly, this is a bad interaction/bug between Cyrus IMAPd and Cyrus SASL. I see you're running IMAP 2.3.10. What version of SASL? :wes On 17 Nov 2007, at 10:27, Dan White wrote: > Nov 17 09:25:02 neo cyrus/imap[11281]: encoded packet size too big > (4156 > 4096) Cyrus

Re: Help with xfermailbox

2007-11-17 Thread Dan White
Wesley Craig wrote: > If I recall correctly, this is a bad interaction/bug between Cyrus IMAPd > and Cyrus SASL. I see you're running IMAP 2.3.10. What version of SASL? > 2.1.22 from Debian etch with a couple of customizations to ldapdb, which itself it compiled against openldap 2.3.30. I've

Re: Help with xfermailbox

2007-11-17 Thread Dan White
Wesley Craig wrote: > On 16 Nov 2007, at 15:53, Dan White wrote: >> Nov 16 13:44:57 neo cyrus/imap[6171]: decoding error: generic >> failure; SASL(-1): generic failure: , closing connection > > A fuller version of this error is probably recorded in your auth log. > > :wes Here's from my syslog.c

Re: Help with xfermailbox

2007-11-16 Thread Wesley Craig
On 16 Nov 2007, at 15:53, Dan White wrote: > Nov 16 13:44:57 neo cyrus/imap[6171]: decoding error: generic > failure; SASL(-1): generic failure: , closing connection A fuller version of this error is probably recorded in your auth log. :wes Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyru