[Users] Strange filter problem

[mlist]

On Wed, 4 Sep 2019 08:48:55 -0000 Paul wrote:

> Do you want to share a filtering log?

OK. My current rules are:

enabled rulename "*** LIST - WATCH MINE" found_in_addressbook "From" in "addrbook-000004.xml" & found_in_addressbook "To" in "addrbook-000009.xml" watch
enabled rulename "*** LIST - WATCH MINE" found_in_addressbook "From" in "addrbook-000004.xml" & found_in_addressbook "Cc" in "addrbook-000009.xml" watch
enabled rulename "*** LIST - ignore NOT WATCHED" header "List-Id" regexpcase ".+" & ~watch_thread ignore
enabled rulename "STOP" all stop

addrbook-000009.xml contains the email addresses of the mailing lists I use.
addrbook-000004.xml contains my email addresses.

To simulate receiving new mail from a list:

I selected your last reply, marked it as unread (also made sure it is not
watched and not ignored). The whole thread in which it resides is watched. So
I ran 'Filter selected messages' (regardless of account). The result is:

----------------------------------------
[2019-09-04 19:15:10] filtering message (manually)
                       message file: /home/username/mail/lists/Claws Mail/1265
                       Date: Wed, 4 Sep 2019 08:48:55 -0000
                       From: Paul <claws at thewildbeast.co.uk>
                       To: users at lists.claws-mail.org
                       Subject: Re: [Users] Strange filter problem
[2019-09-04 19:15:10] processing rule '*** LIST - WATCH MINE' [ found_in_addressbook "From" in "addrbook-000004.xml" & found_in_addressbook "To" in "addrbook-000009.xml" watch ]
> rule is not account-based, all rules are applied on user request anyway
[2019-09-04 19:15:10] checking if message matches [ found_in_addressbook "From" in "addrbook-000004.xml" ]
[2019-09-04 19:15:10] checking if message matches [ found_in_addressbook "To" in "addrbook-000009.xml" ]
[2019-09-04 19:15:10] address [ claws at thewildbeast.co.uk ] does NOT match
[2019-09-04 19:15:10] address [ users at lists.claws-mail.org ] matches
> message does not match
[2019-09-04 19:15:10] processing rule '*** LIST - WATCH MINE' [ found_in_addressbook "From" in "addrbook-000004.xml" & found_in_addressbook "Cc" in "addrbook-000009.xml" watch ]
> rule is not account-based, all rules are applied on user request anyway
[2019-09-04 19:15:10] checking if message matches [ found_in_addressbook "From" in "addrbook-000004.xml" ]
[2019-09-04 19:15:10] checking if message matches [ found_in_addressbook "Cc" in "addrbook-000009.xml" ]
[2019-09-04 19:15:10] address [ claws at thewildbeast.co.uk ] does NOT match
> message does not match
[2019-09-04 19:15:10] processing rule '*** LIST - ignore NOT WATCHED' [ header "List-Id" regexpcase ".+" & ~watch_thread ignore ]
> rule is not account-based, all rules are applied on user request anyway
[2019-09-04 19:15:10] checking if message matches [ header "List-Id" regexpcase ".+" ]
[2019-09-04 19:15:10] checking if message matches [ ~watch_thread ]
[2019-09-04 19:15:10] header value [ <users.lists.claws-mail.org> ] matches regular expression [ .+ ] (Case insensitive)
> message matches
[2019-09-04 19:15:10] applying action [ ignore ]
[2019-09-04 19:15:10] processing rule 'STOP' [ all stop ]
> rule is not account-based, all rules are applied on user request anyway
[2019-09-04 19:15:10] checking if message matches [ all ]
> message matches
[2019-09-04 19:15:10] applying action [ stop ]
[2019-09-04 19:15:10] no further processing after action [ stop ]
----------------------------------------

Final result: the message is marked as read and ignored. Normally (when
receiving new mail) I have seen it simply being marked as read.

Another weird thing I noticed during this test:

All the threads in this folder are collapsed and I expanded this one
explicitly. Right after running the filter command its first 2 sub-threads
collapsed themselves without any additional action on my side.