Closed Bug 209488 Opened 21 years ago Closed 17 years ago

Message view filtering for custom headers is not working

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: delta-mozilla, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529

A custom message view filtering for specific "X-..."-headers always shows all
messages

Reproducible: Always

Steps to Reproduce:
1. View > Customize | New
2. "Customize..." | Add "X-Warning" | OK
3. "X-Warning" still does not show, so I click 'Cancel', then 'New' again
4. fill in "X-Warning" "contains" "by" | OK | OK

Actual Results:  
I can still see all messages in the current folder

Expected Results:  
I should only see messages containing a "X-Warning" header set to something like
"subnet managed by APNIC"
looks like dupe of bug 205501

*** This bug has been marked as a duplicate of 205501 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
I dont think this is a duplicate. I can reproduce this one with POP and "Local 
Folders", while bug 205501 appears to be about the headers not being kept 
locally in an IMAP account.

Furthermore, the problem in bug 205501 is that NO messages are showing in the 
view, while the problem here is that still ALL messages are showing, in spite 
of the view.

The reason for this behaviour seems to be that if you specify a custom header 
field in the view, the _entire_ header is searched for the search pattern, not 
just the field you specified. To verify this, follow the "Steps to reproduce" 
above, but in step 4 use "contains" "Jul" instead of "contains" "by". When you 
apply this view, you should see all mails that have "Jul" anywhere in the 
header, for example in the "Date" field.

I suggest to reopen this bug.
I can reproduce the problem as described by Uwe Schröder in comment 3 -- filter 
on X- headers does seem to be broken, in just the way described.  Reopening.

I also tried setting up a view:
  X-Accept-Language, is, en
I viewed a folder where at least one message definitely matches that, but the 
thread pane is shown empty.

Then I tried
  X-Accept-Language, is, 8bit
knowing that a message in the folder has
  Content-Transfer-Encoding: 8bit
but this filter also shows an empty panel.

Then I tried
  Content-Transfer-Encoding, is, 8bit
but again, the thread pane was empty.

Then I tried
  Content-Transfer-Encoding, contains, 8bit
This worked on all the C-T-E: 8bit headers, but it also worked on a test message 
with
  Subject: 8bit is fun
for a message whose C-T-E is 7bit.

I also tried a final view:
  Subject, contains, 8bit
and only the test message above was included in the view.


Conclusions:
 - problem is not limited to X- headers, but any custom header
 - if the filter is "is" it never matches
 - if the filter is "contains" it matches *any* header containing the substring

  Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040726

For the record: Reporter (delta-mozilla) -- are you seeing the problem in 
Local/POP folders, or in IMAP folders?


Incidentally: the editing process for MailViews, particularly when adding custom 
headers, is badly broken -- it's impossible to select a newly-entered header, or 
a newly-entered view, from the dropdown list.  I'll look for a bug on this, or 
open a new one.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Summary: A custom message view filtering for specific "X-..."-headers always shows all messages → Message view filtering for custom headers is not working
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #4)
> For the record: Reporter (delta-mozilla) -- are you seeing the problem in 
> Local/POP folders, or in IMAP folders?

The problem is reproducible in both Local and POP Folders. Couldn't test IMAP.
(In reply to comment #4)
> Incidentally: the editing process for MailViews, particularly when adding
> custom headers, is badly broken -- it's impossible to select a newly-entered
> header, or a newly-entered view, from the dropdown list.  I'll look for a bug
> on this, or open a new one.

Bug 254804 has been opened for this issue.
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0? → blocking-aviary1.0+
*** Bug 261438 has been marked as a duplicate of this bug. ***
I only seem to run into problems here when I first create the view using a
custom attribute. If I quit and restart the view works as it should with the
custom header. Weird. 
oh wait this shouldn't really work anyway since views do local searches and we
don't store custom headers in the database for imap so we won't find any matches.

It worked for me at first because i was using a custom header that matched a
header we happened to be storing locally...i'm going to minus this for the 1.0
release. I don't think this is a stopper anymore. 
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
(In reply to comment #9)
> oh wait this shouldn't really work anyway since views do local searches and
> we don't store custom headers in the database for imap so we won't find any
> matches.

But this problem is reported for POP/Local accounts.

If in general we should not allow MailViews that can't apply to IMAP (and RSS?) 
as well as POP, then the MailView editor needs to be redefined to show only the 
allowed headers -- xref bug 199689.
Product: Browser → Seamonkey
*** Bug 273395 has been marked as a duplicate of this bug. ***
Why is "Mailnews: Search" a Suite component rather than a Core component?

Per the dupe, this is a problem for virtual/saved-search folders as well, 
unsurprisingly.
Assignee: sspitzer → mail
*** Bug 326857 has been marked as a duplicate of this bug. ***
I have this problem with virtual folders: I wanted to have virtual folders for the "X-Label" header I'm using, but TB seems to stubbornly refuse to search that header. Is this the same bug or do I open a new one?
This bug has been fixed by the patches to bug 338310 and bug 339985, for TB 2.0 and Seamonkey 1.1.
Status: NEW → RESOLVED
Closed: 21 years ago17 years ago
Resolution: --- → FIXED
It doesn't work for me.  I'm using Seamonkey 1.1 on Linux, and when I specify a custom view, it says it can't find any messages, which is incorrect.
If you're trying to view an IMAP folder, that's bug 184490.

Otherwise, please state the details of your "custom view".
I am talking about IMAP folders, but bug 184490 is about filters, not views.

And by View, I mean the pull-down menu in the message pane that labeled "View:" and has these options:

All
Unread
  Tags           >
  Custom Views   >
Save View as a Folder...
Customize...
You're right -- bug 205501 is about the problem with MailViews under IMAP; at core, I think they're the same bug.
yes, I think Mike is right.
Component: MailNews: Search → MailNews: Message Display
QA Contact: laurel → search
You need to log in before you can comment on or make changes to this bug.