[PREF MIGRATION] biff pref migration problem

VERIFIED FIXED in M14

Status

MailNews Core
Profile Migration
P1
normal
VERIFIED FIXED
19 years ago
10 years ago

People

(Reporter: laurel, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
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).
(Reporter)

Updated

19 years ago
QA Contact: gbush → laurel
accepting.  marking all milestone 11.

Updated

19 years ago
Target Milestone: M11 → M12

Comment 2

19 years ago
M12

Updated

19 years ago
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
Last Resolved: 19 years ago
Resolution: --- → FIXED
marking fixed.  this got fixed a while ago.
(Reporter)

Comment 5

19 years 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.