Summary | Equals and Not Equals rules idea |
Queue | Ingo |
Queue Version | HEAD |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | neale (at) metawerx (dot) net |
Created | 12/12/2006 (6808 days ago) |
Due | |
Updated | 12/13/2006 (6807 days ago) |
Assigned | |
Resolved | 12/13/2006 (6807 days ago) |
Milestone | |
Patch | No |
State ⇒ Rejected
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Equals and Not Equals rules idea
Queue ⇒ Ingo
and Doesn't contain rules.
In certain cases, it is useful to be able to specify a rule where a
field equals a value, instead of simply containing it.
Real-life example:
- I subscribe to a list called "Some List".
- The mailing list comes through with a subject of Some List.
- I also sometimes receive messages from business partners, with
subjects such as "Saw this on Some List...".
- If I set up a rule that moves "Some List" messages to my some-list
folder, I have no way to specify that I only want to match the exact
subject "Some List", except for the current "Contains" rule.
- Therefore the messages from my business partners also get included
in the filter.