Closed Bug 285841 Opened 20 years ago Closed 20 years ago

Message Filters don't work on header information

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.7 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 244311

People

(Reporter: sturges, Assigned: sspitzer)

Details

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

Selecting "TO" and choosing some criteria in the header path does not detect the
information.

It seems that there is no way to filter emails based on the path they followed.

Reproducible: Always

Steps to Reproduce:
1. Create a message filter and select "TO" as the item to filter. Select any
criteria found in the header path that the email followed and it will not find
the item when you do Run Now.
2. Add a new selectable item using Customise and create a new selectable item
called "header" and run the above test based on "header" instead of "To" and it
will not find the item when you do Run Now.
3.
> filter emails based on the path they followed

It almost sounds like you expect to find servernames in the recipient (To:) field?
To filter the "Received" fields of the header, you must customize a filter

*** This bug has been marked as a duplicate of 244311 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
(In reply to comment #1)

> To filter the "Received" fields of the header, you must customize a filter


There is no functionality in Mozilla to refer to the "header" information in a
search [and no predefined field to select - like To or CC]; There is a customise
that lets you add another field name but nothing allows you to configure to what
it applies.

Am I missing something?
(In reply to comment #2)
> 
> *** This bug has been marked as a duplicate of 244311 ***

This bug may be a dup, but not of bug 244311. Did you perhaps mistype the bug
number?
You need to log in before you can comment on or make changes to this bug.