Closed Bug 356576 Opened 18 years ago Closed 16 years ago

A user_pref preference to use filters like in 1.0.x (filters on local folders NOT automatic)

Categories

(Thunderbird :: Security, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 440635

People

(Reporter: gialloporpora, Assigned: dveditz)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.8.1) Gecko/20061003 Firefox/2.0
Build Identifier: Thunderbird 1.5.x

In Thunderbird 1.5.x Filters  on  Local Folders are executed automaticcaly when I download my new message, I would like a user_pref preference to  not execute filters on Local Folders automatically like in 1.0.x version.

I understand that people want filers like in OE but OE is not a logical client.
When people have filled bug about version 1.0.x saying "filters are not executed automatically" they have not understand the problem.
Filters on 1.0.x are executed automaticclly  (also with global inbox) if they are set on Remote Folders (ex. pop.yahoo.com...).
The real problem is:
when a filter like the same name are created  both in Local Folders and in a remote account the  TB ignore the filter created on the remote account.

In TB 1.0.x was possible two kinds of filters:
- manual filters
- automatic filters
in TB 1.5.x the first kind of filters are dead.
Sorry for my english and thank for your attention


Reproducible: Always




I report this BUG as "Freature Request" because I know that  many people does not use this  feature , but this feature exist in version 1.0.x
The latest trunk builds (which will go into Thunderbird 3) now have a function that you can specify whether filters should be run with one of the following options:

1) New Mail is received
2) Filters are manually run
3) New Mail is received or filters are manually run.

It can be specified at individual filter level, giving you greater flexibility.

Therefore you now will have the same capability as per 1.x, and this bug is a duplicate of bug 440635 which implemented this fix.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.