filter rules can not be saved
Categories
(Thunderbird :: Filters, defect)
Tracking
(Not tracked)
People
(Reporter: uweklatt, Unassigned)
Details
Attachments
(2 files)
Using Thunderbird 60.7 32 Bit
I am not able to change filter rules.
After closing and reopen Thunderbird all changes are gone.
I tried to delete "msgFilterRules.dat" in the mailfolders.
They are newly created but I can't add or change filter rules.
File content of msgFilterRules.dat remains:
version="9"
logging="no"
Uwe
Addon:
I found that this problem needs
- enabled Junk-filter for mail account
- enabled "trust external SPAM filter" (SpamAssassin) which creates an extra filter rule
Perhaps this filter rule makes trouble!
Uwe
Updated•6 years ago
|
I can't reproduce losing filters even with those options. Is there anything more to this? Can you restart TB with addons disabled (in Help menu) to see if it help?
Also, open the Error console (in Tools) and watch if there are any errors after creating a filter in the Filter editor and closing the Filter list window.
Hello,
I disabled addons and reenable the two settings.
The activated options are creating a non working filter:
- NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgSearchValidityManager.getAttributeProperty] mailWidgets.xml:1606
- Filter not saved because standard search term '47' in rule 2 (Ursprung der Junk-Bewertung, ist nicht) not available in this context
Uwe
Thanks, that looks useful. Can you attach a screenshot of a filter edit that fails like this? Are you creating filter rules using based on Junk score or origin (as the error message says)? Or it is the internal hidden Spamassasin filter that is failing to be created.
This seems to be caused by the internal Spamassasin filter. (This filter entry is not hidden!)
Uwe
What happens to Bugs like this?
Nobody seems to take care of it since 4 month...
In my opinion I have delivered enough informations to drill down and fix the problem!
Uwe
Comment 8•5 years ago
|
||
(In reply to uk from comment #6)
This seems to be caused by the internal Spamassasin filter. (This filter entry is not hidden!)
Why do you say this is causing it? Does unchecking the "trust" checkbox allow filters to be saved?
Comment 9•4 years ago
|
||
perhaps fixed by bug 1607613
Description
•