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: encoded packet size too big

2004-11-01 Thread Andreas
On Sat, Oct 30, 2004 at 09:28:13AM -0400, Kevin wrote: I'm guessing that the patch mentioned at the top of this thread is already in this file (I don't see anything in my file remotely resembling what I see in bugzilla line 1419), as well as the one that apparently caused the broken behavior

Re: encoded packet size too big

2004-10-30 Thread Kevin
that should make this work in both cases, however. I'm using Heimdal and the patch seems to work fine, at least it solved my original problem. Thanks a lot! Hi List- I just found this thread in the archive because I'm seeing the same problem (encoded packet size too big). I'm using MIT

Re: encoded packet size too big

2004-07-07 Thread Jukka Salmi
Rob Siemborski -- cyrus-sasl (2004-07-06 17:57:23 -0400): After talking with Sam Hartman, it became apparent that MIT gets the implementation of gss_wrap_size_limit right and Heimdal gets it oh...so...wrong. I've committed a patch that should make this work in both cases, however. I'm using

Re: encoded packet size too big

2004-07-06 Thread Jukka Salmi
with sieve[8083]: encoded packet size too big (4163 4096) Regards, Jukka [2] https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/src/sasl/plugins/gssapi.c.diff?r1=1.88r2=1.89 Jukka Salmi -- info-cyrus (2004-07-05 15:58:28 +0200): Jukka Salmi -- info-cyrus (2004-07-01 23:33:16 +0200

Re: encoded packet size too big

2004-07-06 Thread Andreas
, with rev. 1.89 uploading sieve scripts larger than 4000 bytes fails with sieve[8083]: encoded packet size too big (4163 4096) Here I applied only the patch at the bugzilla entry below in order to fix the problem (cyrus-sasl-2.1.18): https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2457

Re: encoded packet size too big

2004-07-06 Thread Rob Siemborski
On Tue, 6 Jul 2004, Andreas wrote: Here I applied only the patch at the bugzilla entry below in order to fix the problem (cyrus-sasl-2.1.18): https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2457 This patch corresponds to revision 1.88. I'll have a closer look at the changes in 1.89. -Rob

Re: encoded packet size too big

2004-07-06 Thread Rob Siemborski
On Tue, 6 Jul 2004, Rob Siemborski wrote: On Tue, 6 Jul 2004, Andreas wrote: Here I applied only the patch at the bugzilla entry below in order to fix the problem (cyrus-sasl-2.1.18): https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2457 This patch corresponds to revision 1.88.

Re: encoded packet size too big

2004-07-05 Thread Jukka Salmi
Jukka Salmi -- info-cyrus (2004-07-01 23:33:16 +0200): When authenticating with GSSAPI I can't upload Sieve script larger than about 4k bytes: To be more accurate, it's larger than 4000 bytes. sieve[7228]: encoded packet size too big (4107 4096) Applying [1] solved my problem

encoded packet size too big

2004-07-01 Thread Jukka Salmi
about 4k bytes: $ ls -l my.script -rw-r--r-- 1 jukka jukka 3664 Jul 1 23:31 my.script $ sieveshell -a gssapi mx1 connecting to mx1 put my.script Bad protocol from MANAGESIEVE server: expected LPAREN The following is logged: sieve[7228]: encoded packet size too big (4107 4096) If I