Thunderbird filters and AI sorting can coexist, but first decide which system owns each action. A precise desktop rule may already solve your problem; server-side sorting is useful when you need the result to be visible across connected clients.
Three different mechanisms
| Mechanism | Where it acts | What to confirm |
|---|---|---|
| Thunderbird message filter | In the running desktop client | Execution setting, selected account and target folder |
| Provider or Sieve rule | At the mail server | Provider’s supported conditions and actions |
| AI Email Filter | Application accessing a supported mailbox | Connection, category, processing scope and scheduled runs |
Thunderbird’s Quick Filter Bar limits the displayed list; it does not perform the folder moves of a message filter. Use the native filter guide for creation and troubleshooting rather than replacing a working rule unnecessarily.
Check Local Folders before moving a workflow
The hosted service cannot access messages that exist only in Thunderbird’s Local Folders. A server-side IMAP folder is different: its contents can synchronize to other clients. Check the account and folder location in Thunderbird and verify a test message in webmail before assuming it is available to another application.
Keep a copy of messages before moving an existing local archive. This article does not claim to have migrated a real Thunderbird profile or tested all provider folder mappings.
Assign one owner per action
For a fictional newsletter, choose either a Thunderbird move or a server-side move to the same review folder. Avoid one system moving it out of Inbox and another moving it back. Test with a newsletter and an account alert from the same sender. Exact conditions may suit a native rule; varied message intent may suit a category prompt with explicit exclusions.
Inspect the final folder in Thunderbird and webmail after the chosen mechanism runs. A completed preview is different from an applied move. Check the processing history if an expected action did not occur.
Keep limits visible
AI classification uses a body preview, not full knowledge of your contacts or project history. Conditional sender caching can reuse an assignment without a fresh model call. Start with reviewed folder moves; permanent deletion and forwarding are not reversible through History.
See sender categories and History and Undo. The decision is about where the workflow should run, not proof that AI is more accurate than your existing rules.