Closed Bug 147307 Opened 23 years ago Closed 16 years ago

Message status "New" cleared on POP3 download

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ecarlson, Unassigned)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523 BuildID: 2002052306 When downloading new mail via POP3, mail status column "New" flags are cleared on previously downloaded "New" messages. Reproducible: Always Steps to Reproduce: 1. Download mail via POP3, but don't read it: New mail gets "New" status 2. Download mail via POP3 again: The mail that was marked "New" in step 1 is no longer marked "New" Actual Results: "New" flags were cleared Expected Results: "New" flags to remain until the messages are actually read, or until Mozilla is restarted. Netscape 4.79, and earlier didn't have this problem. Mail would stay "New" until you either read it, or you exited and restarted Netscape. This is not good, because I often receive more messages before I have finished reading all the "New" messages, and I often have old messages that remain unread, and I can't tell the new mail from the old, unread mail after the "New" status is cleared. Also, I often have new messages in subfolders that I haven't even gotten to yet, but the "New" flags for that subfolder, and for the messages in it are cleared when I download more mail, so I can no longer tell which subfolders still have new unread mail.
It now seems that the NEW flags are only cleared in the current e-mail folder when I download more mail. Originally it seemed to clear the NEW flag in all mail folders. I am now running 1.0 final release, and was using RC3 earlier. Also, my e-mail folders, including about 50,000 message from the past 5 years, were imported into Mozilla 1.0/RC3 from my Netscape 4.79 profile. I don't know if that has any relevance.
Does this still happen on a recent nightly build? -M (Added 4xp)
Keywords: 4xp
It still happens in 1.2 final. I'll install 1.3 final as soon as it is released.
So you're saying that downloading new mail marks your unread mail as read? -M
Yes, performing a "Get New Messages" (POP3) marks my unread messages as read, in the current mail folder (whichever folder I happen to be in at the time I click "Get New Messages"). It doesen't even matter if there is new mail to be downloaded or not, just invoking "Get New Messages" clears the NEW flags in the current folder. It only appears to effect the folder I am in at the time.
Correction for comment #3. It should read: "It still happens in 1.1 final. I'll install 1.2 final as soon as it is released."
QA Contact: olgam → esther
FYI: Problem still exists in Mozilla 1.2.1
Reporter: Can you reproduce this bug with a recent build of Mozilla (for example, 1.4 RC1)? If so, then please comment again with details. If not, then please resolve this bug as WORKSFORME. Thanks.
Problem still exists in 1.4-RC1 It's very simple to reproduce, so go ahead and try it. Download some new mail via POP3, and notice the "New" flags on the new messages (most likely in the Inbox folder), then, while still in the same folder, but without reading any of the messages, do another POP3 download, and you'll notice that all the "New" flags are cleared in the current folder.
Correction to #4 and #5 - No, downloading new mail doesn't mark unread mail as read, it clears the NEW flag on NEW unread mail from the previous download in the current folder.
Additionally, changing to another folder, then returning to the download folder (most likely Inbox) will clear the NEW flags on new messages, unlike Netscape 4.xx. Only opening a message or exiting and restarting Mozilla should clear a NEW flag on a message as per Netscape 4.xx.
I have reproduced the following: An explicit Get New Messages by the user will clear the New flags on the account. An explicit Get All New Messages by the user will clear the New flags on the account, the Inbox, and the messages in the Inbox, for all accounts. (However, if the Get New messages is performed by biff, the New flags are not marked.) Viewing a folder with new messages, then switching to another folder, will clear the New flags on the folder and the contained messages. Tested with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030527 There are quite a number of bugs surrounding notification flags; see in particular bug 46133, bug 107206, bug 189878, bug 192039, bug 116181, bug 202783. I just noticed this one because its recent changes.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Problem still exists in 1.4-final.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: esther → message-display
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This is probably still an issue, but I do 99.9% of my personal e-mailing in Google Apps now, so I don't care at the moment. I only use Seamonkey to occasionally download my e-mail from Google Apps as a local backup, and I browse with Firefox, so I hardly ever touch any version of Mozilla Mail at this time (that could change in the future).
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Fixed is not the right resolution if nothing has been checked in.
Resolution: FIXED → WORKSFORME
Thanks. I didn't even want to mark it as resolved, since it isn't, but it forced me to. It wouldn't let me save my comment until I changed it to resolved. It kept saying I wasn't allowed to set something to something (don't remember the exact error).
You need to log in before you can comment on or make changes to this bug.