64117 - Import from Eudora: Extra lines added to the original mails in In mailbox.

Status: VERIFIED DUPLICATE of bug 3157

(MailNews Core :: Backend, defect, P2)

Description

[ji]

This bug is seperated from bug 58897.
After import finishes, there is Eudora account created. In (jushin), Out
(soushin) and Trash (Gomibako) folder in addtion to some default folders are
created under this account. For the mail in the In folder, The Ja chars can be
displayed correctly. But there are following two lines added to wrap the
original mail.
<x-flowed>
</x-flowed>

Comment 1

[nhottanscp]

This does not look like a Japanese specific problem.
Is this Eudora-J specific or also happens with US version.

Comment 2

[ji]

That's right. It's a general problem. Importing from Eudora 5.02 using 
2000-12-31-21-Mtrunk build has the same problem.
Changed the component, summary and QA contact. 
Naoki, please reassign. Thanks.

Comment 3

[nhottanscp]

Reassign to [e-mail], cc to putterman.

Comment 4

[Ninoschka Baca]

Build 2001-02-26-09: NT4
Using Eudora 5.0.2 I'm not seeing this problem. Can someone try this again with
a more recent build?

Comment 5

[ji]

I still have this problem when importing mail from Eudora 5.0.2 to 02/26 on NT.
I used pop on Eudora.

Comment 6

[Ninoschka Baca]

Build 2001-03-0920: NT4
I was able to import Eudora Mail (once without crashing,bug# 57125) 
and reproduced the problem.

The extra lines do not appear when:
- Importing Settings from Eudora
- Importing Mail from Outlook Express

Comment 7

[Ninoschka Baca]

Build 2001-06-21-04: WinMe
Build 2001-06-22-04: Mac 9.04
This problem is still present. The "<x-flowed>  </x-flowed>" tags appear for all
html messages imported from Eudora. 

Comment 8

[scottputterman]

reassigning to cavin.

Comment 9

[Cavin Song]

The extra two lines in the body text:

<x-flowed>
</x-flowed>

are created by Eudora and we simply import the msgs without making any changes 
to them. Every Eudora msg whose 'Content-Type:' header contains 'format=flowed' 
is wrapped with the <x-flowed> tag. Here is an example:

. . .
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-UIDL: e5d15a6dd0d2ec84d484178236d5b46c
Status: RO

<x-flowed>
test

</x-flowed>

To fix this we really need to parse the body and strip out the <x-flowed> tag.

Comment 10

[scottputterman]

We should try to fix this at some point, but right now it's going to have to
exist.  Apparently 4.x had the same bug.

Comment 11

[Ninoschka Baca]

This appears to be a duplicate of bug# 3157.

*** This bug has been marked as a duplicate of 3157 ***

Comment 12

[Ninoschka Baca]

Verified duplicate.