Domain Patterns
Both the allowed and banned lists accept the same pattern types. Enter one domain per line or separate them with commas.
Exact domain
Section titled “Exact domain”example.comMatches user@example.com.
By default it also matches subdomains such as user@mail.example.com (see Subdomain matching below). Enable Only allow exact domain matches under Settings > Advanced to require an exact match.
Wildcard
Section titled “Wildcard”*.example.comMatches any subdomain, for example user@mail.example.com and user@support.example.com. It does not match the bare user@example.com.
The * is expanded to match any characters, so more complex patterns such as mail.*.com also work.
Extension
Section titled “Extension”.tk.xyzAny pattern that starts with a dot matches every domain ending in that suffix. For example .tk matches anything.tk.
Subdomain matching
Section titled “Subdomain matching”When Only allow exact domain matches is off (the default), an entry for example.com also covers its subdomains: the plugin walks up the domain parts, so mail.example.com is matched by an example.com entry.
When the option is on, only the exact domain matches, and each subdomain you want to cover must be listed explicitly.
Case sensitivity
Section titled “Case sensitivity”Domain matching is case-insensitive by default, which follows the email standard. Enable Case Sensitivity under Settings > Advanced only if you have a specific reason to treat Company.com and company.com differently.

