44313 - Need warning dlgbox when From/To/Organization contain data which don't match the chosen encoding

Status: VERIFIED FIXED

(MailNews Core :: MIME, defect, P3)

Description

[Mikhail Khlopotov]

From Bugzilla Helper:
User-Agent: Mozilla/4.73 [en] (Win98; I)
BuildID:    2000062608

If I have "From" which can not be encoded with ISO-8995-1 and I write
a message which utilizes only ISO-8995-1 characters, then my
"From" is being encoded as ISO-8995-1.


Reproducible: Always
Steps to Reproduce:
1. Setup a mail account with non-latin1 user name.
2. Send a message containing only latin-1 chars.
3. See how a message is formed.

Comment 1

[lchiang]

cc: momoi

Comment 2

[Daniel Bratell]

I believe you mean iso-8859-1. (changed summary)

Comment 3

[Katsuhiko Momoi]

Mikhail, I don't think this is really a bug.

What you're doing is the following:

1. Set up a name in non-Latin 1 characters, e.g. Russian.
2. Now when composing a message, select this Russian name
   in the "From: " window.
3. Choose "View | Character Coding" to be Western (ISO-8859-1)
    and type in a Latin 1 characters only.
4. Then send the message.

Under this condition, you will get your Russian name encoded in
ISO-8859-1. In the current Mozilla, we don't use 2 different
character codings for the headers and body. If you set the encoding
in the View menu to ISO-8859-1, the body and the headers will both
go out in ISO-8859-1. 
Perhaps as a new feature in the future, we can allow users to
indicate a separate encoding for the "From:" header. But I seriously
doubt if we need that.

To avoid the problem you're experiencing, please replace the above
step 3 with the one below:

3b. Choose "View | Character Coding" to be Cyrillic (KOI8-R).

I recommend the following default preference setting if 
you're always writing in Russian.

Set "Edit | Preferences | Mail & Newsgroups | Composing Messages | Languages |
      Default Character Coding" to Cyrillic (KOI8-R).

Once you do this, every time you bring up a new Mail composer window,
the Character Coding menu will be automatically set to Cyrillic (KOI8-R)
and this will avoid this kind of problem.

Mikhail, if you agree with this assessment, then please
mark this bug yourself as "invalid".

Comment 4

[Mikhail Khlopotov]

Katsuhiko Momoi,  this is a bug in the mean that if the body of a message 
contains any national characters, then Mozilla will bring up the dialog
indicating that user should select some encoding.   This check should
be applied not only to the body, but to ALL headers as well.  And this is the 
way to fix this bug.

Comment 5

[Katsuhiko Momoi]

Mikhail, thenk you for clarifying this issue.
You're right. We present a warning dialog when the Subject header contains data which
don't match the chosen encoding sending a message. But we don't do that when the "From: "
header contains it. I changed the summary line to reflect this problem more directly.

This seems like Naoki's bug who worked on the warning dialog part.
CC'ing nhotta. I'm also changing the QA contact to myself.

Comment 6

[Katsuhiko Momoi]

This seems to be a duplicate of another bug which deals with "organization" and other
headers.
Hotta-san, please find the other bug.
QA contact to marina.

Comment 7

[nhottanscp]

*** Bug 57042 has been marked as a duplicate of this bug. ***

Comment 8

[nhottanscp]

Added 'intl' keyword and reassign to nhotta.

Comment 9

[nhottanscp]

*** Bug 71769 has been marked as a duplicate of this bug. ***

Comment 10

[marina]

there are two bugs that are marked as dup against this one, though the other two
bugs descriptions are more comprehensive and describe other occurances when we
need warning dglbox to come up, changing the summary

Comment 11

[marina]

the fact that there is no warning dlgbox when the recipient name is in a
different charset brings now another problem in the current builds. If i have
for examle the recipient name in latin-1 charset and the header of my mail is in
Cyrillic i don't get any warning while sending this mail and the result now is
that the mail is not sent to the right recipient, the Latin-1 name is parsed
incorrectly instead of being displayed incorrectly, screen shot to follow.

Comment 12

[marina]

Attachment: here is how the recipient name is parsed when is sent out in a different encoding

Comment 13

[Katsuhiko Momoi]

>  and the result now is that the mail is not sent to the right recipient, 
> the Latin-1 name is parsed incorrectly instead of being displayed incorrectly, 
> screen shot to follow.

Is it true that the message is not sent? Is it not the case that the name is
incorrectly
displayed but the message is delivered?

Comment 14

[marina]

Kat, i guess i have to rephrase what i said above: the message is delivered but
instead of one recipient that would be displayed with ???? we have three names
and if you use them ( by rightclicking) to compose mail the recipient would be
invalid and mail won't be delivered

Comment 15

[nhottanscp]

This is fixed by bug 103313.

Comment 16

[marina]

tested with 2001-11-08 build, when To/From fields have different charset the
warning about charset mismatch comes up