Closed Bug 227308 Opened 21 years ago Closed 10 years ago

RFE: Junk filter doesn't expunge messages from IMAP Inbox

Categories

(MailNews Core :: Filters, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: hacksoncode, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031002 Firebird/0.7+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031002 Firebird/0.7+ There are other bugs that talk about problems with filters moving messages leaving deleted messages behind, but I'm not really seeing that (and even if I were, it's especially egregious WRT spam). I'm seeing the messages being left on the IMAP server intact, and just removed from the local Inbox index (it seems). I read my work mail from home using a webmail interface. I would have thought that Mozilla/Thunderbird (which I leave running on my machine at work) would have moved the messages out of my Inbox, leaving it uncluttered. But it doesn't seem to work that way. That makes it almost impossible to use my webmail interface because of the giant piles of spam in my Inbox. The messages don't go away until I empty my trash. Reproducible: Always Steps to Reproduce: 1. Bring up both Outlook and Thunderbird/Mozilla. 2. Allow spam to arrive and be moved to the junk folder by Mozilla. Actual Results: Messages still appear in Outlook, or in a webmail interface (even after refreshing). They don't look marked deleted in Outlook/webmail... they just look normal. Expected Results: Messages should have been moved immediately from the server. I'm using "move to trash" as my delete method (as opposed to "mark as deleted"). Also, it doesn't seem to matter whether the destination spam folder is local or on the IMAP server.
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/
Well, I'm changing this from a bug report to an RFE. I still think it's a very important feature to have for people that read mail primarily using Thunderbird but secondarily other interfaces such as web-based mail, because it severely limits the usefulness of Thunderbird's filtering system. Without this, I'm seriously considering turning off my Thunderbird filtering and switching over to having Outlook do my filtering, because it will properly expunge my inbox. That would be sad.
Severity: normal → enhancement
Summary: Junk filter doesn't expunge messages from IMAP Inbox → RFE: Junk filter doesn't expunge messages from IMAP Inbox
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Status: UNCONFIRMED → NEW
Ever confirmed: true
Filter on "Nobody_NScomTLD_20080620"
QA Contact: laurel → filters
Product: Core → MailNews Core
Haven't seen this on recent builds.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.