Global Email Filters: How to set rules for all mailboxes at once

Global Email Filters in cPanel: Setting rules for all mailboxes simultaneously

With global email filters in cPanel, you can create rules that apply not just to a single mailbox, but to incoming messages for the entire domain. This allows you to centrally manage recurring patterns, unwanted terms, specific senders, or technical characteristics.

While standard email filters are created for a specific email account, global filters apply domain-wide. This is particularly useful if you want to apply a rule to several or all addresses in your domain, for example, to block specific spam patterns, discard messages with certain subject lines, or forward emails based on technical criteria.

What are global email filters?

Global email filters are server-side rules that cPanel applies to incoming messages for a domain. The server checks whether a message meets specific conditions. If it does, the defined action is executed.

For example, a rule can check if the subject contains a certain word, if the sender belongs to a specific domain, or if a specific header is present. The message can then be delivered, discarded, forwarded, or passed to a program.

Difference between standard and global email filters

The most important difference is the scope. A standard email filter is set up for a specific mailbox. A global filter, on the other hand, applies to the domain and can therefore influence multiple mailboxes.

For most individual sorting tasks, you should use standard email filters first. Global filters make sense when a rule should truly apply to several or all addresses of a domain.

When are global filters useful?

Global email filters are particularly useful when you want to handle recurring messages centrally. Typical areas of application include:

• Blocking messages with clearly recognizable spam terms in the subject line
• Discarding emails from specific unwanted senders or domains
• Forwarding specific messages to a central mailbox
• Filtering automated system notifications for multiple addresses
• Domain-wide rules for old or unused contact addresses
• Technical rules for headers, recipients, or specific patterns

If a rule only affects a single mailbox, a standard email filter is usually the better choice. Global filters should be used purposefully and sparingly.

Opening global email filters in cPanel

First, log in to your CURIAWEB client area or directly into cPanel. Then, in the Email section, open the Global Email Filters function.

There, you can see existing global filters and create new rules. Check existing filters regularly so that old or no longer needed rules do not have unintended consequences.

Step 1: Assign a unique filter name

For every global filter, assign a name that clearly describes its function. This makes management easier later, especially when multiple rules are active.

Good examples for filter names are:

• Discard spam subject giveaway
• Forward old domain to info
• Block sender domain
• Sort system notifications centrally

Avoid unclear names like "Filter 1" or "Test". With global rules, comprehensible documentation is particularly important.

Step 2: Define the rule

The rule determines when the global filter should take effect. Depending on the cPanel version, you can check various fields, for example, sender, recipient, subject, message body, or headers.

Step 3: Choose the action

The action determines what happens to a message if the rule is met. Especially with global filters, you should prefer safe actions before discarding or deleting messages directly.

Example: Discarding spam with a specific subject

A typical global filter can discard messages with recurring spam terms in the subject. Example: You repeatedly receive spam emails with the word "giveaway" in the subject.

If you are unsure whether legitimate messages might be affected, you should first not delete the message, but deliver it to a separate folder or forward it to a monitoring address.

Wildcard redirects and regular expressions

For advanced use cases, global filters can work with regular expressions. This allows you to define patterns that capture multiple similar addresses or senders.

An example: You want to recognize senders like test_user1@example.com, test_user2@example.com, or similar variants. A regular expression can be used for this.

test_user.+@example\.com

The character sequence .+ stands for any character. The dot in example\.com is masked with a backslash so that it is interpreted as an actual dot and not as a wildcard.

Why multiple simple filters are often better

Complex global rules are harder to check and more difficult to maintain later. In many cases, it is better to create multiple simple and clearly named filters instead of using one large rule with many conditions.

This has several advantages:

• Each rule is easier to understand.
• Errors can be found more quickly.
• Individual filters can be specifically deactivated or adjusted.
• The order of rules remains easier to follow.
• Tests are simpler and more meaningful.

Testing global filters

Before putting a global filter into production, you should check it using the Filter Test function. You can enter a sample message and see if the rule acts as expected.

After testing, cPanel shows a technical protocol. This protocol indicates whether conditions were met and whether an action would be triggered.

1 Condition is false: $header_subject: contains "Test"
...
10 Filtering has not set up significant delivery.
11 Normal delivery will occur.

This result means the condition was not met and the message would be delivered normally.

Correctly interpreting test results

If the filter does not react as expected, check the spelling, the selected operator, the checked field, and the order of the rules.

Global filters and BCC recipients

A common misconception concerns BCC recipients. The BCC field is usually not transmitted as a visible header to all recipients upon receipt. Therefore, filter rules cannot reliably act based on the BCC field.

If you want to filter messages based on recipient information, use visible fields like To or technical headers, provided they are reliably present. Global email filters are generally not suitable for BCC-based logic.

Common mistakes with global email filters

Best practices for global filters

Global filters are a powerful tool, but should be used in a controlled manner. Especially with commercially used domains, it is important that no legitimate messages are accidentally lost.

Combining global filters and spam filters

Global email filters can reduce spam, but they do not replace a full-fledged spam filter. Spam filters evaluate messages based on many technical and content characteristics. Global filters, on the other hand, only execute the rules you define yourself.

A combination is often useful: the spam filter handles general spam detection, while global filters specifically process recurring patterns that are particularly relevant to your domain.

Summary

Global email filters in cPanel allow you to set rules for the entire domain. This allows messages for multiple mailboxes to be processed, sorted, forwarded, or discarded simultaneously.

Because global filters act domain-wide, they should be planned and tested with extra care. Use clear filter names, simple conditions, and safe test actions. Deletion rules and Regex patterns should only be used when you are sure no legitimate messages are affected.

For individual mailbox rules, standard email filters are usually better suited. Global filters are the right choice when a rule is intentionally intended to apply to all or several addresses of a domain.

Tip: Always test global filters with sample messages before deploying them. Especially deletion rules and Regex patterns should never be activated unchecked.