205933 - Login to our MS Exchange Server failed

Status: RESOLVED DUPLICATE of bug 312593

(MailNews Core :: Networking: IMAP, defect)

Description

[Christian Stöber]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

We are using "Microsoft Exchange Server (IMAP4rev1, Version 5.5.2653.23
(exchange.local))" and when Mozilla MailNews try to login with my username, I
specified in the account settings, the login to our server fail. My username is
"c_stöber", and it seems that Mozilla MailNews is not able to handle the "ö" in
my username, because with an other mail-client, Evolution v1.2.4, it works. And
I try an other account without any special character like "äüö", and it works too.


Reproducible: Always

Steps to Reproduce:
1. Create my IMAP-Account
2. Try to connect to Server by clicking on my INBOX-Folder
3. Entering my password

Actual Results:  
Login abort, with following message:
Login to Server XXXX failed

Expected Results:  
Mozilla should show my folders.

Comment 1

[u63580]

This could be a dupe of bug 150012 - again about special characters

Comment 2

[David :Bienvenu]

I don't think bug 150012 is related - did you really mean that bug? Can you send
me your prefs.js so I can see if we're somehow storing the user name
incorrectly? thx!

Comment 3

[Christian Stöber]

Sorry,

I see that the german special characters are replace by an "?", in ascii-code I
mean, 129, 132, 148, and so on.

Comment 4

[David :Bienvenu]

Christian, could you be more specific? Where is this replacement happening? What
exactly do the before and after strings look like?

Comment 5

[u63580]

Sorry, meant 150014 - typo!

Comment 6

[David :Bienvenu]

I don't suppose anyone could give me temporary access to such an account that
doesn't work? Unfortunately, we don't put the username in the imap protocol log
so I can't tell from a log what's going wrong.

Comment 7

[David :Bienvenu]

I see that prefs.js doesn't have the correct user name, probably because of
problems sending the chars through JS or the xpconnect idl stuff. I'm not sure
how we should handle this - I think the prefs.js stuff has ways of handling
special chars; perhaps we're just not using it.

Comment 8

[David :Bienvenu]

so, I talked to Alecf about this - apparently, xpconnect isn't happy with non
7-bit characters. So, what we need to do is use unicode strings though
xpconnect, and the prefs code will utf-8 encode and decode the prefs strings.
Then, we need to convert the utf8 to whatever imap wants (probably unicode and
then remove the high byte). We will have an upgrade problem, converting old user
name prefs from ascii to utf8. I think some 8 bit characters make it through
xpconnect, but some do not (I could be wrong about that - I should probably test
that). If they do, however, we'll need to check a one-time special upgrade pref
- if not set, we'll need to upgrade the user names to utf8, and then set the pref.

Comment 9

[David :Bienvenu]

However, I think "c_stöber" survives intact the round-trip to prefs.js, at least
on my machine, so I'm curious exactly what you see in prefs.js for your imap
server user name.

Comment 10

[Christian Stöber]

@[e-mail]

I will send you my prefs.js tomorrow.

Christian

Comment 11

[Wayne Mery (:wsmwk)]

David, Christian's email address is dead.

Comment 12

[Wayne Mery (:wsmwk)]

david, WFM or wontfix?

(In reply to comment #8)
> so, I talked to Alecf about this - apparently, xpconnect isn't happy with non
> 7-bit characters. So, what we need to do is use unicode strings though
> xpconnect, and the prefs code will utf-8 encode and decode the prefs strings.
> Then, we need to convert the utf8 to whatever imap wants (probably unicode and
> then remove the high byte). We will have an upgrade problem, converting old user
> name prefs from ascii to utf8. ...

Comment 13

[Chris Newman]

Looks like a duplicate of bug 312593 which has more technical discussion.