70841 - "Get All New Messages" doesn't do that

Status: VERIFIED INVALID

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[David Iwancio]

Opening the pull-down menu from the Get Msg button and selecting "Get All New
Messages" only downloads messages from the currently highlighted account.

Comment 1

[racham]

Have you logged into other accounts that you want to get messages for ? 'Get All
New Messages' gets messages for all those accounts who have been authenticated
i.e., password avaiable for that session.

Please explain the scenario on your end..

Comment 2

[David Iwancio]

Let me make sure I have this:  I have the passwords remembered for both
accounts, but neither of them have "Log into this account at startup of Mail"
selected.  Becasue of that, I need to log into the accounts by clicking "Get
Msgs" for each account individually before "Get All New Messages" works for both
accounts?

I have two different mail servers, mail.lig.bellsouth.net and smtp.db.erau.edu,
each with their own set of folders (inbox, drafts, etc), as well as the Local
Folders set.  There are two different news servers (the local one and
news1.lig.bellsouth.net), but no subscribeed newsgroups.  They are all listed in
that order, and the logins and passwords for all accounts are remembered.

Comment 3

[racham]

David,

I just verified to see if this regression is real. I couldn't reproduce it. I
always got messages for the accounts which have password available in a given
session. Adding Sheela so that see can also try out couple of cases.

If you authenticate a particular account (process of providing password) either
because of login at startup option (btw, it is now called as 'Check mail at
startup') or by doing it manually (like clicking on get message button), that
account now is eligible to get messages when 'Get All New Messages' is
clicked/chosen.

Can you confirm that both these servers were active and could be contacted at
the time of the testing ? 

BTW, as per the news accounts concerned, I haven't implemented the functionality
mentioned in the spec i.e., to update message count. I will file a separate bug
on that.

Comment 4

[Sheela Ravindran]

change qa contact to myself
Reporter,
which build are you using? What accounts are they? imap or pop? Do you see the
same problem when you do Get Messages for All from the File/menu item?

Comment 5

[Sheela Ravindran]

Bhuvan,
Finally, I was able to reproduce this. Below are the steps to reproduce this. 
commercial Buildid: 2001030505 on linux
-make sure you have saved the password for two accounts in the password manager.
-Launch browser with an existing profile with more than one account. My first
account in the profile is pop account and the second account is an Imap, third
account is an aol account and fourth account is a webmail.
I think you can have just two accounts and still see this problem.
-open mail from the tasks menu item
You will see that with today's bug reported bug 70924 that inbox does not get
selected.
-click on the inbox for the first account.
-Do not click on the inbox for the second account
-compose a new message and send it to 2 accounts
-click on Get All New Messages from tool bar drop down or the menu item

Actual Results:  You will see that the message is retrieved for the first
account only.  I have biff settings checked for every 1 minute on the second
account still the new message is not retrieved untill you click on the inbox for
the second account.
Expected Results: Since the password is saved in the password manager. The
second account is already authenticated. So Get all new messages when password
saved should retrieve messages for the second account also.

Workaround that I see for this is that before doing Get all new messages make
sure you click on both the inboxes for both the accounts.  Then compose and send
a mail and do Get all new messages will retrieve messages for both the accounts.
 Also I see that this cannot be reproduced if you start with -mail as scott
mentioned in bug 70924

So looks like inspite of biff and saving password for the accounts in the
password manager the accounts are not really activated or connection to server
is not being made unless there is some kind of action on inbox folder?

confirming this bug. I have not checked this on other two platforms yet.  Could
this be happening due to bug 70924?

 

Comment 6

[racham]

Sheela,

Thanks for your report. It's very detailed and will be useful in tracing the
cause for the behavior reported. I will try reproducing this following steps you
provided.

I think all these regressions are very much linked (particularly when console
option is working). I will update more as I find things.

Comment 7

[racham]

OK...finally the problem has been identified. As mentioned earlier this is 
commercial only. So, I will be opening a new bug in bugscape.

Regressed by Syd's checkins to AIM. Unfortunately, method toOpenWindowByType() 
routine is described in tasksOverlay.js and aimHelpers.js. Later overwrote the 
former. Implementation of the function in the later was slightly diffrent from 
the former and hence causing these regressions (70841, 70924). Anyway, more in 
bugscape.

thanks everyone for the all info provided. Resolving this as invalid.

Comment 8

[racham]

Adding Syd for some background.

Comment 9

[racham]

Follow bugscape bug 4158 for further action.

Comment 10

[Sheela Ravindran]

verifying this as invalid based on bhuvan comments

Comment 11

[Tim Taylor]

I can reproduce this bug exactly as Sheela described with a non-commercial
build, a nightly a grabbed about 2 hours ago:

Mozilla/5.0 (X11; U; Linux 2.4.1 i686; en-US; rv:0.9+) Gecko/20010503

Used /pub/mozilla/nightly/latest/mozilla-i686-pc-linux-gnu-installer.tar.gz to
install.

Tested with a fresh profile by following these steps:

1. remove .mozilla directory
2. create new profile
3. setup two POP3 accounts
4. check mail for both accounts, entering password and storing in Password Manager
5. restart mozilla
6. reproduce with steps posted by Sheela

It appears the relevant discussion took place in bugscape.  Since this is now
happening with non-commercial builds could someone reopen this bug or provide a
more informative explanation than "verifying this as invalid based on bhuvan
comments"?