Closed
Bug 383118
Opened 18 years ago
Closed 15 years ago
text broken subject and quoted text when reply attached mail (base64 iso-2022-jp )
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 425455
People
(Reporter: mozilla758+bmo, Unassigned)
Details
Attachments
(2 files, 2 obsolete files)
1.open a attached message of charset iso-2022-jp
2.reply the message
3.open compose window and subject started 're:' and quoted text broken.
attached part of the message sources started
---------------------
Content-Type: message/rfc822;
name="(snip)?ISO-2022-JP?(snip)"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="(snip)?ISO-2022-JP?(snip)"
---------------------
attached original message header have below part.
example 1:(not encoding base64, plain)
---------------------
Content-Type: text/plain; charset=iso-2022-jp
---------------------
example 2:(encoding base64)
---------------------
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: base64
---------------------
I tested below version.
Tb version 3.0a1pre (20070603)
Tb version 2.0.0.0 (20070326)
SeaMonkey Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/2007060302 SeaMonkey/2.0a1pre
3.0a1pre and SeaMoenky 2.0a1pre:text broken something like box except quoted text of example 1.
2.0:Case example 1, subject became 'Re: ?????'(line of question mark) and quoted text is OK. Case example 2, subject became 'Re: ?????'(line of question mark) and quoted text became broken text started 'A:����E�A:���� ��_�9'.
Comment 1•18 years ago
|
||
Can you attach a sample? (The whole thing as an .eml)
Reporter | ||
Comment 2•18 years ago
|
||
Reporter | ||
Comment 3•18 years ago
|
||
Comment 4•18 years ago
|
||
The attached .eml files inside those show up blank to me. And trying to reply to the main mails sets the subject to "Re: "- nothing else. (On tb2.0, linux.)
Reporter | ||
Comment 5•18 years ago
|
||
(In reply to comment #4)
> The attached .eml files inside those show up blank to me. And trying to reply
> to the main mails sets the subject to "Re: "- nothing else. (On tb2.0, linux.)
>
Oh.attached .eml example1 is only made following process:[File]->[Save As]->[File].
and open the file. attached file is blank to me too. that seems to be another bug :P
mmm. How I can make .eml file?
another bug occured both version:
Tb version 3.0a1pre (20070603)
Tb version 2.0.0.0 (20070326)
Reporter | ||
Comment 6•18 years ago
|
||
(In reply to comment #1)
> Can you attach a sample? (The whole thing as an .eml)
>
Please make that mail your self.
compose(charset iso-2022-jp and get Japanese text from www.yahoo.co.jp by copy&paste) mail, and send the mail to yourself. and forward to yourself with also iso-2022-jp text. and open the mail and open attached mail.
Comment 7•18 years ago
|
||
To bug opener:
Can you find already opened bug in dependency tree of meta Bug 269826?
example.1(subject broken) looks for me to be DUP of Bug 314351, if ".eml" file is opened initially.
Reporter | ||
Comment 8•18 years ago
|
||
(In reply to comment #7)
> To bug opener:
> Can you find already opened bug in dependency tree of meta Bug 269826?
> example.1(subject broken) looks for me to be DUP of Bug 314351, if ".eml" file
> is opened initially.
>
Oh. I did't see Bug 269826 yet.
Yes. Problem of reply subject seems to be DUP of Bug 314351. not '.eml' file but message/rfc822 attachment.
Problem of reply quoted text is an another bug.
Reporter | ||
Comment 9•18 years ago
|
||
hmm. Attaching .eml sample is no meen now beacause of Bug 351064.
In Bug 383403 comment 1, Wada says why inline forwarded mail is attached and can open it.
I don't understand whether problem of reply quoted text is bug or not.
If that is bug. I have to make testcase...
Comment 10•18 years ago
|
||
(In reply to comment #9)
Kozawa san, can Bug 383361 have relation to your sample mail? (just fixed today)
> forward msg as attachment has content type text/plain instead of message/rfc822
Reporter | ||
Comment 11•18 years ago
|
||
Attachment #267221 -
Attachment is obsolete: true
Attachment #267230 -
Attachment is obsolete: true
Reporter | ||
Comment 12•18 years ago
|
||
testcase:
1.[Tool]->[Options]->[Composition]->[General]->[Forward messages] set inline.
2.[File]->[Open Saved Mail] .eml file attached this bug.
3.forward mail to me.(new mail subject and body don't have to have non-ascii test).
4.open that mail(after received).
5.open attached mail(ex. duble click).
6.reply the mail
7.quoted body broken.
new testcase file is base64 encoding that have euc-kr text.
Reporter | ||
Comment 13•18 years ago
|
||
reproduced. version 3.0a1pre (20070606).
Comment 14•18 years ago
|
||
(In reply to comment #12)
> 1.[Tool]->[Options]->[Composition]->[General]->[Forward messages] set inline.
> 2.[File]->[Open Saved Mail] .eml file attached this bug.
> 3.forward mail to me.(new mail subject and body don't have to have non-ascii
> test).
> 4.open that mail(after received).
> 5.open attached mail(ex. duble click).
Question again. How can we see inline forwarded mail as "attached mail" (message/rfc822 part) at step4?
Did you test with builds while next bug was alive?
> Bug 376557 – Forward Inline ends up forwarding as attachment
Check mail source after each step, please.
"Save as Draft" and/or "Send Later" is convenient for this purpose.
Note:
If step 3 is executed with "not inline forward", subject is already mangled by Bug 314351 when the attached new .eml file of example 2 is used. Then, when this garbage in subject was kept, and when default character set was iso-8859-1, saving as draft didn't complete after responding OK to prompt for altering to UTF-8 (tb 6/03 trunk build was used). Since garbage is already included in data at this stage, sending in Base64 will possibly occur due to binary data as a result of other bug.
Reporter | ||
Comment 15•18 years ago
|
||
(In reply to comment #14)
Oh mistook.
testcase:
1.[Tool]->[Options]->[Composition]->[General]->[Forward messages] set <<As Attachment>>.
2.[File]->[Open Saved Mail] .eml file attached this bug.
3.forward mail to me.(new mail subject and body don't have to have non-ascii
test).
4.read that mail in message pain(after received).
5.open attached mail(ex. duble click).
6.reply the mail
7.quoted body broken.
new testcase file is base64 encoding that have euc-kr text.
> (In reply to comment #12)
> Question again. How can we see inline forwarded mail as "attached mail"
> (message/rfc822 part) at step4?
sorry. At Step 1 we must set [As Attachment].
and at step 4 we can see attached mail by double click.
> Did you test with builds while next bug was alive?
> > Bug 376557 – Forward Inline ends up forwarding as attachment
reproduced both of version 3.0a1pre (20070606) and Tb2.0.0.0.
that bug seems to be no relation.
Reporter | ||
Comment 16•18 years ago
|
||
Comment 17•18 years ago
|
||
Kozawa san, why don't you analyze problem at Bugzilla Japan first in Japanese?
I think this bug is better to be closed as DUP of Bug 314351, because root problem seems to be Bug 314351, and it seems that subsequent problem after Bug 314351 or related problem to Bug 314351.
Comment 18•17 years ago
|
||
I've only just found this bug after filing bug 425455, where I've attached a minimal test case and instructions for reproduction.
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•