Skip to Content
Browse documentation

Configure UAPP Email Filters

Build ordered mailbox rules with message conditions, folder actions and terminal actions, including legacy conversion and processing order.

Open Hosting → Email → Email Filters. Select an existing owned mailbox. These rules run after domain filters and before Roundcube Sieve rules.

Rule fields

ControlMeaning
TargetOwned mailbox receiving the filter.
Filter enabledEnables or disables the saved ruleset.
Rule name / enabledIdentifies a rule and controls whether it runs.
MatchRequire all conditions or any condition.
Message fieldFrom, To, Cc, Subject, Reply-To, List-ID, body, message size in bytes or spam score.
Comparison / valueText contains, equals, begins, ends or regular-expression match; numeric fields use above/below.
Actions / destinationsCopy or move to a mailbox folder, redirect to an address, discard, or stop processing.
Rule orderMove rules up/down to control evaluation order.

Add at least one rule. Limits are 100 rules per filter, 20 conditions and 10 actions per rule. Each rule can have multiple copy actions followed by at most one move, redirect, discard or stop action; the terminal action must be last. Folder names, addresses, numeric values and patterns undergo server validation.

Copy actions continue processing. A move, redirect, discard or stop terminates the relevant downstream handling, including later account/Sieve processing. Use Domain Filters to understand the earlier stage.

Save and maintain

Build the conditions and ordered actions, review destructive/terminal behavior, then save. Enable, disable and delete actions apply to the selected ruleset. Demo mode blocks mutations. Test with controlled mail before relying on a production rule.

Legacy filters may require an explicit supported conversion. Review the offered conversion and resulting rules; unsupported legacy syntax cannot be assumed convertible. Conversion preserves a legacy backup, but deleting the filter can also remove its associated backup files. Preserve a separate recovery copy when required.

Discard and rule order can hide delivery

Review broad matches and terminal actions carefully. A successful save does not prove that a rule matches the intended messages. Avoid redirect loops and confirm both matching and nonmatching mail behavior.