I have my SeaMonkey mail account passwords saved in the password manager. When I open mail, it tries to check mail for all my accounts and prompts me for my master password 3 times. I have 2 IMAP accounts + POP3 accounts. If I delete the IMAP accounts, the problem goes away. If I delete the POP3 accounts, the problem remains. Also, if I try to cancel the dialog, I get multiple master password dialogs. This regressed between linux trunk builds 2006051010 and 2006051109, so this is from bug 326273.

I think this may be what I'm seeing with my IMAP accounts since builds for WinXP after 2006050908 - each day I've had to revert back to that build. I am being prompted for my IMAP password many times, but more importantly I don't think the password is being passed properly to the IMAP server - login failures are being racked up and canceling is virtually useless.

I think this is probably a duplicate of bug 338549.

That might be part of what I'm seeing, but I only get one dialog at the start. I can get multiple simultaneous dialogs if I try to cancel.

I have this with 9 POP3-Accounts and one NNTP with Password. I have 10 Password prompts, which pretty much sucks. Wasnt in TRUNK on 20060510, the next one I have from 20060521 has the problem. I dont have builds in between.

Have any of you set mail.check_all_imap_folders_for_new to true, and if so, does it go away or change things if you set it to false? Curiuous because I have a single IMAP account configured and am asked for a password twice, once for the inbox and a second time for checking all the other folders..

I have no IMAP accounts, I get the multiple *masterpassword* prompt for pop3/NNTP-Accounts. Could someone who has the right please change the summary to include pop3/NNTP-Accounts?

if this is brand new, it's still most likely a dup of bug 338549 - the difference might be that you've password protected your password store.

I do not have that many builds in between, but 20050610 was good, 20060521 was the first bad I have.

Does anyone know if there is a workaround to this problem? I haven't been able to use any of the nightly builds since 2006050908. It's hard to believe more people aren't running into this, which makes me think there's something I've set different from everyone else.

Like Darin says, this is basically a dup of bug 338549. It looks like progress is getting made on bug 265780, which is what we're going to use to fix bug 338549. *** This bug has been marked as a duplicate of 338549 ***