Talk:Message Filters: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
(patch for auto reply/forwarding)
No edit summary
Line 19: Line 19:


I think it's in the works. Check out this bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=11034], where someone's got a basic implementation proposed. -- [[User:Srcosmo|srcosmo]] 14:00, 21 May 2005 (PDT)
I think it's in the works. Check out this bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=11034], where someone's got a basic implementation proposed. -- [[User:Srcosmo|srcosmo]] 14:00, 21 May 2005 (PDT)
== Dichotomous Filtering ==
This is a suggestion for a new type of filtering, called dichotomous filtering after the dichotomous keys used in many methods of classification.  I'm not certain that this is the proper place to put it, but I am entering it here because I feel it needs discussing and I haven't been able to find the proper place to suggest it.  Please send complaints to mozilla@rapplean.net.
In dichotomous filtering, a user creates a tree structure of nodes.  Some nodes are decision nodes. i.e. does the email fit into this category (yes|no).  Others are action nodes: Move to folder X.  These nodes are built into a tree structure which the email is passed through to determine what to do with it.  Although this sounds a lot like what is currently implemented, the current implementation has two major limitations. 
The first is that once a piece of mail fits a specific rule, then filtering of that email stops.  No further filtering can be done.  While it's possible to craft a rule such that it only activates when the mail '''doesn't''' match the rule, it is not possible to have separate further conditions for both sides.
Another problem is that any action taken must be at the end of a sequence.  This prevents behaviors from occuring in-line.  You can [http://www.mythologicalbeast.org/rapplean_dichotomos_filter.gif click here to see an illustration].
Another advantage to this that it creates considerably greater modularity with what can be done, what can be checked on, and how the mail could be treated.  In theory, different baysian filters could be applied at different points in the chain.  Chains could be stored in a central location, and each email account could feed into them at varying points.
In any case, please let me know if there is a better place to post this.

Revision as of 22:44, 14 January 2006

Related:

4/8/05 Changes

I added these changes, stating that filtering stops after the first filter condition is met, based on my observation as a user, and a little (not comprehensive) testing. I have noted some inconsistencies since making this change in the KB, but have not reported it as a bug, since I have seen no documentation of how this feature is supposed to work. Nor have I changed the KB again, since I don't know how it is supposed to work, and whether the behavior I have observed is a bug, or correct behavior according to rules I can't devine from my samples.

Hopefully someone in the know will see these changes and confirm or correct them to state how the program was designed to work.

BTW, for manual filtering, what I have described has always held true. For automatic filtering, it appears that whether a filter stops the filtering process depends on the actions chosen for that filter.

I've modified your edit to clarify. I think what happens is that if one of your filters moves a message from the Inbox, then subsequent filters will not be applied. All you have to do to remedy this is switch the order of your filters, so that the one which moves the message to a specified folder is listed after your other filters. --Wintogreen 19:36, 17 Apr 2005 (PDT)

Filters for forwarding messages

As I have seen in Thunderbird Filters rules, there is no ability to forward or reply an incoming message in dependence on some conditions. Is this ability planned in future versions of Mozilla Thunderbird?

I think it's in the works. Check out this bug: [4], where someone's got a basic implementation proposed. -- srcosmo 14:00, 21 May 2005 (PDT)


Dichotomous Filtering

This is a suggestion for a new type of filtering, called dichotomous filtering after the dichotomous keys used in many methods of classification. I'm not certain that this is the proper place to put it, but I am entering it here because I feel it needs discussing and I haven't been able to find the proper place to suggest it. Please send complaints to mozilla@rapplean.net.

In dichotomous filtering, a user creates a tree structure of nodes. Some nodes are decision nodes. i.e. does the email fit into this category (yes|no). Others are action nodes: Move to folder X. These nodes are built into a tree structure which the email is passed through to determine what to do with it. Although this sounds a lot like what is currently implemented, the current implementation has two major limitations.

The first is that once a piece of mail fits a specific rule, then filtering of that email stops. No further filtering can be done. While it's possible to craft a rule such that it only activates when the mail doesn't match the rule, it is not possible to have separate further conditions for both sides.

Another problem is that any action taken must be at the end of a sequence. This prevents behaviors from occuring in-line. You can click here to see an illustration.

Another advantage to this that it creates considerably greater modularity with what can be done, what can be checked on, and how the mail could be treated. In theory, different baysian filters could be applied at different points in the chain. Chains could be stored in a central location, and each email account could feed into them at varying points.

In any case, please let me know if there is a better place to post this.