If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Several accounts in one domain are not imported properly from Mozilla Suite into Thunderbird

RESOLVED INCOMPLETE

Status

Thunderbird
Migration
RESOLVED INCOMPLETE
11 years ago
9 years ago

People

(Reporter: sergeykhan, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: closeme 2008-10-02)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4

Fresh TB installation. Importing settings from Mozilla Suite.

There are several e-mails accounts in Mozilla Suite. Among them, lets consider two:
ACCOUNT        FOLDER TO STORE
a@domain.com - domain.com
b@domain.com - domain-1.com

After data importing into TB, they look like this:
a@domain.com - aaa (strange name that TB picked up)
b@domain.com - domain-1.com (which is empty!!)

WHAT happend:
1. Actual copy of all files for b@domain.com is in the 'domain.com' folder, which is not in use anymore, since b@domain.com is pointed on to 'domain-1.com'.

2. The content of the initial folder domain-1.com is in the folder 'aaa', which was created by TB.

Reproducible: Always

Steps to Reproduce:
1. Install Mozilla suite
2. Make two e-mail accounts for the same domain
3. Put somthing into inbox, sent, etc.
4. Close Mozilla Suite
5. Install TB, import data from Mozilla Suite

Actual Results:  
The data for a@domain.com stored into the folder 'aaa'
The data for b@domain.com stored into the folder 'domain-1.com' (which is empty!!)
The actual data for b@domain.com stored into 'domain.com' which is pointerless.

Expected Results:  
The data for a@domain.com stored into the folder 'domain.com'
The data for b@domain.com stored into the folder 'domain-1.com'
The folder 'aaa' is not created.

Updated

9 years ago
Assignee: mscott → nobody
Component: Installer → Migration
QA Contact: installer → migration
Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)
Whiteboard: closeme 2008-10-02
RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.