Message Filter Log Stays Empty
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: t20, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:97.0) Gecko/20100101 Firefox/97.0
Steps to reproduce:
When I clicked Menu > Tools > Message Filters > Filter Log in TB recently, I saw the log of handled messages, and it looked correct. I then clicked the Clear Log button, leaving the Enable the Filter Log checkbox checked. Since I did this, no new handled incoming messages have been reported in the Filter Log. Instead, the Filter Log remains empty. === I looked for a file in the TB profile that might be related to this problem, such as "msgFilterRules.dat", but could not find such a file. === Version 91.6.1 32 bit. ==== Don't know my agent string.
Actual results:
See above.
Expected results:
See above.
|
Reporter | |
Comment 1•3 years ago
|
||
I am actually getting some filtering logged and some not logged. Will investigate further.
|
|
Reporter | |
Comment 2•3 years ago
|
||
I narrowed down the problem. I have a rule: when To is example.com move message to Spam folder. The rule is working (the message is moved), but the rule is not logged in the Filter Log. Is this happening because the folder is named "Spam"? Will investigate further.
|
|
Reporter | |
Comment 3•3 years ago
|
||
I've done a number of experiments locally using various kinds of rules, and they all work but are not logged. And some incoming messages are not logged either, but a few are logged. So it appears to be a random problem. I can't narrow it any further.
|
||
Comment 4•3 years ago
|
||
What happens if you try version 102.2.0, which becomes available next week ?
|
|
Reporter | |
Comment 5•3 years ago
|
||
I have no idea, if it is not available now.
Also, I am recovering from an emergency hospital visit, so not sure I can do much testing for awhile.
|
|
||
Comment 6•3 years ago
|
||
Thanks for the feedback. Hope for your speedy recovery.
This tends to be an issue with file permissions. You might also check the error console for related information.
If you eventually see this problem on version 102, please reopen the bug report.
Description
•