Re: SEARCH command limit in uw-imapd?

2002-06-13 Thread Mark Crispin
On Thu, 13 Jun 2002 16:07:13 +0300, Lefteris Chatzibarbas wrote: > What would be the recommended format of the SEARCH command that > would be generated from the user's filter in order for it to scale > and be able to handle 50,100 or 500 searching criteria? In a worst-case situation, you can alwa

Re: SEARCH command limit in uw-imapd?

2002-06-13 Thread Lefteris Chatzibarbas
On Wed, Jun 12, 2002 at 05:41:02PM -0700, Mark Crispin wrote: > On Thu, 13 Jun 2002, Lefteris Chatzibarbas wrote: > > By that you mean to send 2 SEARCH commands with less that 50 deep nesting > > each? Is that right? > > No, I mean doing: > > OR (OR FROM "a" OR FROM "b" FROM "c") OR FROM "d" OR

Re: SEARCH command limit in uw-imapd?

2002-06-12 Thread Mark Crispin
On Wed, 12 Jun 2002, Pete Maclean wrote: > >Each OR effectively takes you down a level of nesting. That is: > > > > OR (FROM "a") OR (FROM "b") OR (FROM "c") (FROM "d") > >is effectively > > OR (FROM "a") (OR (FROM "b") (OR (FROM "c") (FROM "d"))) > I never realized this! And my

Re: SEARCH command limit in uw-imapd?

2002-06-12 Thread Mark Crispin
On Thu, 13 Jun 2002, Lefteris Chatzibarbas wrote: > > UW imapd declines to accept nesting more than 50 deep. Instead of nesting > > 50 deep, you could OR two groups that nest 25 deep and get the same > > effect. > By that you mean to send 2 SEARCH commands with less that 50 deep nesting > each? I

Re: SEARCH command limit in uw-imapd?

2002-06-12 Thread Pete Maclean
>Each OR effectively takes you down a level of nesting. That is: > > OR (FROM "a") OR (FROM "b") OR (FROM "c") (FROM "d") >is effectively > OR (FROM "a") (OR (FROM "b") (OR (FROM "c") (FROM "d"))) I never realized this! And my server does not handle such a thing appropriately.

Re: SEARCH command limit in uw-imapd?

2002-06-12 Thread Lefteris Chatzibarbas
xOn Wed, Jun 12, 2002 at 04:11:09PM -0700, Mark Crispin wrote: > Each OR effectively takes you down a level of nesting. That is: > > OR (FROM "a") OR (FROM "b") OR (FROM "c") (FROM "d") > is effectively > OR (FROM "a") (OR (FROM "b") (OR (FROM "c") (FROM "d"))) > > UW imapd declines t

Re: SEARCH command limit in uw-imapd?

2002-06-12 Thread Mark Crispin
On Thu, 13 Jun 2002, Lefteris Chatzibarbas wrote: > Is there a limit on how many searching criteria may be specified > on an IMAP4rev1 SEARCH command? The limit is not on how many criteria, but rather on the depth of the criteria. Each OR effectively takes you down a level of nesting. That is:

SEARCH command limit in uw-imapd?

2002-06-12 Thread Lefteris Chatzibarbas
Hello, I use uw-imapd version 2001adebian-6 (under a Debian Sid/Unstable system), which I believe is based on imap-2001a. I also get the same error when I try at other uw-imapd mail servers, apart from my system. Is there a limit on how many searching criteria may be specified on an IMAP4rev1 SE