Downloaded a new build today (2002120708, Win98) and Mozilla always sends "foo0heCh" as my password, without asking me what my password is. (I checked that using a network sniffer). This both happens for my IMAP Account and my NNTP Account (the NNTP one has a saved password...) For both accounts, the username was saved.

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

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

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

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

happens in 2002120604 as well

ah yeah, note about my "nntp account" comment: While I do have a password for it saved, it is not the one mozilla sends, of course :)

Works in 2002120108 Does not work in 2002120308 will check 20021202

works in 2002120208

checkins in this timeframe: http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=MozillaTinderboxAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=12%2F02%2F2002+08%3A00&maxdate=12%2F03%2F2002+08%3A00&cvsroot=%2Fcvsroot

er no, the last few comments are wrong... let me test this stuff again.

OK, so this works in builds up to: 2002120508 (and also in the SVG build from that day) Does not work in 2002120604

it's also broken in SPARC/Solaris build 2002120822. Using the hints of a bonsai URL and Christian's narrowing of the timeframe, I'd blame the line 721 MsgGetMessagesForAllServers(defaultServer); in file mozilla/mailnews/base/resources/content/msgMail3PaneWindow.js version 1.224 at 12/05/2002 11:17

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

What does it mean (well what causes it) to get a red background with the message "You are not authorized to access bug #184436." ? If access is restricted because it's a security bug, would it be better to make this bug a dependency of it, but leave this bug open so we can see patches, and when it is marked fixed? At the moment, I don't want to download another nightly build until this bug has gone away.

it is a security bug... what do you mean with seeing patches? they are on that other bug.. note that it does have a patch, and reviews too. I expect that it will be checked in later today.

I guess I meant I'd like to see a report that the patch has been applied. Will it be reported back to this bug that bug #184436 has been fixed? This is the first time I've encountered a bug I'm not allowed to see.

Scott: No, it will not really be reported back. However, that bug has been fixed just now. In addition, the bug was made publically visible, so you can read the report for yourself.

Thanks. I'll try the next nightly build. I'm glad someone else could work out that these two were related. They don't sound too close to me!