Closed Bug 173505 Opened 21 years ago Closed 18 years ago

"Get Msgs" gives no explanation as to why it doesn't work during initial Mozilla mail check, and with slow pop servers the mail check can take some time


(SeaMonkey :: MailNews: Message Display, defect)

Windows 2000
Not set


(Not tracked)



(Reporter: david, Assigned: mscott)



User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

Mozilla mail checks the remote pop server for new mail when it starts, but it
gives no indication that it is busy doing something during this time.
If the pop server is slow [eg it is in another continent], then this mail check
can take some time.

If the user presses "Get Msgs" during this time, it does nothing at all, and it
is not apparent to the user why "Get Msgs" doesn't work.

Reproducible: Always

Steps to Reproduce:
1.Start mozilla configured with a pop server that is very slow.
2.Press "Get Msgs".
Actual Results:  
Mozilla eventually shows the number of messages waiting, but doesn't fetch them.

Expected Results:  
I think that:
1.  It should show some sort of busy indication why it is checking the server.
2.  Perhaps "Get Msgs" should be greyed out during this busy time???????
There are several enhancement requests  for 'progress' dialogs during various
part of the POP/IMAP process (downloading, moving, filtering, ...). But bug
61139 is the closest one to this request.
David, have you tried this recently with a trunk build?  I think we fixed a bug
in this area, but I can't find the number right now.
Hi, have done what you asked, now running the following:

Mozilla 1.2b
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021017

Problem is not fixed.  I managed to click the "Get Msgs" button 15 times while
it was busy polling the mail server for availability of new messages just after
the mail window opened, and still no explanation as to why none of those clicks
do anything at all.
might be fixed with bug 127461
Blocks: 165832
Product: Browser → Seamonkey
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:
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.
Closed: 18 years ago
Resolution: --- → EXPIRED
Component: MailNews: Notification → MailNews: Message Display
QA Contact: stephend → search
You need to log in before you can comment on or make changes to this bug.