IMAP: Quoting in Reply/Forward of msgs containing non-ASCII characters in body is broken



20 years ago
10 years ago


(Reporter: momoi, Assigned: mscott)


Windows NT
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)




20 years ago
** Observed with 8/13/99 Win32 build **

** This bug was split from Bug 11763 which conflated 2 bugs into
   one and was confusing.

When replying or forwarding messages containing
non-ASCII body text on IMAP servers, auto-quoting produces
broken text. Here's a set of steps to reproduce this bug:

1. Select a JPN msg (HTML or plain)containing a Japanese header & body text
   with no attachment
2 [details] [diff] [review]. Now reply or forward (w/ auto auto) either under HTML or plain text mail
3. You see that the Message window body seems to be in raw JIS rather than
   in Japanese.

Note: header quote is not working -- this is a known bug.
      But the body text quote should show in Japanese.

Note 2: I tried Latin1 body text and this seems to be working
        in quoting both body and Subject header.
Note 3: quoting UTF-8 body does not work correctly.

Here's rhp's comment on this bug from Bug 11763:

------- Additional Comments From  08/13/99 12:20 -------
Ok, here is the deal.

The quoting we do with IMAP is a hack that is guaranteed not to work for
Japanese or any other non us-ascii text...and it didn't ever work. I am waiting
on a stream routine from mscott that won't be in the product until M10.


20 years ago
QA Contact: lchiang → momoi

Comment 1

20 years ago
Assigning myself as QA contact.


20 years ago
Target Milestone: M10


20 years ago
Blocks: 7228

Comment 2

20 years ago
Rich, (I don't profess to understand this bug) why will hooking up to the stream
converter fix this problem? (I do have that bug in on my M10 plate). Is it part
of your hack that will go away when we have that in place?

Comment 3

20 years ago
Yes, the hack that is in place is digging through the tempMessage.eml file on
disk to try to snarf some body text. This is because the SaveToDisk() method is
only implemented for local folders (not IMAP or NTTP). When the stream is in
place, the hack goes away for good.

- rhp

Comment 4

20 years ago
Uh, that's NNTP :-)


20 years ago
Assignee: rhp → mscott

Comment 5

20 years ago
Reassign to mscott to hook up streams from IMAP and NNTP to compose backend.

Comment 6

20 years ago
Triage to M11

Comment 7

20 years ago
*** Bug 13382 has been marked as a duplicate of this bug. ***


19 years ago

Comment 8

19 years ago
Kat, can you check out this bug again and see if the problem is still there?
Rich mentioned in this report that he needed some new interfaces from me. I've
done that and with some help from jefft, quoting for reply or forward no longer
uses a temp file. Rich's comments made me thing that things will just work once
I did that. So this bug may already be fixed.

Comment 9

19 years ago
I got a related bug 14189 today. Although I cannot reproduce it but it happens
randomly. So it looks like not completely fixed.

Comment 10

19 years ago
I think "randomly" is a charitable word. It happens at least 50%
of the time with me. Sometimes text get quoted all right and sometimes
they are broken/corrupted. This applies to Latin 1, JPN, UTF-8, etc.
text body.

Comment 11

19 years ago
Scott, Bug 14189 applies to both IMAP & POP3 mail quoting.
Does your fix here affect POP3, too? I thought this bug was
about IMAP quoting and Rich's and your fix applied only to that.


19 years ago
Blocks: 14356

Comment 12

19 years ago
It's entirely possible that this bug is a dup of 14189 (or vice versa). quoting
for reply and forward runs through the same code for both pop and imap now. To
me, I would think this bug should happen to both the imap and pop case.


19 years ago
Blocks: 11091

Comment 13

19 years ago
(target milestone is M11 or M12 - add to mail beta tracking bug)

Comment 14

19 years ago
I18N: I don't know enough about what's going on here I think. To my ignorant
eyes, this bug and Bug #8405 seem to be the same problem. (Please ignore the
imap specific nature of this bug..I think the problem is in both pop and imap).
Can we mark one as a dupicate of the other? Which one do you think has the
better problem statement? Thanks for the help!

Comment 15

19 years ago
For 8405, I attached a screen shot and the data. The first message contains
Japanese both subject and from address but only subject shows and address is all
truncated (shows only dots), not sure wheather converted wrong or truncated

This bug shows not dots but something like raw UTF-8 string. So looks different
from 8405 but could be the same internally, I am not sure.
I think we better have a screen shot of this too. This is reproducable using the
i18n smoke test. Marina, could you attach a screen shot for this, I cannot
reproduce this bug?

Comment 16

19 years ago
Reviewing this bug at this juncture, it seems to me that the bug
as I described 8/13/99 no longer exists.
HTML quoting of Japanese is OK now. It is certainly not
quoting raw JIS (with all MIME-encodign intact).
There is Forward/inline bug which shows raw B-encoded ISO-2022-JP
headers but that is covered by Bug 17034.
That leaves body corruption in Plain Text mail which is covered by
Bug 15465.
In any case the kind of dichotmy I noted between IMAP and POP mail
in quoting does to seem to exist any more, either.

Unless someone objects, I'm inclined to mark this bug as
a duplicate of Bug 15465 or Worksforme since the problem as dsecribed
originally seems to be gone now.


19 years ago
Last Resolved: 19 years ago
Resolution: --- → DUPLICATE

Comment 17

19 years ago
Marking dup per kat's comments.

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


19 years ago

Comment 18

19 years ago
Verified as a duplicate of multiple bugs.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.