Closed
Bug 276464
Opened 20 years ago
Closed 19 years ago
Adress book Thunderbird 1.0 : bad When importing MS Outlook 2003 addressbook, old (obsolete) addresses are imported
Categories
(MailNews Core :: Import, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: redsun, Assigned: mscott)
Details
For many contacts, a spécific e-mail address has been replaced by an old and depreciated e-mail adress. For exemple, I had in my Outlook 2003 the contact "xx" with only one e-mail adress : "xx@wanadoo.fr" After the standard import, Thunderbird presents me a contact with the good name "xx". But, this contact has only one e-mail and it is not the actual e-mail present in Office 2003 ! It is an depreciated e-mail adress (xxx@hotmail.com here). It is very important because with this problem, the import is not reliable.
Comment 1•20 years ago
|
||
I don't get it. Where would that old email-address (xxx@hotmail.com) be coming from ? Was it in the Outlook address book (under a different name ?) Or was it already in the Tunderbird address book, maybe in the 'Collected Addresses' list ?
I agree that it is a very strange bug. I know that this email-adress was not already in Thunderbird because it was a new install without mails or email-adress. The fact is that the bad email-adress presented by Thunderbird is an old adress for this contact (and just for this contact). This adress was erased in Outlook 2003 many months before. In addition, Thunderbird presents me two directory in Adress book that were erased too many months before in Outlook 2003 ! <X-File music> In addition, an other fact : I have erased my Thunderbird adress book. Then, I have added a "real adress" (street, city...) of a contact that presents a problem. Then, I have runned again the import of Thunderbird. The previous problem (ghost directory, bad email-adress...) were always here but the new "real" adress added too. Therefore, we can think that the Outlook 2003 datafile target is good... I suppose that Outlook 2003 keeps many "historic" informations in this adress book data representation and that the import on Thunderbird is confused by this "historic" informations.
Updated•20 years ago
|
Component: Address Book → MailNews: Import
Product: Thunderbird → Core
Summary: Adress book Thunderbird 1.0 : bad e-mail address for many contacts after an import from Outlook 2003 → Adress book Thunderbird 1.0 : bad When importing MS Outlook 2003 addressbook, old (obsolete) addresses are imported
Version: unspecified → 1.0 Branch
Comment 3•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•