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

Status: VERIFIED FIXED

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

Description

[(not reading, please use [e-mail] instead)]

I hope to have this for m11.

Comment 1

[(not reading, please use [e-mail] instead)]

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.

Comment 2

[(not reading, please use [e-mail] instead)]

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.)

Comment 3

[laurel]

What about the case of the new profile who just creates a news account?

Comment 4

[(not reading, please use [e-mail] instead)]

update status whiteboard.

Comment 5

[(not reading, please use [e-mail] instead)]

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?

Comment 6

[(not reading, please use [e-mail] instead)]

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").

Comment 7

[(not reading, please use [e-mail] instead)]

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

Comment 8

[laurel]

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.