AntiSpam Block- and Allowlists
Retarus has decided to replace the terms "blacklist" and "whitelist" with "blocklist" and "allowlist" in order to avoid offensive language. We are gradually replacing the terms in all areas, but this means that you may still find the outdated terms in some places at the moment.
myEAS (https://myeas.retarus.com) - Administration - List Management - AntiSpam Detection
EAS (https://eas.retarus.com) - Administration - Email Services - Black- and whitelists
Retarus AntiSpam Detection allows you to use block- and allowlists. They can be located at company, profile and user levels.
AntiSpam Blocklist
The AntiSpam Blocklist allows you to manage the list of all sender addresses from which all messages are automatically rejected. You can block individual addresses, entire domains or single IPv4 addresses. (On user level, only email addresses and domains are possible.)
If you have multiple Retarus customer numbers, select one and click on Show. The table will then display all of the blocked addresses for this customer number. You can sort them alphabetically by clicking on the corresponding column header. Specific entries can be found using the search function - simply enter the full email address in the box and then click on the gray Search button. The search results will then appear in the table. Addresses in this table can exported as a CSV file by clicking on the Download list button.
If you place the mouse over the (
) symbol, you can see who made the most recent update.
To make changes to any of the entries, just click on the entry line you want to modify. Any changes take effect immediately.
To add new items to the list, just click on Add entries. The next screen allows you to add as many entries to the blocklist as you want, but you have to make each entry on a separate line. To save the items you added, click on Save. To return to the list without saving your changes, click on (
).
Entries on the customer- or profile-based AntiSpam Blocklist can look like this:
http://domain.com (or *http://domain.com , asterisks are cut off in the backend) → transformed into a suffix match for “http://domain.com ”. This means that an email from a subdomain (e.g. colleague@marketing.domain.com) would be blocked as well.
It also means that an email from goodguy@somethingdomain.com would be blocked as well.
@domain.com (or *@domain.com or **@domain.com, asterisks are cut off in the backend) → transformed into an exact domain match. Emails from colleague@domain.com will be blocked, but emails from goodguy@somethingdomain.com will not be blocked. Also, subdomains are not blocked: someone@marketing.domain.com would not be blocked.
.domain.com (or *.domain.com or **.domain.com, asterisks are simply cut off in the backend) → transformed into suffix search for “.domain.com”, used to include subdomains. This means that an email from a subdomain (e.g. colleague@marketing.domain.com) would be blocked as well, but an email from goodguy@somethingdomain.com would not be blocked.
badguy@domain.com → exact match for this email address.
94.199.89.121 → exact match for this IPv4 address.
AntiSpam Allowlist
You can edit the allowlist the same way you modify the blocklist, and it similarly applies to your entire company. Emails from all of the sender addresses on the list will be accepted and not checked for spam, although they are checked for viruses using Retarus AntiVirus. You can allow individual addresses, entire domains or single IPv4 addresses. (On user level, only email addresses and domains are possible.)
Entries on the customer- or profile-based AntiSpam Allowlist can look like this:
http://domain.com (or *http://domain.com , asterisks are cut off in the backend) → transformed into a suffix match for “http://domain.com ”. This means that an email from a subdomain (e.g. colleague@marketing.domain.com) would be allowed as well.
This means that an email from badguy@fakedomain.com would be allowed, too.
@domain.com (or *@domain.com or **@domain.com, asterisks are cut off in the backend) → transformed into exact domain match. Emails from colleague@domain.com will be allowed, but emails from badguy@fakedomain.com will not be allowed. Also, subdomains are not allowed: goodguy@marketing.domain.com would not be allowed.
.domain.com (or *.domain.com or **.domain.com, asterisks are simply cut off in the backend) → transformed into suffix search for “.domain.com”, used to include subdomains. This means that an email from a subdomain (e.g., colleague@marketing.domain.com) would be allowed as well, but an email from badguy@fakedomain.com would not be allowed.
goodguy@domain.com → exact match for this email address.
94.199.89.121 → exact match for this IPv4 address.
This behavior is valid for customer-wide and profile-based AntiSpam Allowlists only. Nevertheless, the listed ways of adding domains and email addresses work for CxO Fraud Detection as well, if it is configured there to use the global AntiSpam Allowlist for CxO Fraud Detection. IP addresses do not work for CxO Fraud Detection.