281511 - IMAP: wrong syntax for OR search

Status: RESOLVED DUPLICATE of bug 281510

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Ulf Uhrmann]

User-Agent:       Opera/8.00 (Windows NT 5.0; U; en)
Build Identifier: Mozilla MailNews 1.7.6; also TBird 1.0 and 20050203 nightly

When setting up a filter on IMAP-accounts which contains or-linked conditions, 
server returns an error.
Analyzed with ethereal: OR search term contains brackets while AND search term 
doesn't.
Search term should be
  <x> uid SEARCH UNDELETED OR HEADER SUBJECT "test3" HEADER SUBJECT "test4"
but is
  <x> uid SEARCH UNDELETED (OR HEADER SUBJECT "test3" HEADER SUBJECT "test4")
which doesn't work.


Reproducible: Always

Steps to Reproduce:
1. set up filter on IMAP account with two or more OR-linked conditions
2. try to run this filter
Actual Results:  
Server returns "BAD SEARCH parse error".


Expected Results:  
Server should return search results.

Extract from Ethereal log:
---------------------------------------------
DONE
108 OK IDLE terminated
109 uid SEARCH UNDELETED HEADER SUBJECT "test0"
* SEARCH
109 OK SEARCH completed
110 uid SEARCH UNDELETED HEADER SUBJECT "test1" HEADER SUBJECT "test2"
* SEARCH
110 OK SEARCH completed
111 uid SEARCH UNDELETED (OR HEADER SUBJECT "test3" HEADER SUBJECT "test4")
111 BAD SEARCH parse error
112 IDLE
+ idling
---------------------------------------------



Checked manually with telnet:
---------------------------------------------
3 uid SEARCH UNDELETED (OR HEADER SUBJECT "test3" HEADER SUBJECT "test4")
3 BAD SEARCH parse error
4 uid SEARCH UNDELETED OR HEADER SUBJECT "test3" HEADER SUBJECT "test4"
* 14 EXISTS
* 2 RECENT
* SEARCH 14 15
4 OK SEARCH completed
---------------------------------------------


I'm unsure if I should classify it as normal or major; in fact it's normal, but 
on the other hand it complicates using of filters (workaround is to set up own 
filter for every condition), therefore it should be fixed soon.

btw: As TBird is affected too, I have filed an identical bug report there.

Comment 1

[OstGote!]

see TB bug 281510 from reporter

Comment 2

[David :Bienvenu]

*** This bug has been marked as a duplicate of 281510 ***