Created attachment 1988 [details] Snip of filter rule error I have two IMAP accounts. PAH (id=1) and WT(id=2). Each with separate servers and logins. PAH is the default account. I have several filtering rules for PAH an 1 for WT. When executing a filter on account WT, an error is returned via the log and the rule is ignores. The error is: > skipped: rule is account-based [id=2, name='WT'], not matching current account [id=1, name='PAH'] However, when running the filter manually, I am in the WT INBOX. The current account seems to always pick up the DEFAULT account. This should not be when residing in a different folder tree. The current account should be the account whose tree you are viewing/working in, not the default account.
How do you apply the filtering rules, exactly? Manually?
As the log showed, this was a manual run. Once another spam email arrives I expect to see a similar result, but will report
Since Claws Mail also supports POP accounts, which are not tied to any particular mailbox - for example, several POP accounts can share a single mailbox - then the default account always remains the default account. Likewise, the currently selected account is always indicated by the seletor in the lower right hand corner of the main window.
Created attachment 1990 [details] Filter Setup Menu showing account selection option Thanks, Paul. I respectfully disagree. Maintaining separate mailboxes, e.g. Personal, Work, is a common and necessary practice. And being able to filter on them separately is a necessary function. On reviewing this, it makes more sense to have filters set by account. And claws-mail does this! Why have the option to set an account to which filter(s) apply when they won't work unless all mailboxes are combined??? Do consider this again. Thank you
(In reply to comment #4) > Created attachment 1990 [details] > Filter Setup Menu showing account selection option > > Thanks, Paul. I respectfully disagree. Maintaining separate mailboxes, e.g. > Personal, Work, is a common and necessary practice. And being able to filter > on them separately is a necessary function. On reviewing this, it makes more > sense to have filters set by account. And claws-mail does this! Why have the > option to set an account to which filter(s) apply when they won't work > unless all mailboxes are combined??? Do consider this again. Thank you I have several POP accounts, and each of them has their own inbox, sent, draft and queue folders (sub-folders of the parent folder of each type). So it is not a problem at all to keep different account's mail separate from the others. So maintaining separate mailboxes may be a common practice, but it is not a necessary practice. Claws Mail's auto-account selection is completely sufficient also, for replies, etc. But, on the occasion that it is not, you can set the account in the folder Properties. Some filters apply to all messages, regardless of the account they were received through, so that's why the option is there.
When I create an IMAP account, it creates it's own hierarchy in the main tree, not as a subfolder. Perhaps there's a difference here between POP and IMAP. Anyway, don't want to beat a dead horse. I'll review your comments and maybe they can apply. Maybe not. But I just wanted to report my thoughts. Thanks again.
Created attachment 1991 [details] Snip of filter rule success on secondary IMAP account Paul, an email was retrieved this morning on the Secondary IMAP account and the filter rule for the secondary IMAP account processed properly. Apparently, in this case, when creating a rule after a target email comes in for a secondary IMAP account, the rule fails (as previously demonstrated). However, on subsequent retrieval of a target email, the rule will succeed. So the rule works, but only after the rule was created and a new email arrives. It does not seem to work when rule is created and applied to an existing email in INBOX. But I'm satisfied with this result. Thank you.