After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 242549 - mail subject encoding should be the same of the body
mail subject encoding should be the same of the body
Status: RESOLVED DUPLICATE of bug 224026
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-05-07 23:13 UTC by zic
Modified: 2003-05-09 01:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description zic 2003-05-07 23:13:35 UTC
Package: Evolution
Priority: Major
Version: 1.2.2
Synopsis: mail subject encoding should be the same of the body
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Description of Problem:

In Japan and its language Japanese, for historical reasons,
most mail reader assumes the mail body is encoded in 'ISO-2022-JP'
and the subject is encoded in MIME ISO-2022-JP base64.


But your evolution mailer,
If I select default encoding as ISO-2022-JP and put subject in Japanese
KANJI,
of course, write body in also KANJI,
and then I send it to someone,

the body will be encoded in ISO-2022-JP and
the subject will be encoded as MIME UTF-8 quoted printable,
not MIME ISO-2022-JP base64.

This results subject garbled mail in the recipients' environment.


Steps to reproduce the problem:
1. using evolution mailer, compose a new message to someone
2. write subject and body in Japanese, using default encoding as
ISO-2022-JP
3. send the messsage

Actual Results:
body is encoded in ISO-2022-JP, but the subject(and other headers) is
encoded in MIME UTF-8 quoted printable.

Expected Results:
headers(including subject) also to be encoded as MIME ISO-2022-JP
base64.



How often does this happen?
always


Additional Information:
At the side of the recipient,
when he/she using a legacy mailer(including MS-Outlook or Outlook express, the
latest version),
subject is always garbled,
and probably 3 or 4 times out of 10, the body is also garbled.

I know a few mailer that can handle such mail correctly.
(header encoded in MIME UTF-8 quoted printable, body encoded in
ISO-2022-JP).

The examples of such mailers are, evolution and Becky! Ver.2.
I do not know any other mail reader that can handle such messages
right.
And the worse thing, 9 people out of 10 are using MS-Outlook(or that
family).

So every time I forgot to rewrite the subject in all ASCIIs and respond
the message I received,
I would be told as 'Your message was garbled, please do not use the
mailer(evolution)'.




Unknown reporter: zic-rhn@ontime.venus.to, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Jeffrey Stedfast 2003-05-09 01:25:43 UTC

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