395745 - Importing email from Outlook PST file results in some messages having html tags

Status: RESOLVED DUPLICATE of bug 207156

(MailNews Core :: Import, defect)

Description

[Gabriel Kaplan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
Build Identifier: Thunderbird 2.0.0.6

I know this was a problem in earlier versions of T-bird for importing mail from Eudora but I haven't found any discussion of this in regards to Outlook.

I imported my PST files from Outlook 2003 into Thunderbird as part of an effort to migrate my Outlook emails to MS Entourage 2004.  Everything went smoothly except some emails arrived with thick html tags and code embedded around the text of the message.  Now mind you this did not happen to all messages.  My hunch is that it only happened to emails that were composed in Outlook when Outlook uses Word as it's email composer/editor (but that's just a hunch).  I know that not all the messages came across this way and about half came across just fine with all formatting appearing the way it was supposed to.

In addition, many of the attachments came across fine although some of them seemed to lose their file extension so that the computer could not tell what kind of program wrote them (this was on the PC.)

Has anyone else run into this and if so are there any fixes out there?  I have found no mention of this any where on the web other than the reference to this problem with Eudora and the 0.7 build of Thunderbird.

Reproducible: Didn't try

Steps to Reproduce:
1.Export your Outlook files to a PST file using OUtlooks Export function
2.Go to Tools in Thunderbird and Import
3.Select Outlook and messages and next
Actual Results:  
Same problem

Expected Results:  
all the messages should be readable in the same way they were in Outlook

Comment 1

[Joshua Cranmer [:jcranmer]]

Moving bugs from TB: Migration to MailNews Core: Import, as the code for Outlook, OE, and Eudora migration is almost entirely shared within the core import code.

Comment 2

[wcn00]

I would like to add my "me to" to this.  I just converted about 500gb of mail from outlook 2003 to thunderbird 2.0.  Things went fine for a few days until several (and eventaully all) users noticed that about 1/4 of their archived mail appears in thunderbird in raw html format.  
I looked for a way to fix this but it would involve changing headers and adding tags all over the place.  Its the fault of the original outlook importer.
We've decided to stay with thunderbird (because for this group the alternative is outlook 2008 which is dog slow) but should a fix for this problem become available will reconvert the historical email again to reover its readability.  For the moment it is necessary to paste such mail into an editor that will render basic html... blech.

Comment 4

[Jorg K (CEST = GMT+2)]

This is NOT a duplicate of bug 250878, but it was fixed together with the issues in bug 207156.

Comment 5

[Ludovic Hirlimann [:Usul]]

(In reply to comment #4)
> This is NOT a duplicate of bug 250878, but it was fixed together with the
> issues in bug 207156.

207156 isn't fixed...

Comment 6

[Jorg K (CEST = GMT+2)]

Well, yes, it is now. I can assure you that this is not a duplicate of  bug 250878, since I fixed the latter ;-) and it has nothing to do with the symptoms described here.

Comment 7

[Ludovic Hirlimann [:Usul]]

(In reply to comment #6)
> Well, yes, it is now. I can assure you that this is not a duplicate of  bug
> 250878, since I fixed the latter ;-) and it has nothing to do with the symptoms
> described here.

Korg would you like to fix this one too ?

Comment 8

[Jorg K (CEST = GMT+2)]

This bus has been fixed as part of the fix to bug 207156. In bug 207156 Mike reworked the retrieval of the message body from Outlook, including getting the type (plain text or HTML) right.

Comment 9

[Ludovic Hirlimann [:Usul]]

(In reply to comment #8)
> This bus has been fixed as part of the fix to bug 207156. In bug 207156 Mike
> reworked the retrieval of the message body from Outlook, including getting the
> type (plain text or HTML) right.

Rah missread your comment 6