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 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? Is that right? > However, I don't think that's what you really want to do. It looks to me > as if you are looking for messages with non-empty FROM and TO. In that > case, > tag SEARCH OR FROM "" TO "" > will accomplish what you want with much less trauma. > > Then again, it should be noted that there is no such thing in the Internet > email specification as an empty FROM, and most MTAs will ensure a > non-empty From: header, generally taking it from the SMTP originator or > "MAILER-DAEMON" as a last resort. Thus, in effect, > tag SEARCH TO "" > is all you really need. I forgot to mention that my SEARCH commands were just examples in order to show the problem, and such queries would probably be useless... Anyway, are there any plans to remove this limitation? Thanks again, Lefteris Chatzibarbas
