Closed
Bug 311202
Opened 19 years ago
Closed 16 years ago
Filter Log Showing Incorrect Information
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: worcester12345, Unassigned)
Details
(Whiteboard: closeme 2008-11-20)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051004 Firefox/1.4.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051004 Thunderbird/1.4.1 ID:2005100415 I have maybe a dozen filters set up. They run for the most part (one still doesn't work, but that is not what this bug is about). I received some email messages today, some of which were filtered into the appropriate folders, some which were unfiltered stayed in inbox, some stayed in inbox which should have been filtered (again, that's not THIS bug). I went to look for an email I deleted in the filter log to find the subject title of the message because I wanted to ask the sender a question, and lo and behold, the message did NOT appear in the filter log. In fact, NO messages from today appeared in the filter log. Reproducible: Didn't try Steps to Reproduce: 1. Get some messages, some of which are filtered. 2. Check message log for current activity. 3. Note missing activity. Actual Results: Current activity not logged. Expected Results: Log of current activity. Filters have had problems since maybe .8 or .9 of the software. Go do a bug search on filters and see how many open bugs exist!
Reporter | ||
Updated•19 years ago
|
Flags: blocking-aviary2.0?
Comment 1•19 years ago
|
||
Reporter, can you please attach a copy of your filter log and explain further what is missing from the log?
Reporter | ||
Comment 2•19 years ago
|
||
(In reply to comment #1) > Reporter, can you please attach a copy of your filter log and explain further > what is missing from the log? Sorry, I already cleared the log. For what it is worth, I remember a lot of the dates were "1969" which isn't right.
Comment 3•19 years ago
|
||
Could you attach the filter log once you see the behaviour again?
Summary: filter log not working reliably → Filter Log Showing Incorrect Information
Updated•19 years ago
|
Flags: blocking-firefox2? → blocking-thunderbird2?
Updated•19 years ago
|
Flags: blocking-thunderbird2? → blocking-thunderbird2-
Reporter | ||
Comment 4•19 years ago
|
||
After further review, they still don't work. I have some emails coming in. I have a filter with the words "no new price changes" in the body of the message to catch and put those messages into trash. Instead, the messages stay in the real estate folder with the other messages. I belong to a real estate service which sends email alerts every day, and I only want to keep ones which have actual data. The filter order doesn't matter, it doesn't work no matter the order.
Comment 5•19 years ago
|
||
are these body filters, and do you have message quarantining turned on? If so, that's covered by an other bug.
Reporter | ||
Comment 6•18 years ago
|
||
(In reply to comment #4) > After further review, they still don't work. I have some emails coming in. I > have a filter with the words "no new price changes" in the body of the message > to catch and put those messages into trash. Instead, the messages stay in the > real estate folder with the other messages. I belong to a real estate service > which sends email alerts every day, and I only want to keep ones which have > actual data. The filter order doesn't matter, it doesn't work no matter the > order. > Sonofagun! This filter FINALLY started working after well, since IT NEVER WORKED BEFORE! What changed?
Reporter | ||
Comment 7•18 years ago
|
||
(In reply to comment #5) > are these body filters, and do you have message quarantining turned on? If so, > that's covered by an other bug. > Yes, and yes. What bug? Was that fixed finally?
Comment 8•18 years ago
|
||
you were probably seeing bug 323367
Reporter | ||
Comment 9•18 years ago
|
||
(In reply to comment #8) > you were probably seeing bug 323367 > Actually, I CAN'T see bug 323367. "You are not authorized to access bug #323367."
Comment 10•18 years ago
|
||
sorry, that's bug 324467
Reporter | ||
Comment 11•18 years ago
|
||
(In reply to comment #10) > sorry, that's bug 324467 > That one looks like it was for trunk and 1.8.1 only, not 1.8.0 which is what I think I have. version 2 alpha 1 (20060403)
Reporter | ||
Comment 12•18 years ago
|
||
(In reply to comment #11) > (In reply to comment #10) > > sorry, that's bug 324467 > > > > That one looks like it was for trunk and 1.8.1 only, not 1.8.0 which is what I > think I have. > > version 2 alpha 1 (20060403) > Yes? No?
Updated•17 years ago
|
QA Contact: front-end
Reporter | ||
Comment 13•17 years ago
|
||
Can someone confirm this bug as new?
Comment 14•17 years ago
|
||
(In reply to comment #13) > Can someone confirm this bug as new? Sorry, no - it is not good practice to confirm a bug where, as of your comment 13, the last dated info is 14 months old, regarding a beta. And more info is needed a) are you pop or imap? b) is your information correct in comment 6 that the problem went away, but problem come back? c) do you see the problem in the current version 2.0.0.6 or on trunk? setting reported version to 1.5 (1.4x iirc was beta for 1.5)
Version: unspecified → 1.5
Comment 15•16 years ago
|
||
Worcester12345 do you see this on trunk? irrc a logging bug was fixed in the last several months.
Updated•16 years ago
|
Assignee: mscott → nobody
Comment 17•16 years ago
|
||
RESO INCO due to lack of answer to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Reporter | ||
Comment 18•15 years ago
|
||
Still seeing this bug in Thunderbird 2.0.0.23 where random emails get filtered and not logged for no good reason. After much digging around, I find the email filed away somewhere with no logging, which would at least give a clue as to why it was moved.
Resolution: INCOMPLETE → FIXED
Comment 19•15 years ago
|
||
correcting resolution. please reopen if you see the problem in version 3, which should be available in a few weeks.
Resolution: FIXED → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•