235841 - Unable to send UTF-8 messages

Status: RESOLVED DUPLICATE of bug 234597

(MailNews Core :: Composition, defect)

Description

[Troodon]

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.5) Gecko/20031007

Mail&News stucks when sending UTF-8 messages with "mixed" characters from
multiple languages (i.e. latin and cyrilic) at the send progress window
("Sending mail").
This doesn't happens when in Options->Format I change the default option
("Autodetect") to another one.

Reproducible: Always
Steps to Reproduce:




This does NOT happen in Mozilla 1.5. The problem appeared in 1.6 and it still
exists in the lasted build - 2004022608.

Comment 1

[Jean-Marc Desperrier]

Can not reproduce with mixed french japanese.

Did you get the warning that the selected encoding is inappropriate and saying
Mozilla will sent your mail in UTF-8 instead ? 
This should happen after the "Assembling mail" windows appears.

Try to find anything else that can be special about your configuration.
Test on a fresh profile.

Comment 2

[Troodon]

I don't get any warning message, because I have set UTF-8 as the default encoding.

Comment 3

[Mike Cowperthwaite]

Troodon: How do you compose these mixed-language messages?  Using the CharMap 
program?

What exactly is the problem?  I don't understand "stucks"; do you mean Mozilla 
"gets stuck" -- that it freezes?

Comment 4

[Jungshik Shin]

You're NOT supposed to send emails with two character encodings mixed. Mozilla
would never allow that. 

How do you get such a message in the first place? In fr.*Japanese newsgroup?
Please, evangelize people there to use UTF-8 if they want to use French and
Japanese in a single news posting. If they use a good i18nized mail/news client
like Mozilla/Thunderbird, they can't never commit such a hineous crime of mixing
two character encodings in a single news posting.

Comment 5

[Troodon]

(In reply to comment #3)
> Troodon: How do you compose these mixed-language messages?  Using the CharMap 
> program?
>

I'm using Windows and its multi-language support, so with a key combination I
can change the language (keyboard/font) I type in.

> What exactly is the problem?  I don't understand "stucks"; do you mean Mozilla 
> "gets stuck" -- that it freezes?

This it what happens:
- I write the message and press "Send".
- The "Sending messages" window appears, the progress bar grows a bit, then in
the status appears "Sending message" and nothing more happens. This is why is
say it "stucks", because Mozilla doesn't freeze, as it continues to respond and
works normally (I cand press the "Cancel" button and close the message).



(In reply to comment #4)
> You're NOT supposed to send emails with two character encodings mixed. Mozilla
> would never allow that. 
> 

I don't mean two charsets in the same message but CHARACTERS from different
charsets in the same message (see my initial description).

> How do you get such a message in the first place? In fr.*Japanese newsgroup?
> Please, evangelize people there to use UTF-8 if they want to use French and
> Japanese in a single news posting. If they use a good i18nized mail/news client
> like Mozilla/Thunderbird, they can't never commit such a hineous crime of mixing
> two character encodings in a single news posting.
> 

Using characters from different chrasets in the same message it's something I
need for my work. I.e. I get a cyrilic message and I need to send it to someone
else adding a latin text or I just need to send a message with a cyrilic part
and a latin part. And as I said, I'm using UTF-8 as my default enconding.

Comment 6

[Jungshik Shin]

> I don't mean two charsets in the same message but CHARACTERS from different
> charsets in the same message (see my initial description).

Gee, then, you're just using a *single* coded character set (Unicode) and a
single character encoding form (UTF-8) for that character set. 

What you put in the summary line is not technically wrong, but nobody would
describe that way so that I was confused. 

Anyway, I can't reproduce your problem. I've just sent an email with Chinese,
Korean, Japanese, Thai, Devanagari, Tamil, Cyrillic, Latin letters altogether. 

Comment 7

[Troodon]

Tried on another computer, and it seems to work. Mayble it's profile-related
problem (can't check right now), so let's mark this as invalid.
Thank you to all who commented/checked.

Comment 8

[Jungshik Shin]

> The "Sending messages" window appears, the progress bar grows a bit, then in
> the status appears "Sending message" and nothing more happens. This is why is
> say it "stucks", because Mozilla doesn't freeze, as it continues to respond and
> works normally (I cand press the "Cancel" button and close the message).

This symptom is very similar to what I and others reported in bug 234597.  Can
you just turn off the option to send 8bit characters encoded in quoted-printable
in Edit | Pref | Mail&News | Composition and try again? If turning off that
option solves your problem, this is a dupe of bug 234597. (we have to mark as
such instead of marking it invalid)

For an unknown reason, I can't trigger the bug in Mozill-mail. As far as I can
tell, both Mozilla-mail and TB use the same method to determine which C-T-E to
use, QP or Base64 when the option is turned on. Somehow, Mozilla-mail never uses
Base64 even if there are enough 8bit characters that using Base64 is
space-saving   (but you may find a way to get Mozilla to do just that...)  TB
does what I expect (that is, it uses Base64 if the proportion of 8bit characters
in a message is higher than a certain value.) However, unfortunately, this leads
to bug 234597 (see bug 234597 comment #1). 

Comment 9

[Troodon]

(In reply to comment #8)
> This symptom is very similar to what I and others reported in bug 234597.  Can
> you just turn off the option to send 8bit characters encoded in quoted-printable
> in Edit | Pref | Mail&News | Composition and try again? If turning off that
> option solves your problem, this is a dupe of bug 234597. (we have to mark as
> such instead of marking it invalid)

Yes! That solved the problem, thanks! Thus, I'm marking this as a dupe.
 
> For an unknown reason, I can't trigger the bug in Mozill-mail. As far as I can
> tell, both Mozilla-mail and TB use the same method to determine which C-T-E to
> use, QP or Base64 when the option is turned on. Somehow, Mozilla-mail never uses
> Base64 even if there are enough 8bit characters that using Base64 is
> space-saving   (but you may find a way to get Mozilla to do just that...)  TB
> does what I expect (that is, it uses Base64 if the proportion of 8bit characters
> in a message is higher than a certain value.) However, unfortunately, this leads
> to bug 234597 (see bug 234597 comment #1). 

As I said in comment #1, even with the quoted-printable option marked if in the
composition window, in Options->Format I select Rich text (HTML) or Plain text
and rich text it doesn't happen but if I select Autodetect or Plain text only it
happens. Maybe this has something to do?

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