Closed Bug 272952 Opened 20 years ago Closed 18 years ago

Eudora migration should import filters

Categories

(Thunderbird :: Migration, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 359255

People

(Reporter: oliver, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Thunderbird 1.0RC1 (20041201)

Noticed in migrating from Eudora 6.1 that Message Filters were not migrated.

Reproducible: Always
Steps to Reproduce:
1. Install Eudora 6.1 (Sponsored)
2. Create some Filters in Eudora (eg. match sender, transfer to a folder).
3. Install TB and choose Eudora import option.
Actual Results:  
No filters were migrated from Eudora 6.1 to Thunderbird.

Expected Results:  
The migrate should have recreated the old Eudora filters as Thunderbird filters
closely as possible.  Since it's done at the same time as the mail/folders
import, it should be possible to wire up the "Transfer To <folder>" type actions
to the right folders.

In my Eudora 6.1 installation my filters appear to live in Filters.pce.

Obviously certain filter criteria and actions may not have a TB equivalent. A
decision would need to be made whether to notify the user of those, or just fail
silently.

But it's the message transfer filters that were most important to me (eg. for
handling a large number of mailing lists), and probably most other Eudora users
who rely on filters.
I confirm this behaviour, filters are not imported.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
"If anyone thinks this is incorrect, they should feel free to reopen it."

I think this is incorrect, yet I am powerless to reopen it.

Isn't auto-resolving bugs a bit irresponsible? No one can be bothered to look at feature requests? And here I thought that WONTFIX was the most arrogant response to a user request...
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
confirming
Status: UNCONFIRMED → NEW
Ever confirmed: true
confirmed to still be a hole on Thunderbird 2.0.0.0.
QA Contact: migration
Status: NEW → RESOLVED
Closed: 19 years ago18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.