An allowlist rule in AliasFleet lets mail from a trusted address, domain, or pattern bypass automated filtering and reach the destination inbox directly. One rule covers every alias on the account. This guide covers adding, pausing, and deleting allowlist rules, and the plan limits on each rule type.
An AliasFleet account is required. Exact Match rules are available on every plan. Domain Match and Wildcard Pattern rules require a Pro or Business plan. The sender address, domain, or pattern to allow must be known before starting.
What an allowlist rule does#
Mail that matches an active allowlist rule skips automated filtering and is delivered to the destination inbox. The Sender Rules page banner states the same behaviour: senders matching active allowlist rules bypass automated filtering and deliver directly to inboxes.
A rule applies to the whole account, not to a single alias. Allowing noreply@bank.com therefore sends mail from that address to every alias on the account, including a shopping alias and a newsletter alias. Because the scope is account-wide, rules should stay narrow. A domain rule allows every address on that domain, which is wider than a single-address rule.
What are the three rule types?#
Exact Match matches one specific address. Use it for a single sender, such as a bank notification address or a newsletter sender.
Example: noreply@bank.com
Domain Match matches every address from a given domain. Use it when a whole organisation is trusted and its mail arrives from many addresses.
Example: entering github.com allows all mail from any GitHub system address.
Wildcard Pattern matches addresses that fit a pattern. Use * to match any number of characters and ? to match a single character.
Example: billing-*@company.com matches billing-team@company.com and billing-2026@company.com, but not support@company.com.
Domain Match and Wildcard Pattern rules are Pro and Business features. On a Free plan, only Exact Match rules can be added.
Worked example: allowing GitHub mail through#
GitHub verification mail keeps being filtered on an account with one alias for shopping and one for newsletters. GitHub sends from several addresses, so one exact address is not enough. The fix is a single Domain Match rule:
- Open the Sender Rules page: Go to the Sender Rules page and select the Allowlist tab.
- Start a new rule: Click Add Rule. The Add to Allowlist dialog opens.
- Choose the rule type: Select Domain Match (All senders from domain).
- Enter the domain: Type
github.comin the Email Address or Match Pattern field. - Add a reason (optional): Enter a short reason, such as "GitHub verification and notification mail", so the purpose of the rule stays clear later.
- Save the rule: Click Create Rule. The rule takes effect at once and appears in the list.
After saving, mail from any GitHub address reaches every alias on the account, including the shopping alias and the newsletter alias. If GitHub later sends from a subdomain, check Include subdomains on the rule, or add a separate rule for the subdomain.
How do I add an allowlist rule?#
- Open the Allowlist tab: Go to the Sender Rules page and select Allowlist.
- Start a new rule: Click Add Rule. The Add to Allowlist dialog opens.
- Choose the rule type: Select Exact Match (Single sender email), Domain Match (All senders from domain), or Wildcard Pattern (Using * or ?).
- Enter the address, domain, or pattern: Type the value in the Email Address or Match Pattern field. For a Domain Match rule, check Include subdomains only when subdomains of that domain should also be allowed.
- Add a reason (optional): Enter a short reason, up to 255 characters, so the purpose of the rule stays clear later.
- Save the rule: Click Create Rule. The rule takes effect at once and appears in the list.
How do I pause or delete a rule?#
Each rule has a toggle. Switching a rule off pauses it: mail from that sender is filtered by the default settings again, while the rule stays on the list and can be switched back on at any time. Pausing suits a temporary change, for example stopping a broad rule while its scope is checked, without losing the rule.
To remove a rule permanently, click the trash or menu icon on the rule and confirm the deletion. The rule disappears at once. Deletion cannot be undone from the list, so pause a rule that may be needed again instead of deleting it.
A saved pattern cannot be edited. The dialog states that patterns are fixed to keep delivery records consistent. To correct a pattern, delete the rule and add a new one.
How do I check whether a rule is working?#
The metric strip above the list shows a count of emails delivered under the allowlist rules. A rising count shows the rules are matching mail. A count of zero means no rule has matched an incoming email yet. That may mean the sender has not mailed since the rule was added, the address or pattern is wrong, or the rule is paused.
The search bar above the list filters rules by address or pattern. Typing part of an address or pattern narrows the list to matching rules, which helps when the account holds many rules.
What if allowed mail still does not arrive?#
Allowed mail that still does not arrive usually points to one of four causes. First, check whether the rule is paused: a paused rule has no effect, so switching it back on restores delivery. Second, check the scope of a Domain Match rule: with Include subdomains unchecked, mail from a subdomain of the allowed domain is not covered, so the rule needs the box checked or a separate rule for the subdomain. Third, check the pattern: a Wildcard Pattern rule must contain at least one * or ? character and must not contain spaces, and a pattern that is too narrow misses the sender. Fourth, check whether the sender address differs from the allowed value, for example a changed local part or a different sending domain, and add a rule for the exact variant.
If mail from a sender on an allowlist rule still does not arrive and none of these causes apply, the problem sits outside sender rules, for example a delivery fault at the destination inbox. For the wider sequence when an alias starts receiving unwanted mail, see When an Alias Starts Getting Spam, Contain It and Replace It.
Related guides#
- Using Sender Rules: how blocking rules work, and the full list of rule types.
- Blocked Emails Explained: what happens to blocked mail and how to read blocked counts.