Closed Bug 21688 Opened 25 years ago Closed 25 years ago

[Dogfood] Headers are all collapsed into 1 line when forwarding certain types of msgs

Categories

(MailNews Core :: MIME, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: momoi, Assigned: jefft)

References

Details

(Whiteboard: [PDT-])

Attachments

(1 file)

** Observed with 12/13/99 Win32 build (1999121314) ** In the Intl Somketest file I use, if I forward/inline the 2nd and 3rd messages under HTML send option, all the headers are quoted "fused" into 1 line. We used to have this problem for almost all msgs but now only certain types of msgs seem to exhibit this problem. The 2nd and 3r msgs in the Smoketest file are typical. Other 3 msgs in the Smoketest file do not cause this problem.
Attached file Intl Smoketest File. —
Please save the attached file as "smoketest.zip" and un-archive it using the Zip utility.
QA Contact: lchiang → esther
Actually, since the HTML or Plain Text option changes depending on what the original msg was, this problem happens with both HTML and Plain text send option. The 2nd msg in the Smoketest file will induce Plain Text mail and the 3rd, HTML mail.
Originally I set the send option to HTML but the problem happens when the send option is Plain Text also.
*** Bug 21746 has been marked as a duplicate of this bug. ***
Severity: major → critical
Summary: Headers are all collapsed into 1 line when forwarding certain tyeps of msgs → [Dogfood] Headers are all collapsed into 1 line when forwarding certain tyeps of msgs
Target Milestone: M12
I have been able to narrow this down to the following. It looks like this will be a serious problem for non-English Plain text mail users. This problem occurs under the following conditions: 1. When the original mail contains "Plain text body". 2. When the original mail contains non-ASCII characters in the headers, e.g. Subject line. Apparently, as we try to form forwarding headers, line breaks are lost if the headers contain non-ASCII characters under the above conditions. I'm going to raise the severity to critical. I would like to get this fixed for M12 if at all possible.
Assignee: rhp → jefft
Jeff, Can you take a look at this? - rhp
In addition to the plain text original, I found one condition under which the original HTML mail body causes this problem also. 1. Go to some web page with 4.x -- it does not matter which. Netscape English Home Page will do for this purpose. 2. Send this page to your Mozilla mail account but make sure that a. Your digital sigature is attached. b. Your vCard option is turned off. c. Include some Latin 1 "accented" characters in your Subject. 4. Receive this msg with Mozilla. Now try forward as inline on this message. You will see that header lines lose the line breaks. I found that: When the message is an HTML type with simple multipart/mixed parts, e.g. a web page attached to your message (containing non-ASCII headers), this problem does not occur on forward/inline. But if you add your siganture to this, you get: multipart/signed; protocol="application/x-pkcs7-signature" wrapping up the multipart/mixed part. Under this condition, the problem occurs. Another way to induce this problem easily is to have both vCard and digital sigature turned on. This will produce the same structure as above. 1. Try a message which contains non-ASCII headers, HTML body, vCard (non-ASCII OK),and a digital signature. The problem will be visisble if you try Forward/inline on this message. 2. Now skip the signature to the same message as in step 1. In this case, the problem will not occur when you engage Forward as inline on it.
Status: NEW → ASSIGNED
Sure...
Is there a clear dogfood workaround here?
I just filed a related bug -- Bug 21856.
The workaround is to forward as attachment and do NOT forward as inline. This can be marked PDT-. But it is definitely needed for Beta (hopefully by M13). Feedback is that in Japan most users use forward as inline as opposed to forward as attachment.
This bug should be reduced to the forward as inline of PLAIN TEXT email. (The HTML case has been logged as a separate bug 21856. See comment above.) In the plain text case, if you look at the HTML generated for the message compose window, the linebreaks are missing.
Summary: [Dogfood] Headers are all collapsed into 1 line when forwarding certain tyeps of msgs → [Dogfood] Headers are all collapsed into 1 line when forwarding certain types of msgs
I think we should keep the HTML case also where it loses linebreaks. Bug 21856 was filed for another bug, that of losing the body and the attachment under the same condition which causes this bug.
Whiteboard: [PDT-]
Putting on PDT- radar...you can fwd as attachment :-)
Target Milestone: M12 → M13
Move to M13....
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This is fixed along with fixing bug 21869.
Status: RESOLVED → REOPENED
** Checked with 12/24/99 Win32 Mozilla M13 build ** The 2 types of problems as I described above dont appear to be fixed in this new build. Also note that the plain text example I mentioned first does not contain any multi-parts to begin. It is just a single body 1-line message with nothing else. Re-opening ...
Resolution: FIXED → ---
Status: REOPENED → ASSIGNED
We are having problem with the second message of the Smoketest folder. We stripped out all the CRLF when doing MIME_DecodeMimePartIIStr(). I wonder why?
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Fix checked in to conditionally strip out the line continuation.
QA Contact: esther → momoi
Esther, if you don't mind, let me check on this fix. Assigning myself as QA contact.
** Chcecked with 1/24/00 Win32 build ** I tried all the original scenarios mentioned above with msgs which contain non-ASCII in headers. 1) 2 msgs in Smoketest file, 2) HTML mail with S/MIME and/or vCard. In none of these cases, line-collapsing occurred. Marking fix verified/fixed.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: