Closed Bug 342798 Opened 19 years ago Closed 18 years ago

Enhancement: Share filter among IMAP client machines

Categories

(Thunderbird :: General, enhancement)

x86
Windows 2000
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 78858

People

(Reporter: shaneyfelt, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4 It's too much trouble to synchronize changes to my filters among IMAP client machines. The process could be automated so that you set up a filter using one IMAP client machine, say at work, then go to the other IMAP client machine and have the same filter automatically applied when you read from there. Here's one way to do it: Synchronization could be automated by generating a dummy message in perhaps the drafts folder containing perhaps XML representation of the filter. As changes to the filter are made, the dummy message would be generated or updated. As FireFox starts up, it would check for filter updates and offer to update the filter based on the draft message. There are certainly other ways to do this, but this could work with existing standards. To stop the automated filter update step, simply delete the draft message (or make it an option through the GUI) Reproducible: Always Steps to Reproduce: 1. Run thunderbird on work machine, and set up a filter 2. Cause mail to arrive in your inbox 3. Rum thunderbird on home machine, and see if the filter has an effect. Actual Results: The filter created at work does not appear at home, and it is too frustrating to manually synchroinize the filters. Expected Results: The filter created at work should work at home, with no more trouble than checking a box in the preferences, or clicking OK to synchronize when a filter is created or changes elsewhere.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.