Closed Bug 65591 Opened 24 years ago Closed 23 years ago

Compuserve imap.cs.com: Mail marked as deleted shouldn't be rebolded when rechecking for new mail

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: Peter, Assigned: mscott)

Details

(Keywords: imap-interop)

Mail marked as deleted shouldn't be rebolded when rechecking for new mail. 1. edit mail/news account settings - server - when delete: MARK AS DELETED 2. get new mail and read it (now it's unbolded) 3. delete mail (x appears next to envelope on left) 4. click: Get New Messages 5. deleted message is rebolded (but shouldn't) This is particularly annoying singe the INBOX unread message count is updated too, making one think one has more unread messages than one really has. Also a visual scan of ones messages makes it appear that there are a lot more unread messages (bold) than there really are.
Keywords: mozilla0.9
QA Contact: esther → sheelar
I was not able to reproduce using build 2001-01-17-08 . Reporter, Are you still seeing this problem? Can you also tell us which build you were using?
Yes, i am definetely still getting this bug. I use: build 20010118, imap server, just copy new nightly over old (no delete), no new prefs.js, winNT4sp6 Also, if i press delete on an already deleted file, it doesn't undelete (unmark as deleted) that message. But that is probably another bug.
Marking NEW as per comments.
Status: UNCONFIRMED → NEW
Ever confirmed: true
change qa contact to karen- this is a imap functionality
QA Contact: sheelar → huang
I cannot reproduce this problem by using 02-26-09-Mtrunk build. Can you tell me what kind of the IMAP server are you using?
I'm still getting this on 2001-02-22 My IMAP server is Compuserve: imap.cs.com I have "check for messages every *10* minutes" activated.
I still cannot reproduce this problem with the same setting as you. I only see bug 69151 for NMS 4.15p4 Server & bug 59694 problems. Adding Compuserve IMAP on the summary and interop for the keywords. This might be depend on different IMAP server implementation (there was bug 69757 report the other IMAP server mark as deleted problem....)
Keywords: interop
Summary: Mail marked as deleted shouldn't be rebolded when rechecking for new mail → Compuserve IMAP: Mail marked as deleted shouldn't be rebolded when rechecking for new mail
karen: are you still not getting this? I definetely am (2001-07-05) Do you have messages that you have *MARKED* as deleted (they should have a little red "x" in the icon). Then select "Get Message" and watch the read, marked messages get RE-bolded. Please describe exactly what you are doing and seeing/not seeing.
OS: Windows NT → All
Summary: Compuserve IMAP: Mail marked as deleted shouldn't be rebolded when rechecking for new mail → IMAP: Mail marked as deleted shouldn't be rebolded when rechecking for new mail
I have a similar problem. It occurs after the route to the IMAP host was broken and established again (Dial-up or modify routing tables manually). 1. receive IMAP email 2. delete some messages 3. break route to host (modify routing table / unplug network cable / hang up dial-up network) 4. reconnect (modify routing table / replug network cable / reconnect dial-up network) 5. check for mail -> previously deleted messages are displayed as new in Inbox
.
Assignee: sspitzer → mscott
Component: Mail Window Front End → Networking: IMAP
QA Contact: huang → meehansqa
Summary: IMAP: Mail marked as deleted shouldn't be rebolded when rechecking for new mail → Compuserve imap.cs.com: Mail marked as deleted shouldn't be rebolded when rechecking for new mail
Peter, could you attach a protocol log? http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap odi, your problem is simply that the server is losing state because you disconnected the client before it had a chance to tell the server to save state, and the server dropped all the state changes on the next connection.
This must have gotten fixed somehow - WFM (build 1.0.0+, 2002-05-11, win98) Hey, just wait long enough, and bug magically fix themselves. ;)
great - it's possible it was fixed by a new server release.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.