1873032 - SpamAssassinYes rule wants to be first after Thunderbird updates

Status: UNCONFIRMED

(Thunderbird :: Filters, defect)

Description

[Valery Ledovskoy]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0

Steps to reproduce:

Note: The problem does not depend on the platform. I have observed this problem on Windows 10, and it manifests itself now after switching to Ubuntu 23.10.

I have been using the SpamAssassin spam filter on the Thunderbird beta for the past few months. The automatic transfer of spam messages to the Spam folder is configured.

At the same time, I use a number of other filters that sort incoming emails into different folders according to various criteria. And I would like to check for spam after performing other filters, i.e. at the end, because SpamAssassin has a lot of false positives for mailing lists and other mass emails (for example, e-checks, emails from Google Alerts, etc.), which I filter by the appropriate folders.

After I started using SpamAsassin, I saw that the SpamAssassinYes rules appeared in the filtering rules (one for each account) and they are located at the beginning of the filter list.

I moved these filtering rules to the end of the list so that the spam check takes place after my other rules are fulfilled.

But since I am on the Thunderbird beta channel, updates happen quite often and after updates, the problem described below occurs. And it has been playing steadily for me for several months now.

Actual results:

After each Thunderbird update, the SpamAssassinYes filtering rule first disappears from the list of message filtering rules. And Thunderbird behaves as if this rule is the first one. That is, anti-spam works first, then the rest of the filtering rules.

After a while (probably after one/more Thunderbird restarts), the SpamAssassinYes rule starts to appear in the list of rules, but at the top of the list. Moreover, it may first appear in the rules for one account, and continue to be absent in others.

Over time, this rule appears for all accounts and I move it to the end of the list and everything starts working the way I want.

Until the next update, when the problem is reproduced again.

Expected results:

In my opinion, after Thunderbird updates, the message filtering rules should remain in place. In particular, the SpamAssassinYes rules should be displayed (and worked out) at the end of the list of filtering rules, as I configure it every time after the next Thunderbird update.

Based on the above, I consider this a bug. And I ask you to fix it.