cyrus-imapd server, sasl client and "encoded packet size too big (4156 > 4096)"

2013-02-24 Thread Ragnar Sundblad
Hello all, We are modernizing our Cyrus IMAP server, and are using cyrus sasl 2.1.26 and imap server 2.4.17. We are using Kerberos (GSSAPI) for authenticating the different parts to each other, such as the proxy to the imapd, imapds to each other, and such. We often get "encoded packet size too

Re: upgrading with murder/aggregator

2010-05-28 Thread Ragnar Sundblad
On 28 maj 2010, at 19.58, Andrew Morgan wrote: > On Fri, 28 May 2010, Ragnar Sundblad wrote: > >> Is murder/aggregator backwards compatible with older imap >> servers? >> >> We want to migrate form a single 2.1.18 cyrus imap server to >> multiple 2.3.x se

Re: upgrading with murder/aggregator

2010-05-28 Thread Ragnar Sundblad
On 28 maj 2010, at 16.53, Torsten Schlabach wrote: > Hi Ragnar! > >> Could this be mitigated by letting the proxys have a lifetime of only >> one session? > > Possibly. I am sure if any proxyd terminates after having done its work > (which means either after a logout or a given idle period) thi

Re: upgrading with murder/aggregator

2010-05-28 Thread Ragnar Sundblad
o! I'll do the same! > I'd also be interested in > your findings. But me personally, I can only encourage you to go for > what you have in mind. Unless you have a very tight deadline and very > little data to migrate. We don't have a very tight deadline: the sooner the better

upgrading with murder/aggregator

2010-05-28 Thread Ragnar Sundblad
Is murder/aggregator backwards compatible with older imap servers? We want to migrate form a single 2.1.18 cyrus imap server to multiple 2.3.x servers. An idea is to insert a common murder/aggregator in front of both the 2.1.18 server and the new servers, and seamlessly migrate users. Would this