"Sending authenticate login information..." is poor wording. As I understand it, we're doing an IMAP login and authenticate but the phrase "authenticate login" doesn't make any sense. We should either just say "Sending login information" or "Authenticating" I believe that the string lives in http://lxr.mozilla.org/seamonkey/source/mail/locales/en-US/chrome/messenger/imapMsgs.properties#128

That phrase is pretty geeky. How about using the same phrase we do for a non auth login David, which is: "Sending login information..."

I love "Sending login information..." :D

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

putting in the tb 2 bug bucket

My mistake, I missed this bug when I was getting all the strings in for the l10n string freeze. I still think it would have been a good change :(. Axel, is it ok to improve the english translation for a string after the string freeze? We wouldn't be changing the meaning, just improving the wording. It's not worth trying to make sure it gets fixed for each localization after the l10n freeze, so if Axel says no, I'll just bump this to Thunderbird 3 and we'll get it there.

I'd actually think that the translated strings don't suck as bad as the English one does, at least they look more verbose and less cryptic than the English string feels to me. Catch up, dude ;-), and post to .l10n? No key change danger around, IMHO. 5014 is an interesting key name, too.

What's the difference between these two strings anyway? Does it really matter if you're doing InsecureLogin or AuthLogin? 5013=Sending login information... 5014=Sending authenticate login information... Maybe you can just use the 5013 string in both cases.

On the trunk, I think it eventually makes sense to collapse the string for IMAP_STATUS_SENDING_LOGIN and IMAP_STATUS_SENDING_AUTH_LOGIN into a single string since right now in en-US they have the same value. But I don't want to do that on the branch. It makes assumptions about how localizers may have localized those strings. Let's just improve the wording for en-US as mentioned earlier. When this lands I'll also post to l10n, although I suspect that most of the localizations already have a better string here than we do :)

Comment on attachment 252943 [details] [diff] [review] improve the en-us string I'll post to l10n too.

While I agree that "Sending authenticate login information..." is too geeky, why not consider "Sending secure authentication..." ? After all, the checkbox that enables the feature is labelled "Use secure authentication".

Sync' with (SeaMonkey) bug 368618, "per" comment 10 ... Distinguish between 5013 and 5014 messages.

Comment on attachment 285865 [details] [diff] [review] (Bv1) Add "secure" I actually prefer the string I added in this bug and not this new one. If you want to work on this bug, the remaining work is to implement my suggestion in comment 8 for the trunk...

(In reply to comment #12) > If you want to work on this bug, the remaining work is to implement my > suggestion in comment 8 for the trunk... Filed bug 408821.