Trunk build 2003-05-23: WinMe Overview: Create a customize view (using an entry in the message header) and the name of the view does not appear immediately in the Message View Setup dropdown menu. Steps to reproduce: 1. From the views dropdown menu select Customize 2. Select New so that the Message View Setup dialog appears 3. Click on the first dropdown menu, go to the bottom to select Customize so that the Customize Headers dialog appears. 4. Type the name of a header (i.e. User-Agent), select the Add button and it appears in the list, press the OK button. 5. From the Message View Setup dialog click on the first dropdown menu again and look for the newly created custom view. Actual Results: The new custom view does not appear. Close the Message View Setup dialog, reopen the dialog, click on the dropdown menu again and now the custom view appears. Expected Results: The new custom view should appear in the dropdown list immediately after its creation.

I can confirm this bug on Mozilla 1.4 for Win32. Further to the bug mentioned above when you create a customised header (in my case "X-Spam-Flag" or "X-Spam-Level") and then create a view using this header, no messages are found. Negating the expression matches all messages. mailView.dat contains: --------------------- name="Spam" enabled="no" type="1" condition="OR (\"X-Spam-Flag\",contains,YES)" --------------------- If this should be logged as a new bug, then i will do so (I don't want to take away from the original bug above).

*** Bug 217135 has been marked as a duplicate of this bug. ***

> mailView.dat contains: > --------------------- > name="Spam" > enabled="no" > type="1" > condition="OR (\"X-Spam-Flag\",contains,YES)" > --------------------- > > If this should be logged as a new bug, then i will do so (I don't want to take > away from the original bug above). this bug is still active in Thunderbird 0.4 (20031205) and Mozilla 1.6 on Win32

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

Regarding the problem in comment 1/comment 3 -- is the problem seen for IMAP accounts? There are known issues for applying custom-header filtering of any sort to IMAP message stores -- see bug 196605, bug 199689, bug 184490; also bug 67421, bug 127250.

(In reply to comment #5) > Regarding the problem in comment 1/comment 3 -- is the problem seen for IMAP > accounts? you are rigth: comment 3 was relatetd to remote imap account.

my interest in this bug was also from an IMAP pov (additional comment #1). We use IMAP as our primary mailbox protocol.