Closed Bug 205501 Opened 22 years ago Closed 16 years ago

Views don't work with custom search message header in IMAP accounts

Categories

(MailNews Core :: Search, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: baffoni, Unassigned)

References

(Blocks 1 open bug)

Details

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507 1) create a custom search header by going to the message search, select customize for the header field, put in a new header type (e.g. x-msmail, etc.). 2) Verify that there are messages that can be found with that custom header by doing a search with it and verify messages come up. 3) Create a view based only on that custom header field Expected behavior: all of the messages found with the search should show in the view Actual behavior: No messages are viewed with that custom view.
*** This bug has been marked as a duplicate of 196780 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Oops, I thought it was the same as bug 196780, but I just realized that they were talking about any custom view, not just a custom view created with a custom header (and with 1.4b (release), I don't have the problem with new custom views not showing immediately as long as they contain default headers).
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Michael, do you use IMAP or POP?
Status: REOPENED → ASSIGNED
QA Contact: esther → nbaca
a guess about what's going on, assuming this is imap only. I bet with IMAP, we don't have the headers around. to search for headers like this on imap, we have to execute and online search, running an specific imap url which does the search on the server. this is what advanced search will do. but, QS does a search against the local header db. I need to check the other view choices, but if there are things that won't in the .msf file, we can't allow you to create a QS for them, at least not one that will work for imap and pop. we have a similar bug (logged by nbaca, most likely) about not allowing you to create a QS view on body, since that won't work for IMAP. I think the "fix" for this will be to not allow you to create QS views on custom headers.
Trunk build 2003-05-23: WinMe - Views using custom headers do not appear to work with my IMAP account but does work for my POP account. - Interesting... On my POP account I only have messages where the MIME-Version is 1.0. Then I create a view "MIME-Version" "contains" "2" and it displays all the messages in the folder when it should show 0.
Yes, I'm using IMAP. I use junk filtering that ends up downloading all messages anyway - anyway we can get the download from junk filters to properly update the .msf with all of the indexing?
we don't store the custom headers in the db (to keep the db size under control). Since views work with local search, they're not going to work with custom headers.
*** Bug 208735 has been marked as a duplicate of this bug. ***
*** Bug 209488 has been marked as a duplicate of this bug. ***
*** Bug 215699 has been marked as a duplicate of this bug. ***
(In reply to comment #9) I can reproduce Bug 209488 with POP and "Local Folders", while this bug here appears to be about IMAP. Furthermore, the problem here is that NO messages are showing in the view, while in Bug 209488 the problem is that still ALL messages are showing, in spite of the view. Should I post further comments on that issue here anyway, or should Bug 209488 be reopened?
Views with custom headers also don't work with News filters using Thunderbird 0.7.3.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Status: ASSIGNED → NEW
This issue seems to remain with Thunderbird 2.0a1, even if the "Search Online"-option is ticked for the saved search in question. Am I the only one seeing this?
I have the problem that virtual folders never want to search my custom headers (standard headers are still fine). Is this the same bug or do I need to open a new one?
*** Bug 235506 has been marked as a duplicate of this bug. ***
Blocks: mailviews
Could someone please change the message summary to contain the word "IMAP", because that's all this bug is about? Non-IMAP filter view failures were fixed recently via bug 209488. You may as well also change the hardware and OS, because this problem affects Mac and Linux also.
Done.
OS: Windows XP → All
Hardware: PC → All
Summary: Views don't work with custom search message header → Views don't work with custom search message header in IMAP accounts
Isn't it possible that the db code could be smart enough to know which headers it should store in the db based on which custom headers are added to list? After all, it seems the list of custom headers I want to care about is global to thunderbird, so when I add one to the list, it would be nice if thunderbird would be so kind as to start making sure it's got that one cached for future reference.
Assignee: mail → bienvenu
Assignee: bienvenu → search
Component: MailNews: Main Mail Window → Search
Product: Mozilla Application Suite → Core
QA Contact: nbaca
Assignee: search → bienvenu
Assignee: bienvenu → nobody
Component: Search → MailNews: Search
QA Contact: search
In response to comment 18, I tried copying my mailnews.customHeaders entry to mailnews.customDBHeaders, and the result was that my imap server puked back errors every time I opened a folder. It looks like we'll need to make the caching code a bit smarter first. I like the idea though. If someone who knows the code would deign to point me in the right direction, I will write the patch myself. I'm getting sick of this bug.
Related to this issue, custom headers are not detected by custom column handlers in IMAP accounts. RE: http://developer.mozilla.org/en/docs/Extensions:Thunderbird:customDBHeaders_Preference I'm not sure if a new bug should be filed on that.
Product: Core → MailNews Core
Michael Baffoni is this problem gone using current trunk/early beta?
Yes, this is working for me with Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20090214 Shredder/3.0b2pre.
Status: NEW → RESOLVED
Closed: 22 years ago16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.