With global email filters In cPanel, you can process incoming messages based on defined rules at the level of your cPanel account.
Unlike a normal email filter, which is set up for a specific mailbox, a global filter has a significantly larger scope. This makes it possible to create rules that do not affect just a single email address.
In this guide, we will show you how to create a global email filter in CURIAWEB, define conditions and actions, combine multiple criteria with each other, and safely test the rule.
Important: Global filters can affect significantly more messages than a filter for a single email account. A misconfigured rule can therefore impact multiple addresses of your hosting account.
What is the difference between email filters and global email filters? #
cPanel provides two separate filter areas.
Under Email filter manage rules for a specific email account. One there for info@deine-domain.ch created rule is limited to this account.
Global email filters work against this at the level of the cPanel account and can therefore affect a much larger portion of incoming email traffic.
Rule of thumb: If a rule only affects a specific mailbox, use a standard email filter if possible. You should only use global filters if the rule is intentionally meant to apply at the account level.
We show the setup of account-related rules at Create and manage email filters in cPanel.
When is a global email filter useful? #
A global filter can be useful if a clearly defined rule is to be applied independently of an individual mailbox.
This can be, for example, a technical or organizational rule that is relevant for several incoming addresses.
Precisely because the scope of impact is greater, it should be checked beforehand whether a filter for a single email account is not sufficient.
When should you not use a global filter? #
If you only have messages in your inbox info@deine-domain.ch you want to sort, a global filter is usually not required for this.
The same applies to individual user rules or simple automatic sorting of a specific mailbox.
The smaller the required scope of a rule, the easier it is to control and the lower the risk of unintended consequences.
1. Open Global Email Filters in cPanel #
Log in to your CURIAWEB cPanel.
Scroll to the section on the homepage Email and click on Global email filters.
Here you can see already existing global filters and create new rules.
Attention: Before creating a new rule, first check the existing global filters. A rule with a similar function may already exist.
2. Create new global filter #
Click the button to Creating a new filter.
cPanel then opens the global filter configuration.
As with account-related filters, the rule basically consists of one or more conditions and at least one action.
Simplified:
If condition met → execute action
3. Assign a meaningful filter name #
Give the global filter a name that clearly describes its purpose.
Avoid terms such as:
Filter 1
or:
Test
A description that will help you recognize what the rule does later is better.
For example:
Filter specific sender
or:
Process automatic system messages
With multiple global rules, clear names make later troubleshooting considerably easier.
4. Select email feature to test #
In the next step, you select which part of a message should be checked.
Depending on the cPanel configuration, various criteria may be available, for example:
- Sender
- Recipient
- Subject
- Return address
- News content
- Header Information
- spam-related values
You can see the specific criteria directly in your cPanel.
5. Define comparison operator #
Next, you determine how cPanel should compare the selected component with your value.
Depending on the selected criterion, operators such as the following can be offered, for example:
- equals
- contains
- does not contain
- starts with
- ends with
- matches a regular expression
The choice of the operator largely determines how broadly or narrowly your rule works.
„Do not confuse “equals„ and “contains" #
If a condition equals used, the tested value must match accordingly and exactly.
At contains however, the occurrence of the specified value within the tested field is sufficient.
A rule like:
Subject contains "Invoice"
can therefore, for example, also have a subject line like:
Your invoice for August
capture.
With global filters, you should be especially careful with very general "contains" rules because they potentially affect messages for multiple recipients.
6. Enter comparison value #
Enter the value that the rule should trigger on now.
If you want to check a specific sender, that could be, for example:
system@beispiel.ch
For a subject rule, a value could be, for example:
Status report
Check the spelling carefully and consider what other legitimate messages might also match this condition.
Practical Tip: Before saving, ask yourself not only „Which emails do I want to capture?“, but also „Which emails might accidentally match this condition as well?“
7. Select action #
Once the condition is established, you determine what cPanel should do with a matching message.
Depending on the server configuration, various actions are available. These may include, for example, delivery to a defined destination, forwarding or redirection actions, or discarding a message.
You can see which options are available directly in the filter configuration.
Use destructive actions with extreme care #
An action that discards or removes messages should only be used in a global filter with a very precise condition.
An improperly formulated rule could otherwise affect legitimate messages from multiple email addresses.
Recommendation: When initially testing a global rule, avoid using a destructive action if possible. First, check with safer processing to see if really only the desired messages are captured.
8. Add multiple conditions #
If a single condition is not precise enough, you can add further criteria.
This makes it possible, for example, to check not only the subject but also the sender of a message.
Several conditions must be logically linked together.
Use AND connection #
At a AND operation the linked conditions must be met together.
For example:
Sender contains "@beispiel.ch" AND Subject contains "Statusbericht"
A message with the correct subject line but a different sender would not fully satisfy this combination.
Therefore, UND rules can be helpful to narrow down a global filter more precisely.
Use OR operation #
At a OR operation is it sufficient if one of the conditions is met.
For example:
Subject contains "Status Report" OR Subject contains "System Report"
This rule covers a broader area than an AND operation.
Attention: Especially in the case of global filters, an additional OR condition can greatly expand the scope of impact. Check carefully whether every single OR condition on its own is allowed to trigger an action.
9. Save filters #
Check the complete structure once again before saving:
- Is the filter name unique?
- Is the correct email feature checked?
- Is the comparison operator appropriate?
- Is the comparison value correct?
- Are multiple conditions correctly linked?
- Is the chosen action really intended?
Then save the global filter.
The rule should then appear in the overview of your global email filters.
10. Test global filter with an appropriate message #
Now send a test message that must clearly fulfill the defined rule.
For example, if your filter is set to:
Subject contains "Status Report"
React, send a test email with an appropriate subject.
Then check whether the configured action was actually executed.
11. Be sure to also perform a negative test #
With a global filter, the negative test is particularly important.
Send a second message explicitly stating the rule not may fulfill.
If the filter is set to Status report reacts, the second subject line could be, for example:
Normal customer inquiry
This message cannot be processed due to the tested rule.
Basic rule: A global filter is only meaningfully tested once you have controlled both a desired match and at least one non-match.
12. Testing multiple recipients #
Since a global filter is not limited to a single mailbox, you should also consider different recipients for a relevant rule.
For example, if your hosting has the following accounts:
info@deine-domain.ch
and
verkauf@deine-domain.ch
you should check what impact the rule has on messages to both addresses.
This allows you to see whether the global scope actually matches the desired behavior.
Check filter order #
When multiple global filters are set up, their order can affect processing.
A general rule may already handle a message in a way that affects subsequent filters.
Depending on the configuration, cPanel offers options in the filter overview to manage the order of existing filters.
Check this order, especially if a new rule looks correct on its own but does not produce the expected result when interacting with existing filters.
Specific rules and general rules #
The more generally a filter condition is formulated, the more messages it can capture.
For example, a rule for a complete email address is much more specific than a rule that only reacts to a frequently occurring word in the subject line.
This distinction is particularly important for global filters.
Practical Tip: The larger the scope of a filter, the narrower its condition should normally be formulated.
Do not use global filters as a replacement for spam filters #
While a global email filter can react to certain characteristics of unwanted messages, it is not a complete replacement for actual spam detection.
Simple rules like:
Subject contains "Gewinn"
can also affect legitimate messages and are too inaccurate for reliable spam classification.
Dedicated spam filters are available for general spam detection.
We show how to configure the cPanel spam filters under Configure spam filter in cPanel.
Distinguish between global filters and SpamExperts #
Global email filters in cPanel are rule-based features within your hosting account's email processing.
They are not the same as an external or upstream email security solution like SpamExperts.
A global cPanel filter processes messages based on conditions you define. A specialized spam filter solution, on the other hand, analyzes emails using dedicated methods for detecting unwanted or malicious messages.
Therefore, the systems perform different tasks and should not be confused with one another.
Do not use global filters as security proof #
A rule based on a sender address does not mean that the visible sender has been technically verified.
Email sender information can be manipulated.
A global filter like:
Sender is chef@deine-domain.ch
should therefore not be used to automatically place special trust in a message or to bypass security checks.
Safety: Email filters automate the processing of messages. They do not replace sender authentication and do not replace security checks.
Global filters and redirects #
If you merely want to forward all messages from a specific address to another address, you usually do not need a global filter for that.
A standard redirect is clearer for this purpose.
We show you how to set them up at Set up email forwarding in cPanel.
Global filters and catch-all #
The standard address or a catch-all also fulfills a different task.
The default address determines how messages sent to non-existent recipients of a domain are handled.
A global filter, on the other hand, checks messages against defined filter conditions.
We explain how to configure unknown recipients at Default Address in cPanel: Catch-All and Unknown Recipients.
Use regular expressions only when specifically needed #
For certain filter conditions, cPanel can support regular expressions.
This allows defining complex patterns. At the same time, faulty or overly broad patterns can capture many more messages than intended.
With a global filter, this risk is particularly relevant because not just a single mailbox can be affected.
Therefore, only use regular expressions if you understand the pattern being used and can test it adequately.
Global filter does not work #
If a rule does not work as expected, check its conditions first.
Check in particular whether the correct message component was selected, the operator matches the desired comparison, and the entered value is spelled correctly.
In the case of multiple conditions, you should additionally check the AND or OR operations.
Also check the order of existing global filters.
Global filter catches too many messages #
When legitimate news is unexpectedly affected, the rule is probably too broadly drafted.
Check if you can restrict the condition by an additional feature.
For example, instead of just:
Subject contains "report"
to use, an additional condition for a specific sender or recipient could make the rule more precise.
Deactivate or modify a problematic rule as early as possible before further legitimate messages are affected.
Global filter captures too few messages #
If expected messages are not recognized, the condition may be too strict.
An exact comparison can fail, for example, if a subject line differs slightly.
Then check if another operator makes more sense. However, extend the rule only as much as necessary.
An important email has disappeared #
If an expected message does not appear in the designated mailbox and global filters are set up, you should include them in the troubleshooting process.
Check in particular rules with actions that move, redirect, or discard messages.
Then check the account-related filters of the actual recipient mailbox as well.
If it remains unclear how the message was processed, you can use the cPanel function Track delivery use.
We will show the procedure in the next article under Track email delivery in cPanel.
Edit existing global filter #
To do this, open:
Email → Global Email Filters
Find the desired filter and open the edit function.
Change the required conditions or actions and then save the configuration.
Perform a positive and a negative test again after every significant change.
Clear global filter #
If a rule is no longer needed, you can remove it in the global filters overview.
Check the name and function of the rule before deleting it so that you don't accidentally remove a filter that is still needed.
Deleting a global filter removes the filter rule. It does not delete email accounts.
Be careful before deleting an unknown rule. #
If you did not create an existing global filter yourself and do not know its purpose, you should not delete it hastily.
First, check its conditions and actions and try to determine what task it performs.
Especially in the case of long-standing hosting accounts, rules can be part of a deliberately established email configuration.
Important: „I don't know what this rule is for“ does not automatically mean it is redundant. Document existing rules and only change unknown configurations once their function has been clarified.
Document filter rules #
When using multiple global filters, it is worth documenting their purpose in a comprehensible way.
Use unique names and keep more complex rules as clear as possible.
When multiple people are administering a hosting account, it should be apparent why a global rule exists and which messages it is intended to affect.
This makes later changes easier and prevents important filters from being accidentally removed or created twice.
When is an account-based filter the better solution? #
If you find during creation that your rule actually only affects a single mailbox, you should check again whether a standard email filter is more suitable.
A smaller scope of action means:
- easier troubleshooting
- fewer unintended effects
- clearer assignment of the rule
- easier later management
You can find the instructions for this at Create and manage email filters in cPanel.
Basic rule: Use global filters only as globally as necessary. If a rule can be limited to a single mailbox, the account-specific variant is usually easier to control.
Summary #
You can find global email filters in your CURIAWEB cPanel under Email → Global Email Filters.
They generally function similarly to account-based filters: you define one or more conditions and specify which action should be executed when messages match. The decisive difference is the larger scope of operation.
Therefore, use conditions that are as precise as possible, pay attention to AND and OR operators when using multiple criteria, and also check the order of the filters when using multiple ones.
Test new rules with messages that are supposed to trigger the filter as well as messages that must explicitly not be affected. Destructive actions such as discarding emails should only be used once the rule has been reliably tested.
If a rule only affects a single mailbox, a standard email filter is usually the clearer solution.
