Off the top of my head, TEXT searches *everywhere* -- all headers, body, etc.
""[EMAIL PROTECTED]"" <[EMAIL PROTECTED]> said: > Sounds good. I just looked at the php.net keywords and noticed: > > TEXT "string" - match messages with text "string" > > Is that synonymous to BODY? > > Xing > > Aaron Stone wrote: >> So let's make two text fields: >> >> IMAP_SEARCH_ALLOW and IMAP_SEARCH_DENY, then use these keywords: >> >> http://us2.php.net/imap_search >> >> By default, allow all and deny none. If Deny is *, then we only allow >> what's in the allowed list. If Allow is * then we only deny the denied >> list. >> >> In your case, IMAP_SEARCH_DENY=BODY and you're done. >> >> Aaron >> >> >> ""[EMAIL PROTECTED]"" <[EMAIL PROTECTED]> said: >> >> >>>The search queries would be more intensive as it has to process each >>>record retrieved vs a just retrieving all the records. >>> >>>The reason I have suggested the search block option is because in it's >>>current state, 2.0.1 + mysql, the BODY search is already useless, timing >>>out each time, so instead of having a feature that nets only negative >>>gain to my server load with zero return, it's heck a lot safer to stop >>>serving searches altogether. >>> >>>Xing >>> >>> >>>>Is there really a gain for this feature? >>>> >>>>The IMAP client has to make a search, >>>>preferably on the server. >>>>If the server lacks these capabilities will the client back off and >>>>download all messages and do the search itself. >>>>We actually do not gain anything, the database must in these cases serve >>>>the content of all the messages down to the client. This is as expensive >>>>as doing a linear search in the database. >>>> >>>>Magnus >>> >>>_______________________________________________ >>>Dbmail-dev mailing list >>>Dbmail-dev@dbmail.org >>>http://twister.fastxs.net/mailman/listinfo/dbmail-dev >>> >> >> > > _______________________________________________ > Dbmail-dev mailing list > Dbmail-dev@dbmail.org > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > --
