Re: imclient >4k literal error

2003-04-02 Thread Igor Brezac
On Wed, 2 Apr 2003, Patrick Welche wrote: > On Wed, Apr 02, 2003 at 01:28:06PM -0500, Rob Siemborski wrote: > > See Also: > > > > http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=333 > > > > In practice, not many applications use libcyrus for reading email, the > > closest we generally see is for s

Re: imclient >4k literal error

2003-04-02 Thread Patrick Welche
On Wed, Apr 02, 2003 at 01:28:06PM -0500, Rob Siemborski wrote: > See Also: > > http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=333 > > In practice, not many applications use libcyrus for reading email, the > closest we generally see is for small things like cyradm. So there hasn't > been pressur

Re: imclient >4k literal error

2003-04-02 Thread Rob Siemborski
See Also: http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=333 In practice, not many applications use libcyrus for reading email, the closest we generally see is for small things like cyradm. So there hasn't been pressure to fix it. -Rob On Wed, 2 Apr 2003, Patrick Welche wrote: > When libcyrus

imclient >4k literal error

2003-04-02 Thread Patrick Welche
When libcyrus reads a server response, it does so in 4k (4067) chunks. If I read a message which is greater than 4k, it is be truncated, eg {96091} gives me a 96050 long reply->text, the beginning of the reply looking like: FETCH (FLAGS (\\Seen) INTERNALDATE \"24-Feb-2003 12:45:17 +\" BODY[]