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 As soon as I open the e-mail client and click on the get msgs button, the Alert Message pops up that reads, "One of your filters uses a custom header that contains an invalid character, such as ".", a non-printable character, a non-ascii character, or an eight-bit ascii character. Please edit the msgFilterRules.dat file, which contains your filters, to remove invalid characters from your custom headers." As soon as I click the "OK" button, the mail, all of it unfiltered, loads up my inbox. The previous version that I have, Mozilla 1.1b has no problem in handling the filters as they were added for the purpose of trashing spam as it was downloaded from the server. It still works fine in the older version, but only in this newer version is there any problem. I have a couple of other servers that I get mail from, other than my ISP, and the filters work fine for those. My ISP is http://www.cpinternet.com I only got this new version as when I opened the Mozilla browser, it took me to a page on your site that informed me that I was using an older version and should download the new version. So I did. I am still in the learning curve for using Linux, and haven't a clue where the file msgFilterRules.dat would reside on my machine. I am using Mandrake 8.2 on the KDE desktop. Besides, I figure that if the filters work fine in the older version, Mozilla 1.1b, then in is something that needs to be fixed in the newer version, Mozilla 1.3a. Maybe someone had a mis-stroke while coding for filters. I have just too many filters to go through if you have reconfigured everything. If that is the case, is there a way for me to apply the older version configuration to the new version? That would be a whole lot easier for me. Thank you. Reproducible: Always Steps to Reproduce: 1. Just start up the email client and click on get msgs 2. or right click on sender and choose create filter from message 3. Actual Results: I get the afore mentioned error alert message Expected Results: Should have accepted the filters from the previous build and continue to work with them as in the older build. It first did it in the default theme, and in grey modern. Not all previous installed themes even work with 1.3a. Some themes when applied, do not take when restarting client, but stay in default theme mode. I have not yet downloaded this version to the Windows platform yet, to see if it happens in there as well. I have a Pentium IV 1.7GHz, 512MB SDRAM. Dual platform system, 2 40GB HDs, one is Windows 98SE, and the other Mandrake 8.2, with Mandrake boot via floppy. The two O/Ss do not see each other and are completely seperate. There is no cross traffic to interfere with either system. Connected to the web, via an external U.S. Robotics 56kb dial-up modem. ATI RADEON 7000/VE Video card, and Creative Labs SB Live 5.1 sound card. 17" CTX video moniter, headset and boom mic and webcam for video conferencing. CDRW 36x12x48 and a Diamond Multimedia LAN card for local LAN. I built this box around the end of July 2002, and was surprised that it worked right off with no problems. My first build. Oh yeah, motherboard is a NB72-SC/SR socket 478 for the Intel 845 chipset with 400MHzsystem data bus, and a Panasonic DVD drive. Only have one DVD so I kind of forget the drive sometimes. And finally a Lexmark Z11 printer. Software besides the standard added software that comes bundled with Mandrake 8.2, Java SDK, and a whole slew of 3D graphics applications, and VRML for game development.
*** Bug 174933 has been marked as a duplicate of this bug. ***
OS -> All based on dupe. Reporter: msgFilterRules.dat should be found in ~/.mozilla/Mail/[servername]/ If you can spot an obvious error in that file, or could attach it to this bug, that might be helpful.
OS: Linux → All
*** Bug 185372 has been marked as a duplicate of this bug. ***
I get the same response for the same actions. I switched directly from Netscape 7.02 to Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 I have no filters for this email address in either Netscape or Mozilla yet I get this message. My other email addresses using the same pop server with extensive filtering have no problems.
Richard Quick, what is your status with this bug? You never responded to comment 2. If you no longer encounter this symptom, please mark this bug Resolved | WorksForMe
I only get this message when I go to Tools - Message Filters... My filters are working but when I go to add a new filter I get the message and if I ok it a empty filter list. As I have a couple hundered filters set up I'm having problems spotting the bad filter. I didn't have the problem until I shut down Thunderbird and started it again. I'm using the Sun Solaris version 0.9 version downloaded from the web site. Also had the same problem with version 0.7.1. It would be useful if the error was caught when the filter is entered, or if not there at least print the name of the problem filter to make it easier to find.
(In reply to comment #6) > if I ok it a empty filter list. Will this occur even when new profile & new account & new message filter? What did happen? When you clicked "OK" of error message dialog, no filter was displayed on message filter list panel(same display as when no filter is defined)? When you clicked "OK" of error message dialog, blank panel was displayed? If latter, what will happen when resize the blank panel? > I only get this message when I go to Tools - Message Filters... Will this occur even when new profile & new account & new message filter? Can you attach your megFilterRules.dat file? If it is difficult for security/privacy, check your msgFilterRules.dat contents. - Are there long filter rule lines? (more than 1024 bytes line, etc.) - Is there "(double quote) in a quoted rule(quoted by 2 "s)? - Are there any spcecial characters such as non-ascii in rules?
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.