283884 - Alert: Sending of password did not succeed. Mail server 127.0.0.1 responded: Invalid user name or password

Status: RESOLVED EXPIRED

(Thunderbird :: General, defect)

Description

[Louis Pacelli]

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

When I click on "Get Mail" on Mozzilla Thunderbird I receive the following Alert:

Alert: Sending of password did not succeed. Mail server 127.0.0.1 responded:
Invalid user name or password

If I click on "OK" six times it goes away and my new email come in. Everything
that I've tried to do to update of correct my user name and/or password has not
helped make it go away. 

Reproducible: Always

Steps to Reproduce:
1. Click on to "Get Mail" on Thunderbird toolbar.
2. Alert message popsup
3. Click on "OK" six times to make it go away

Actual Results:  
The alert message goes away and I receive my new email messages. 

Expected Results:  
It should just bring in my new email messaged. No alert message.

Comment 1

[Jeongkyu Kim]

Reporter,

It would be helpful if you specify which mail server you have on your local
machine and thunderbird version you use. 

Comment 2

[Louis Pacelli]

(In reply to comment #1)
> Reporter,
> 
> It would be helpful if you specify which mail server you have on your local
> machine and thunderbird version you use. 
> 
Thunderbird version 1.0 (20041206)
Mail server setting is mail.optonline.net Port: 110 default: 110

Comment 3

[Jeongkyu Kim]

(In reply to comment #2)
> [...]
> Mail server setting is mail.optonline.net Port: 110 default: 110

If you don't have local mail server(127.0.0.1), anti-virus software might be
involved in the bug. Do you have any anti-virus or firewall software installed?

By the way, I realized that protocol logs might give more clear idea. If you
don't mind, would you try pop3 logs? Basic information is here.
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#protocol

In my case, I ran following commands to get pop3 logs ( Drag & drop
thunderbird.exe into command prompt to get full path of it ).

C:\>set NSPR_LOG_MODULES=pop3:5
C:\>set NSPR_LOG_FILE=c:\temp\log.txt
C:\>"C:\Program Files\Mozilla Thunderbird\thunderbird.exe"

Comment 4

[Louis Pacelli]

(In reply to comment #3)
> (In reply to comment #2)
> > [...]
> > Mail server setting is mail.optonline.net Port: 110 default: 110
> 
> If you don't have local mail server(127.0.0.1), anti-virus software might be
> involved in the bug. Do you have any anti-virus or firewall software installed?
> 
> By the way, I realized that protocol logs might give more clear idea. If you
> don't mind, would you try pop3 logs? Basic information is here.
> http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#protocol
> 
> In my case, I ran following commands to get pop3 logs ( Drag & drop
> thunderbird.exe into command prompt to get full path of it ).
> 
> C:\>set NSPR_LOG_MODULES=pop3:5
> C:\>set NSPR_LOG_FILE=c:\temp\log.txt
> C:\>"C:\Program Files\Mozilla Thunderbird\thunderbird.exe"
> 
Yes, I have McAfee Virusscan and Personal Firewall installed. Can I disable it
to get around it?

Comment 5

[Jeongkyu Kim]

(In reply to comment #4)
> Yes, I have McAfee Virusscan and Personal Firewall installed. Can I disable it
> to get around it?

Would you try that and see what happen?

Comment 6

[Jeongkyu Kim]

(In reply to comment #5)
> (In reply to comment #4)
> > Yes, I have McAfee Virusscan and Personal Firewall installed. Can I disable it
> > to get around it?
> 
> Would you try that and see what happen?

By the way, this might not be a good idea because it will expose your system to
the security threat. What about trying protocol logs first to see if we can get
useful information?

Comment 7

[WADA:World Anti-bad-Duping Agency]

Reporter, see Bug 213300.

Comment 8

[Gervase Markham [:gerv]]

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/

Comment 9

[Gervase Markham [:gerv]]

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.