User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; .NET CLR 1.0.3705) Build Identifier: version 0.9 (20041103) 1) First of all, there's no way to run filters automatically as soon as mail arrives, or I haven't found those. Pressing Run FIlter on folder to toss all the subscription and mailing lists into their folders, etc stuff is a pita #1. 2) From that, comes another pita. I am subscribed to ad-sponsored lists, and they end up in Junk - I have to dig them out each and every time. 3) Finally, (and thisl ooks like a real bug at last), after the first time I get mail, auto move Junk mail to Junk folder feature stops working. Mail marked as junk is moved to Junk when I collect mail on the program launch, on all the subsequent queries to server, mail is marked as Junk, but it stays in the inbox. If oyu press run junk control on the folder, it is removed. 4) And one more feature that's lacking - there's empty thrash, but there's no empty junk, so if i want to, I have to go there, select all the messages and delete them manually. Reproducible: Always Steps to Reproduce: That's for 3 cause 1-2-4 are features that are lacking. 1. Launch TB, configured to move junk mail to junk folder automatically. 2. Get mail with junk and watch it land in the junk folder. 3. Get more mail with junk. Actual Results: The mail got in step 3 is marked as junk and stays in the inbox. Expected Results: It should've been moved to Junk
Summary: Juk Control and Filters have poor usability → Junk Control and Filters have poor usability
oh, and by feature suggestion #2 I mean running filters before Junk control and ability to mark messages as trusted on that stage, e.g. no-junk messages.
(In reply to comment #0) > 1) First of all, there's no way to run filters automatically as soon as mail > arrives Simply defining a filter (and being sure it's been enabled) is sufficient to run filters automatically. Is this still a problem for you? Note that if you're using the Global Inbox, filters have to be defined for each individual account to be automatically run; defining filters for Local Folders does, currently, require running filters after-the-fact. See bug 257979. > 2) From that, comes another pita. I am subscribed to ad-sponsored lists, and > they end up in Junk - I have to dig them out each and every time. > I mean running filters before Junk control and ability > to mark messages as trusted on that stage, e.g. no-junk messages. When filters run automatically, they *do* run before the junk filter; and filters *do* have the capability to Mark As Not Junk. What will surprise and probably annoy you is that, when you switch to the folder containing the filtered messages, the junk filtering will be run on those messages *then*; see bug 198961 (and the bugs it references). > 3) after the first time I get mail, auto move Junk mail to Junk folder > feature stops working. Mail marked as junk is moved to Junk when I collect > mail on the program launch, on all the subsequent queries to server, mail is > marked as Junk, but it stays in the inbox. [Run Junk Controls On Folder works > to remove them.] Yes, that would be a bug. Are you still experiencing this problem? See bug 196732 comment 59 (many commenters describing many symptoms), bug 272414 (possible interference by AVG), bug 231845 (IMAP). > 4) And one more feature that's lacking - there's empty thrash, but there's no > empty junk, so if i want to, I have to go there, select all the messages and > delete them manually. Bug 261875. So we have a problem here: your bug is duplicating perhaps four different bugs; this is why the Bug Reporting Guidelines request that you search for bugs *before* you file, and when you file, specify *one issue per bug*. Further, item 3, which seems to bother you the most, doesn't have a clear earlier bug report. I have never experienced your items 1 or 3; junk controls work very well for me, notwithstanding the few missing features.
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.