No, what is happening is that Evolution is sending a set of UIDs that is too long for the server to handle.
For example, the implementation of UW.IMAP is that no command line can exceed 8000 bytes. Courier IMAP won't allow tokens larger than ~16k (the length of the command-line doesn't matter). I'm not sure about the implementation of Cyrus IMAP but I'm sure it's got some limitation such as the above two. (Note: a UID set is a single token) Anyways, I have code in CVS that will break command-lines into smaller chunks if they exceed a pre-defined limit. Jeff On Mon, 2002-03-11 at 01:27, Zot O'Connor wrote: > On Fri, 2002-03-08 at 17:22, Jeffrey Stedfast wrote: > > The problem is not a timeout or anything, it's because the uid list was > > too long most likely. This is already solved in development CVS as I > > said earlier. > > > > So is this an error on the evo side (too long)? That is evo is locking > up trying to send the too long list? Like maybe its sending a partial > list, thus causing an invalid (truncated) UID? > > I am trying to decide if I should debug the cyrus/SSL-tunnel end. I am > leaning towards a pure evo error, but no one else is complaining.... It > seems like a "me" problem. > > > > > > -- > Zot O'Connor > > http://www.ZotConsulting.com > http://www.WhiteKnightHackers.com > > > _______________________________________________ > evolution maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/evolution -- Jeffrey Stedfast Evolution Hacker - Ximian, Inc. [EMAIL PROTECTED] - www.ximian.com _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
