Closed Bug 14364 Opened 25 years ago Closed 24 years ago

[MIGRATION][FILTERS] 4.x filters "actionValues" need to be migrated to work in 5.0

Categories

(MailNews Core :: Profile Migration, defect, P1)

x86
All
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: sspitzer, Assigned: Bienvenu)

Details

in 5.0, we migrate your 4.x filter file over by copying it.

in the filter file (rules.dat on all platforms) we may have action values like:
actionValue="Trash"

in 4.x, this would mean the Trash folder on your "Local Mail".

in 5.0, this should me the Trash folder for your pop server, if you used pop in
4.x, or the Trash folder for your "Local Mail" if you used imap in 5.0

we have to "fix" the file, after we copy (and rename it for linux and mac),
because in 5.0, you can have multiple "Local Mail" servers.
Status: NEW → ASSIGNED
Target Milestone: M12
marking m12.

accepting.
QA Contact: gbush → laurel
Summary: [FILTERS] filters "actionValues" to play nice in 5.0 → [MIGRATION][FILTERS] 4.x filters "actionValues" need to be migrated to work in 5.0
change summary.
Target Milestone: M12 → M13
Priority: P3 → P1
Target Milestone: M13 → M14
marking p1.
(m14 p1 are m13 bugs that I want to fix first, but are not m13 blockers)
Target Milestone: M14 → M15
moving to m15
david, I think you've fixed this.  re-assign to you, so you can mark dup, or
fixed, or whatever.
Assignee: sspitzer → bienvenu
Status: ASSIGNED → NEW
yes, I fixed this as part of getting move to local folders to work.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
OK.  We do change POP for a Move to Folder/Trash.  We leave the folder actions
as is for migrating IMAP which has any Move to Folder/trash filters, whether the
imap 4.x profile specified local mail Trash folder or the online Trash folder.

This seems correct to me, although reading Seth's original comments confuse me a
bit ..

OK using jun13 m17 commercial build.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.