If I define a processing rule which should mark a thread as watched, only the mail which matches the processing condition is marked as watched but not the whole thread. Steps to reproduce: - Have a mail thread with multiple mails - Define a processing rule which matches one of the mails with the action "watch thread", e.g : "enabled rulename "" body_part matchcase "test" watch" - run processing rule Result: Only the mail which matches the condition is marked as "watched". Expected: The whole thread is marked as watched.
That's expected, that's how it works. When you apply 'watch thread' to a message in a thread that applies from that message onwards, and not to the older messages.
It also don't apply from the message onward but only for the single message which matches the rule. While if I perform the "watch thread" action manually with the right-click menu the message itself and all messages below are marked as watched. So it seems like there is at least some inconsistency.
works for me.
anything I can do? Are there any logfiles I could provide any other way to debug the processing rules?
the 'watch thread' icon is shown in the S (status) column, a message may have more than one status, e.g. replied, forwarded, unread, replied+forwarded, watched thread, etc, but the status column shows only one icon. Is your problem that you are expecting to see the 'watch thread' icon but another, such as 'replied' is there instead?
No, there is no the "watched" indicator isn't hidden by another status. I created a screenshot to illustrate the problem: https://wolke.schiessle.org/s/uGLggaIsRWYxTsH As you can see two mails where caught by my processing rule, the first one and the third one and exactly this two are marked as watched. I would expect that from the first one down all mails in the thread are marked as watched.
Originally I'd mistakenly used filtering rather than processing, so re-opening this as I have now managed to reproduce what you describe, and I can now see that manually marking 'watch thread' applies to all msgs in that thread below, but it is not the case when using processing to 'watch thread'.