Closed Bug 242136 Opened 21 years ago Closed 19 years ago

filtered IMAP mail always gets marked as read, new for 1.7b

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mitchs.bugzilla, Assigned: Bienvenu)

References

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040421 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040421 I'm sorry I don't have details about my IMAP server, but since I've installed Mozilla 1.7, all of my filtered mail gets marked as read. I'm the type of person that likes to Expunge deleted/filtered mail at the end of the work day. This means leaving my filtered mail all in my inbox, but not marked as deleted in Local Folders. I only read stuff that's bold, ignoring the 'mark as read and delete' stuff that I filter, unless the subject looks REALLY interesting. In Mozilla 1.6, only my filtered-for-deletion mail got "marked as read" but everything else remained 'bold'. Now, in Mozilla 1.7 Alpha and up (beta, and RC 1) every FILTERED mail gets marked as read, but filtered properly. Is this a new feature that I'm missing, or is this unexpected? I've been able to reproduce it only with my own settings, so I'm hoping someone else can reproduce it. Reproducible: Always Steps to Reproduce: 1. Set up IMAP Server Settings with: [x] Check for new messages at startup [x] Check for new messages every [10] minutes When I delete a message [Mark it as deleted] [x] Clean up ("Expunge") Inbox on Exit [x] Empty Trash on Exit 2. Filter some messages to Local Folders, filter some messages for deletion. Actual Results: Everything gets marked as read, except non-filtered mail. Expected Results: Filtered messages should remain marked as Unread, but deleted messages should be marked as read
can I get an imap protocol log? I don't think this is a general problem - I wonder if something is going wrong with the PEEK command we use to look at filtered mail. It might also be interesting to look at your filters file... http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
You can see it reading my INBOX, up to 1064, (but edited for size) and then 1065 comes in. It gets marked as read automatically, and then I think I proceeded to read it. I have two filters that should ave run on it-- one to change the label (color) and then one to move it to a folder in Local Folders. Basically, everything that came in with the subject containing "[AB Req]" was to me labeled a certain color and sent to a Local Folder, but supposed to leave it Marked As Deleted but not Marked As Read in my inbox until I quit mozilla.
oh, you're marking the message as deleted? There was a change to make sure that we mark deleted messages as read because it plays much more nicely with move filters, especially. Ack, it sounds like you are a person who liked the old behaviour :-(
No, that's not what I've been saying. Deleted mail should be marked as read and marked as deleted. Filtered mail should not be marked as read, but marked as deleted, just as is the behavior of Mozilla 1.6. Perhaps when I said, "It gets marked as read automatically," I should have said "Mozilla marks it as read automatically" to be clear on what my filter does ("I") and what Mozilla is doing ("it") That IMAP log is so hard to decipher-- is it unclear what's happening? Can you suggest a series of actions you'd like to see, so that you can read the log of these actions? Or do you think the IMAP log is the wrong path to go down?
>Filtered mail should not be marked as read, but marked as deleted, just as is >the behavior of Mozilla 1.6. If by filtered, you mean moved to another folder, then I should say that a move is a copy followed by a delete, and that's the context that I meant "deleted messages are marked as read". And that's the behaviour that a lot of people wanted - they didn't like messages getting left in their inbox, deleted, but still unread...
I think I follow. So you're saying that this IS a new feature in 1.7? either one of these two things changed: 1) The Mozilla 1.6 was explicitly marking moved-by-a-filter'ed mail as UNread or maybe explicity marked ONLY deleted mail as read, as long as there were no other actions taken on said deleted mail. 2) The Mozilla 1.7 is doing a copy-and-delete on moved-by-a-filter'ed mail, whereas before it was doing something else, perhaps a copy-and-delete-and-mark-as-unread-again? (do I overuse hyphens or what?) I also want my deleted mail is marked as read automatically. I agree with that. I liked the feature in which my filtered mail would remain unread in my Inbox, as well as in my local folders, just marked as deleted so I don't have to go to those local folders to read my mails so as to keep track of what I've read and what I haven't. If this arguments has been gone around and around again, you could point me to the bug where it was decided to change this, I'd love to see it, especially because I searched for a very long time to find an already-existing discussion about this (I work with bug trackers too, and I hate dups as much as the next programmer)
I am seeing this same problem: emails from an IMAP server (GroupWise) filtered to move to folders on the same server (but NOT filtered to be marked as read) are marked as read. Until yesterday, when I upgraded from 1.6 to 1.7, I was not having this problem. This bug may be a duplicate of bug 233041. User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 Until I click on a folder to which new emails have been moved (by a filter), the folder name is bold, and shows the correct unread messages count. But after I select the folder, its name is changed from bold to normal, the unread count disappears (becomes zero), and none of the new, unread messages are shown as unread (titles should be bold, but aren't).
see bug 225021 as to why we did this. It also sounds like GroupWise has a bug...
Depends on: 225021
I recompiled Thunderbird 0.8 after backing out the (very small) patch at bug 225021, and voila! My issue disappeared. My guess is that you're right, this is a GroupWise bug (behavior is the same with both GW 6.0 and 6.5 IMAP servers). I'm a newbie to Mozilla, IMAP and mail client development. Can an IMAP client get the IMAP server vendor and version? Does Mozilla mail/T-bird collect this information? If so, is it available via the API? Where do I go to find information like this? My thinking: although this appears to be a GroupWise bug, it also appears to be a long-standing one. A medium-term solution for me and other GroupWise users that wouldn't break the current behavior for other IMAP server users could be to check whether the server vendor is GroupWise, and if so, *not* apply the \SEEN flag to deleted messages.
Product: MailNews → Core
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
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: