864301 - Rules File not common

Status: RESOLVED DUPLICATE of bug 34973

(Thunderbird :: Filters, defect)

Description

[OldManRiver]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130201190337

Steps to reproduce:

Message Filters not in common by account, but by mailbox.


Actual results:

When a person logs into TBird their rules, the entire set should be in the main profile directory, but instead they are scattered across the mail accounts, inbox by inbox.  Right now their is no option to apply a rule to "ALL" inboxes, which should be the default.  So a person has to derive the rules, one-by-one into a Master Rule file, which then has to be cut-n-pasted into the individual inbox rules files.

Please fix this so their is only one rules file per account and also allow the users to designate either "ALL" or the name of the individual inbox he/she want the rule to apply to.

Currently all kinds of problem occur, when trying to sync up the rules, which should not be and should not be the responsibility of the user to manually correct this flaw in the program.

PS.
You bugzilla is errored here as all files for TBird are in the .thunderbird (hidden) folder and your "File Browse" does not allow for any hidden directories.  Therefore files can not be entered through the web site.



Expected results:

Single rules file should be in the main account profile directory and give the user the option to apply a rule to "ALL" inboxes in the account or to a specific inbox by inbox name.

Comment 2

[OldManRiver]

Sirs;

How can you say "Resolved" and assign to a ticket that has been open and unresolved since 2000?

This is a obvious political move to "make yourselves look good" when in fact you have done nothing!

Do not do this, the original, since it over a year old, should have already been scrubbed from the system and the original does not, from my reading, address this issue at all.

Quit fixing the data to look good and insted fix things so the project is going forward!

Thanks!

Nyle

Comment 3

[:aceman]

As you can see we do not want to look good and actually have admitted this is a >10 years old request. You wouldn't know without me duping this bug :)
Having 2 open bugs for the same thing will only make matters worse.

Ok, can you say why bug 34973 does not address the problem here? What is different?

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to OldManRiver from comment #2)
> Sirs;
> 
> How can you say "Resolved" and assign to a ticket that has been open and
> unresolved since 2000?
> 
> This is a obvious political move to "make yourselves look good" when in fact
> you have done nothing!

Thank you for your interest. On the contrary, keeping the bug database as trim as possible and identifying duplicates HELPS bring focus to bugs with common ideas and needs.  This is the way we operate in *this* bug database.

With no further feedback, I agree with aceman this is properly a duplicate of 34973, despite your protests. Please do not reopen this bug.