Closed Bug 248733 Opened 20 years ago Closed 19 years ago

you have to click "get messages" twice to get messages

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.7 Branch
x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: kaufmannjd, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040113

I installed the new release 1.7 of Mozilla. To get new messages (mail) I clicked
on the button and I had to enter the password. Then nothing happened though
there were new messages on the server. Clicking the button once more, the
messages are downloaded. This problem doesn't exist in version 1.6

Reproducible: Always
Steps to Reproduce:
Follow my description I made above (details).
Actual Results:  
Follow my description I made above (details).

Expected Results:  
Follow my description I made above (details).
Blocks: 165832
Is this each time you get mails, each time you get mails in a session, or was it
just once after switching to 1.7?
(In reply to comment #1)
> Is this each time you get mails, each time you get mails in a session, or was it
> just once after switching to 1.7?

Indeed it happened each time I tried to get new messages without having entered
the password. After entering the password it worked normally. Because of this
bug I switched back to version 1.6
If an password is entered/in the manager and detected as false, you'll get
prompted for a new one. After entering this one, you've to issue a new get.

But if none is present in the manager or cache when pressing get msgs, it
shouldn't be necessary twice. To this I wasn't able to reproduce the behaviour
you described with 1.7 here.
Sorry, I can't help.
Product: Browser → Seamonkey
Component: MailNews: Notification → MailNews: Main Mail Window
Version: Trunk → 1.7 Branch
Assignee: sspitzer → mail
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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.