237476 - pop3 login broken. Always replies "Mail server responded: Bad authentication"

Status: RESOLVED DUPLICATE of bug 258077

(Thunderbird :: Account Manager, defect)

Description

[Hugo Elias]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

I have a pop3 mail account. It definitely works, because I can telnet into it,
and use the "user" and "pass" commands to login, and view my e-mail. Also an
application called "poptray" can read mail from this account.

However, whenever I try to use Thunderbird on my machine, or Netscape Mail on
another machine, I am asked for the password, then I get the message: "Sending
of password did not succeed. Mail server mail.btinternet.com responded: Bad
authentication".

Now, this account *used* to work. But BTinternet.com merged with Yahoo.com, and
this problem started.

Is there any way to look at the conversation Thunderbird is having with my mail
server?


Reproducible: Always
Steps to Reproduce:
1. setup new account on Thunderbird with mail server = mail.btinternet.com
2. click "Get Mail"
3. Type in my correct password

Actual Results:  
replies: "Bad authentication"

Expected Results:  
it should have downloaded the mail.

For several years, there was no problem at all. Then our ISP (BT Internet)
merged with Yahoo. As far as I know, this is the only thing that has changed.

Comment 1

[Travis Chase]

Do you still have this problem with the latest version of thunderbird? 

Your password might also be case sensitive.

Comment 2

[Florian Holzinger]

Attachment: [Testcase] Mozilla 1.7.3: ok, Thunderbird 0.8: invalid user/pwd

Same problem here (mailserver: "Ipswitch_IMail_8.0"). Thunderbird 0.8 doesn't
download my mails (logfile: invalid user/pwd) and displays no error message.
mozilla 1.7.3 works. Username/Password is correct. Testcase logfile attached.
Mail me, if you need a temporary account on that server.

Comment 3

[David :Bienvenu]

please try a newer build, thx.

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