Closed Bug 15295 Opened 21 years ago Closed 20 years ago

[PREF MIGRATION] biff pref migration problem

Categories

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

x86
All
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: laurel, Assigned: sspitzer)

Details

Using 1999092909m11 NT 4.0
Will confirm on other platforms

The biff ("check for new mail every N minutes") setting doesn't migrate
correctly for POP or IMAP (no news biff in 4.x to migrate).  Here's what I've
found:

1.  When migrating enabled biff, the enabled state and value do not migrate to a
"mail.server.server1..." seamonkey type of pref line, rather the values go to
4.x generic "server.nsmail-1" type of pref line.

2.  The migrated enabled value indeed is reflected in the accounts setup UI
(good, but prefs.js seamonkey style line not present).
QA Contact: gbush → laurel
accepting.  marking all milestone 11.
Target Milestone: M11 → M12
M12
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)
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
marking fixed.  this got fixed a while ago.
OK using:
2000-01-20-08m13 commercial build on NT 4.0
2000-01-20-08m13 commercial build on linux rh 6.0
2000-01-20-08m13 mozilla build on mac OS 8.5.1
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.