User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 I have a filter set up which simply moves any msg marked as "Junk" to my "Trash" While going through newsgroups, i noticed that sorting by date wasn't accurate, because a decent minority of the posts had only a time -- no m/d/y date info. I selected all of these messages (perhaps 50) and clicked "Tools > Run Filters on Selected Folders" My machine paused a bit, then spat out an error message: A News (NNTP) error occurred: yellow.readfreenews.net: Your host connection limit reached - email@example.com OK, fine, I'm using a free public news server, I reached some kind of time-based download limit. Then another popped up, and another and another... I first clicked "Enter" for each "OK", but that got tiresome after 10 or 12, so then I held the Enter key down. The windows popped up and dissapeared rapid-fire. I then let go the Enter key and then my KDE window list started filling up with many many seperate error windows, so quickly that I couldn't close them. I switched to an Alt-F2 and kill -9ed the lowest mozilla pid, killing everything. Reproducible: Always Steps to Reproduce: 1. Open a news account to news.readfreenews.net 2. Subscribe to "alt.os.linux.redhat" 3. Download the first 500 posts 4. Create a filter whose Junk Status == Junk to local "Trash" folder 5. Select all articles in newsgroup 6. Mark all as "junk" Keep articles highlighted 7. Tools > Run Filters on Selected Folder Actual Results: bombarded with "A News (NNTP) error occurred: yellow.readfreenews.net: Your host connection limit reached - firstname.lastname@example.org" error windows ad infinitum, or at least one per post (i assume) Expected Results: The problem here is that it appears that whatever path was running tried to keep going after that error message, instead of simply quitting. Either that, or the code dispensing error messages should be "smart", i.e. it should know whether or not i've already gotten that error in regards to the current action.
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.