Closed Bug 271688 Opened 20 years ago Closed 19 years ago

Cannot authentificate at POP3 Server if username is something like mike@mike.meyers.name

Categories

(Thunderbird :: Account Manager, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mailinglist, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I have been using Mozilla-Mail and different versions of Thunderbird.
I have several E-mail accounts at Networksolutions, some of them with normal
domain names and some .name domains.
The Problem is now that I cannnot anymore authentificate to get the emails from
the .name accounts. I get the error message from Thunderbird "Sending of login
failed, Mailserver responded: Invalid login". I am sure that the login data and
configuration is correct - the retrieval of mails still works with Mozilla Mail
with exactly the same setup.

The problem might lie behind the format of the login. While the "normal" domains
 have usernames like "john@example.com", the .name account loginnames have the
format "john@john.meyers.name".


Reproducible: Always
Steps to Reproduce:
1. Set up account with .name account at Networksolutions (Example:
Servername="mail.john.meyers.name", username="john@john.meyers.name"
2. Klick on "Get Mails"
3.

Actual Results:  
Error box from Thunderbird "Sending of password did not succeed. Mailserver
mail.john.meyers.name responded: Invalid login"
Summary: Cannot authentificate at POP3 Server if username is something like mike@mike.name.com → Cannot authentificate at POP3 Server if username is something like mike@mike.meyers.name
This does not seem to be a security vulnerability so removing the
"security-sensitive" designation.
Group: security
(In reply to comment #0)
> The problem might lie behind the format of the login. While the "normal"
> domains  have usernames like "john@example.com", the .name account loginnames
> have the format "john@john.meyers.name".
> 
> Reproducible: Always
> Steps to Reproduce:
> 1. Set up account with .name account at Networksolutions (Example:
> Servername="mail.john.meyers.name", username="john@john.meyers.name"

So for the "normal" domain logins, are the usernames format with the @ or just 
with the username ("john") part?

xref bug 216290.
WORKSFORME.
My username of my provider is accountname@subdomain.domain.ne.jp format (both
POP3 and SMTP) and is working well from beginnig of my Mozilla use(Mile Stone 17) .

I saw a bug of same complaint as you in the past ;
 - He paseted text of username to Mozilla's UI panel from some where.
   But a space is included after username on copy, this becomes wrong username.
Similar case?
See prefs.js in your profile directry and find next line(s). 
   user_pref("mail.server.serverNN.realuserName", "user-xx "); (If changed)
or user_pref("mail.server.serverNN.userName",     "user-xx "); (If not changed)
Is this set as you expected?
Philipp Ebneter, please respond to comment 2 and comment 3.
I have run into the same problem.  It was not present in versions up to about
0.5 (I think) and started showing up after that.  It is present whether the
client runs on Mac, Windows or Linux.  It is probably due to a different
handling of escape characters in latter versions of Thunderbird.
(In reply to comment #2)
> (In reply to comment #0)
> > The problem might lie behind the format of the login. While the "normal"
> > domains  have usernames like "john@example.com", the .name account loginnames
> > have the format "john@john.meyers.name".
> > 
> > Reproducible: Always
> > Steps to Reproduce:
> > 1. Set up account with .name account at Networksolutions (Example:
> > Servername="mail.john.meyers.name", username="john@john.meyers.name"
> 
> So for the "normal" domain logins, are the usernames format with the @ or just 
> with the username ("john") part?
> 
> xref bug 216290.

The "normal" user names also have the @ in the login-name.
(In reply to comment #3)
> WORKSFORME.
> My username of my provider is accountname@subdomain.domain.ne.jp format (both
> POP3 and SMTP) and is working well from beginnig of my Mozilla use(Mile Stone
17) .
> 
> I saw a bug of same complaint as you in the past ;
>  - He paseted text of username to Mozilla's UI panel from some where.
>    But a space is included after username on copy, this becomes wrong username.
> Similar case?
> See prefs.js in your profile directry and find next line(s). 
>    user_pref("mail.server.serverNN.realuserName", "user-xx "); (If changed)
> or user_pref("mail.server.serverNN.userName",     "user-xx "); (If not changed)
> Is this set as you expected?
> 

yes, the 
    user_pref("mail.server.serverNN.realuserName", "user-xx")
seemed to be correct
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.