Closed
Bug 121926
Opened 23 years ago
Closed 22 years ago
email does not ask for password if it has the wrong one
Categories
(MailNews Core :: Networking, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: juddrogers, Assigned: naving)
References
Details
(Whiteboard: [adt1 rtm])
Attachments
(1 file, 2 obsolete files)
5.54 KB,
patch
|
Bienvenu
:
review+
mscott
:
superreview+
jud
:
approval+
|
Details | Diff | Splinter Review |
I started mailNews for the first time with build 20011122106. I normally use netscape 4.7. mailNews picked up all the accounts just fine but got the wrong password. mailNews tells me it can't log on to the mail server -- does this twice. Never asks for the password. After mailNews shuts up I click on some mail folder other than inbox and mailNews asks for the password. All is right with the world.
Comment 1•23 years ago
|
||
Confirmed on build 2002020516 (Solaris moz0.9.8). This may be related to bug 63633. Because of this problem, I went to the Password Manager just to find that it had only web passwords and not email passwords listed! Looks like a 1.0 stopper to me...
Comment 2•22 years ago
|
||
I believe I am seeing the same bug in Mac OS X build 2002030108. I am having this problem with an IMAP account. I entered the wrong password, and now do not get a prompt to re-enter -- I get a sheet (dialog) that says the login failed. This repeats 4 times, and then stops. I never get a chance to re-enter the password.
Comment 3•22 years ago
|
||
I can reproduce this bug with 2002032921/Linux. Confirming.
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows NT → All
Comment 4•22 years ago
|
||
I can reproduce this with Windows 2000, build 2002041711, and a pop account. The exact answer trying to get the mail is: The PASS command did not succeed. Mail server <servername> responded: [AUTH] Password supplied for "<username>" is incorrrect. Up to now I did not find a way to reenter the password. I think this is a very serious bug!
Comment 5•22 years ago
|
||
Doesn't this look like bug #94775?
Comment 6•22 years ago
|
||
*** Bug 138815 has been marked as a duplicate of this bug. ***
*** Bug 139679 has been marked as a duplicate of this bug. ***
*** Bug 133851 has been marked as a duplicate of this bug. ***
Comment 10•22 years ago
|
||
*** Bug 139819 has been marked as a duplicate of this bug. ***
Comment 11•22 years ago
|
||
In just a couple of days these bugs bave been filed on the issue: bug 138815, bug 139679, bug 133851, bug 139819, bug 139973 and bug 139981 Some are POP issues. The timespan between this bug being reported, and the "new ones" - and not least the amount of them, may indicate a newer regression than this bug? It's becoming a major problem and usability issue, as some users now have to kill mozilla to get out of the loop.
Comment 12•22 years ago
|
||
*** Bug 142486 has been marked as a duplicate of this bug. ***
Comment 13•22 years ago
|
||
Confirm with Debian woody/i386 mozilla build 0.9.9-4 (old-ish, I know...) exactly as described in #4. If the mozilla is told to remember the password, it will never ask for it even when it is incorrect. The password _is_ listed in password manager, so suggested workaround is delete password from password manager and either (1) don't use remember password or (2) be very sure you type it right. Also confirm exact same problem with rc1 off mozilla.org
Comment 14•22 years ago
|
||
I can confirm this bug is still alive and well in build number 2002051104. I had to delete the entry from the Password Manager before it would even ask me for a new password. And even after I had entered the new password, I needed to shut down the mail client (left hand pressing return -- to clear the error message, right clicking the mouse keys franticly) before it would work. This bug cropped up after several weeks of error free computing, where in I connecte daily to my ISP's mail server.
Comment 15•22 years ago
|
||
*** Bug 145125 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 16•22 years ago
|
||
I believe all these are dups pop/imap. I'm working on it.
Assignee: mscott → naving
Assignee | ||
Comment 17•22 years ago
|
||
*** Bug 140274 has been marked as a duplicate of this bug. ***
Assignee | ||
Updated•22 years ago
|
Assignee | ||
Comment 18•22 years ago
|
||
This was a regression caused bug bug 113540. The fix is to make sure we are creating services for password manager category. One of the services is nsIWalletService that needs to be created for mailnews passwords to work correctly. patch upcoming that does this.
Assignee | ||
Comment 19•22 years ago
|
||
See last comment by me for an explanation of the fix.
Assignee | ||
Comment 20•22 years ago
|
||
David, can I get r=? thx.
Comment 21•22 years ago
|
||
how come the wallet service isn't loaded as a result of getting the password out of it to send to the server in the first place?
Assignee | ||
Comment 22•22 years ago
|
||
Because it doesn't need walletService, we use nsIAuthPrompter.
Assignee | ||
Comment 23•22 years ago
|
||
We can pass nsnull for origin to NS_CreateServices... because it doesn't use it.
Comment 24•22 years ago
|
||
I don't understand. So we don't need the wallet service to retrieve passwords from the password manager, but we need the wallet service when a logon fails?
Comment 25•22 years ago
|
||
I see that there's other code doing this (the forms code). It still seems weird. In any case, could you actually check the return value of CreateServicesForPasswordManager(and return the result of NS_CreateServicesFromCategory...)
Assignee | ||
Comment 26•22 years ago
|
||
Most of the times the passwords are stored and we don't create WalletService if we are successful in logging in. That is what happens most of the time. If the stored passwords fail because the password has been changed using some other client or like yahoo pop3 server is denying access to foreign clients, then we need to create wallet service for "login-failed" notification. Other interfaces are used, I have seen in the debugger singsign etc. They (performance grp) made walletService to be created lazily because of start-up performance and they added RegisterProc and UnregisterProc to WalletService for this to happen dynamically, like from form manager.
Assignee | ||
Comment 27•22 years ago
|
||
Attachment #84333 -
Attachment is obsolete: true
Attachment #84349 -
Attachment is obsolete: true
Comment 28•22 years ago
|
||
Comment on attachment 84360 [details] [diff] [review] patch -checking for return code r=bienvenu
Attachment #84360 -
Flags: review+
Comment 29•22 years ago
|
||
Comment on attachment 84360 [details] [diff] [review] patch -checking for return code r=bienvenu
Comment 30•22 years ago
|
||
Comment on attachment 84360 [details] [diff] [review] patch -checking for return code I'm worried about the static global variable. Recently those have been causing trouble for issues like turbo where a restart doesn't cause static variables to get cleared out. Will that be a problem here?
Assignee | ||
Comment 31•22 years ago
|
||
That should be okay here because we don't release/free services on turbo exit.
Comment 32•22 years ago
|
||
I was under the impression that some services like wallet in particular which cache security information are cleared out over session-logout's..
Assignee | ||
Comment 33•22 years ago
|
||
good point, let me verify.
Assignee | ||
Comment 34•22 years ago
|
||
We are not releasing walletService on turbo exit. I have seen this in debugger and also if you look at nsWalletLibService::Observer, it doesn't listen for "session-logout" topic. Even it holds cache security information it will have to just clear out on session-logout topic, but the service will still be there. There is no need to free service from security point of view, IMO.
Comment 35•22 years ago
|
||
Comment on attachment 84360 [details] [diff] [review] patch -checking for return code thanks for investigating Navin. sr=mscott
Attachment #84360 -
Flags: superreview+
Assignee | ||
Comment 36•22 years ago
|
||
fixed.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 37•22 years ago
|
||
*** Bug 146323 has been marked as a duplicate of this bug. ***
Comment 38•22 years ago
|
||
*** Bug 139981 has been marked as a duplicate of this bug. ***
Comment 39•22 years ago
|
||
*** Bug 146961 has been marked as a duplicate of this bug. ***
Comment 40•22 years ago
|
||
*** Bug 146961 has been marked as a duplicate of this bug. ***
Comment 41•22 years ago
|
||
Not being able to re-enter a password was showing up as a top issue from PR1.
Comment 42•22 years ago
|
||
adding adt1.0.1+ for checkin to the 1.0 branch. Please get drivers approval before checking in. David, would you be able to ask for drivers approval and land this if it's given?
Updated•22 years ago
|
Attachment #84360 -
Flags: approval+
Comment 43•22 years ago
|
||
please checkin to the 1.0.1 branch ASAP, and replace the mozilla1.0.1+ bug with fixed1.0.1 once it's landed there.
Keywords: mozilla1.0.1+
Comment 45•22 years ago
|
||
*** Bug 147872 has been marked as a duplicate of this bug. ***
Comment 46•22 years ago
|
||
*** Bug 138801 has been marked as a duplicate of this bug. ***
Comment 47•22 years ago
|
||
*** Bug 138815 has been marked as a duplicate of this bug. ***
Comment 48•22 years ago
|
||
It looks like this bug has been marked as fixed, correct me if I'm wrong. I just need to let everyone know that my problem is NOT fixed and I still cannot use Mozilla mail (I've been using Pegasus 4.01 since first reporting my problem). To reiterate my problem: When I try to send mail, Mozilla prompts me over and over and over again for my SMTP password. It'll keep requesting it for as long as I care to type it in and hit enter. When I finally give up, I get a window displaying the following obvious message: "Sending of message failed. The message could not be sent because connecting to the SMTP server failed. The server may be unavailable or is refusing SMTP connections. Please verify that your SMTP server setting is correct and try again, or else contact your network administrator." This behavior started right around the time Mozilla 9.9 came out though I cannot be more specific than that. I know it was right around the end of February so if that is when Mozilla released the new 9.9 version, that is when it began. I've changed my password several times trying to find a work around to no avail. Pegasus works fine and is a very nice app but it's not what I'd prefer to use if I had a choice. Hopefully, someone can track this down and fix it soon. P.S.: I'm running release candidate #3 now.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 49•22 years ago
|
||
*** Bug 140403 has been marked as a duplicate of this bug. ***
Comment 50•22 years ago
|
||
*** Bug 142787 has been marked as a duplicate of this bug. ***
Comment 51•22 years ago
|
||
*** Bug 129085 has been marked as a duplicate of this bug. ***
Comment 52•22 years ago
|
||
The fix is apparently checked into 1.0.1, but not 1.0. It's likely that once you install 1.0.1, your SMTP problem will be fixed. If not, please post another comment here.
Comment 53•22 years ago
|
||
*** Bug 127855 has been marked as a duplicate of this bug. ***
Comment 54•22 years ago
|
||
*** Bug 148293 has been marked as a duplicate of this bug. ***
Comment 55•22 years ago
|
||
*** Bug 148237 has been marked as a duplicate of this bug. ***
Comment 56•22 years ago
|
||
*** Bug 145627 has been marked as a duplicate of this bug. ***
Comment 57•22 years ago
|
||
*** Bug 134578 has been marked as a duplicate of this bug. ***
Comment 58•22 years ago
|
||
marking fixed again based on comments that RC3 was being used whereas this was landed in 1.0.1 and the trunk.
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
Comment 59•22 years ago
|
||
Besides Jim said that Mozilla prompts for the password...
Comment 60•22 years ago
|
||
Proposed relnote: If a user types in a wrong password for e-mail and stores the wrong password in password manager, Mozilla will not prompt the user to type in a new, correct password. Workaround: go to Edit | Preferences | Privacy & Security | Passwords | Manage Stored Passwords. Remove the appropriate entries for the mail servers. Then, the next time the user accesses e-mail, he will be prompted for a new password. This problem is fixed in Mozilla version 1.0.1.
Keywords: relnote
Comment 61•22 years ago
|
||
*** Bug 146332 has been marked as a duplicate of this bug. ***
Summary: email does not ask for password if has wrong one → email does not ask for password if it has the wrong one
Comment 62•22 years ago
|
||
I'll wait to see what comes with version 1.0.1 but most of the comments here bear no resemblence to what happens to me at all. I tried the workaround just posted and got precisely the same results... I get prompted over and over and over and over and over and over and over for my password (until I give up). I have to repeat that I *know* my password (use it everyday with Pegasus mail). I don't think it's got much to do with whether or not Mozilla remembers my password correctly or not. But, as I said, I'll wait to see what the future brings.
Comment 63•22 years ago
|
||
Jim Your problem sounds like a completely different issue to me, unrelated to this one. Why don't you post it as a new bug, rather than trying to reopen this one that is apparently fixed. It would be usefull if you said what SMTP server you where using. Just a thougth does you SMTP server need a password to send mail, most don't. Try turning of the SSL in the mail and news settings dialog box for your outgoing SMTP server. If that dosn't work start a new bug. HTH Ian
Comment 64•22 years ago
|
||
After reading Ian's note, I took another look through the SMTP client settings. SSL was already set to "when possible" so I left that alone. The "Use Name and Password" was checked, however. I removed the checkmark, shutdown and restarted Mozilla and am again able to send mail. Thanks to all who hung in there with me and to Ian especially. I'm very grateful.
Comment 65•22 years ago
|
||
*** Bug 150531 has been marked as a duplicate of this bug. ***
Comment 66•22 years ago
|
||
*** Bug 152559 has been marked as a duplicate of this bug. ***
Comment 67•22 years ago
|
||
After confirmed with Navin & Cavin. Verified fix along with bug 94775 and today's verification on all the platforms as following: Win 06-20-08-1.0 Linux 06-20-06-1.0 Mac 06-20-05-1.0 Marking as verified and changing keywords to "verified 1.0.1"
Status: RESOLVED → VERIFIED
Keywords: fixed1.0.1 → verified1.0.1
Assignee | ||
Comment 68•22 years ago
|
||
*** Bug 156635 has been marked as a duplicate of this bug. ***
Comment 69•22 years ago
|
||
*** Bug 157916 has been marked as a duplicate of this bug. ***
Comment 70•22 years ago
|
||
*** Bug 161345 has been marked as a duplicate of this bug. ***
Comment 71•22 years ago
|
||
*** Bug 161902 has been marked as a duplicate of this bug. ***
Comment 72•22 years ago
|
||
*** Bug 166623 has been marked as a duplicate of this bug. ***
Comment 73•22 years ago
|
||
*** Bug 131587 has been marked as a duplicate of this bug. ***
Comment 74•22 years ago
|
||
This bug seems to have reappeared in Mozilla V1.2.1. I have entered a new report as bug# 190806
Comment 75•20 years ago
|
||
*** Bug 195844 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: MailNews → Core
Comment 76•18 years ago
|
||
As we still have this problem with Mozilla 1.7.13 and Thunderbird 1.0.4 I did some more research. It seems that the fix in comment #12 does not fix it in all possible cases. What I worked out so far using Mozilla 1.7.13: When the mail account has "check for new messages at startup" disabled on the server settings page, the fix works ok. After opening mail and selecting the inbox, first the message about failed login appears, with an OK box, and when that is clicked a new password entry box appears where the correct password can be typed and it can be stored. OK. HOWEVER: when "check for new messages at startup" is enabled, the above does NOT happen! The program attempts to open the inbox automatically, and one gets two login failed dialogs which can be OK'ed away, but NO password box. Any further action on the mail account causes another login failed but still no possibility to enter the password. Maybe the "check for new messages at startup" causes the start of the services to be called too early, and they cannot be successfully started. The only available workaround still is to remove the password using the password manager, and try again. Unfortunately the password manager has moved even further away from the user's view in Thunderbird, so it is even more difficult for our helpdesk to explain to people how to do this over the phone.
Comment 77•18 years ago
|
||
please try a trunk or 2.0 nightly TB or Seamonkey build - I believe this is fixed in those builds.
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•