Closed Bug 18064 Opened 25 years ago Closed 25 years ago

[MIGRATION] if user had POP in 4.x don't give them a "Local Mail" account

Categories

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

x86
All
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: sspitzer, Assigned: sspitzer)

Details

(Whiteboard: fix in hand, reviewed by alecf, seeking approval now.)

I hope to have this for m11.
Status: NEW → ASSIGNED
if we have a new user, who isn't migrating, I have one other related change to make: don't automatically create a "Local Mail" account. the code needs to be changed to: if you create a new IMAP server, create a "Local Mail" (type=none) account unless one already exists accepting.
Target Milestone: M11
I've got a fix in my tree. I'll do some serious testing tomorrow and get it reviewed, and hopefully make it into m11. I think with will help prevent confusion (for pop users.)
QA Contact: gbush → laurel
What about the case of the new profile who just creates a news account?
Whiteboard: fix in hand, reviewed by alecf, seeking approval now.
update status whiteboard.
in the case where you create just news.... the point of having a "Local Mail" account would be to get a Sent, Trash, Drafts Unsent Messages (send later) and Templates folder. if they had just news, they'd still want those folders. so, in that case, I'd say create a Local Mail account, if one doesn't exist, when a news account is created. agreed?
a problem the news scenario just described... if they have pop, and add a news, do they reall need pop, local mail, and news? That seems wrong. perhaps we should do as alecf suggested: only create a "Local Mail" if you create a new server and no other "mailbox:/" server exists. (pop or none, aka. "Local Mail").
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
fixed. the only unresolved issue is that news issue that laurel raised. I'll open a new bug on that, and fix it when we decided what todo.-
Status: RESOLVED → VERIFIED
Verified for most basic scenarios on all platforms using commercial builds nov8 and nov 9. Any specific scenarios with problems will be logged as separate issues.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.