[{"data":1,"prerenderedAt":12},["ShallowReactive",2],{"$ffR_wqrjo0qafBYhiuhTN53Um8HtI6TwhYyI6zW54OL4":3},{"title":4,"slug":5,"description":6,"category":7,"order":8,"screens":9,"html":11},"How to whitelist or block sender domains","whitelist-sender-domains","Restrict your alias to only accept emails from trusted sender domains, or block unwanted ones, using alias rules","use-cases",2,[10],"aliases","\u003Cp>Need to make sure your alias only accepts emails from specific companies or domains? Or want to block a noisy sender? Alias rules let you create an allowlist (whitelist) or blocklist for any alias in just a few clicks.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> Alias rules require a Maker plan or higher.\u003C\u002Fp>\n\u003Ch2>Allowlisting: accept only trusted domains\u003C\u002Fh2>\n\u003Cp>The most common use case is restricting an alias so it only processes emails from domains you trust. For example, if your \u003Ccode>invoices@yourcompany.com\u003C\u002Fcode> alias should only accept emails from your two suppliers:\u003C\u002Fp>\n\u003Ch3>Step-by-step\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Open the alias you want to protect\u003C\u002Fli>\n\u003Cli>Go to the \u003Cstrong>Rules\u003C\u002Fstrong> tab\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Add rule\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Set rule type to \u003Cstrong>Allow\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Set criteria to \u003Cstrong>Sender domain\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Enter your trusted domains: \u003Ccode>@supplier-one.com\u003C\u002Fcode>, \u003Ccode>@supplier-two.com\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Save the rule\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>That's it. Only emails from those domains will trigger your webhook. Everything else is silently rejected.\u003C\u002Fp>\n\u003Ch3>How the allowlist works\u003C\u002Fh3>\n\u003Cp>When you create one or more \u003Cstrong>Allow\u003C\u002Fstrong> rules:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Emails matching \u003Cstrong>any\u003C\u002Fstrong> allow rule are accepted\u003C\u002Fli>\n\u003Cli>Emails matching \u003Cstrong>no\u003C\u002Fstrong> allow rule are \u003Cstrong>rejected\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>If you also have block rules, those are checked first\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This means you don't need to think about blocking — just define who's allowed and everything else is excluded automatically.\u003C\u002Fp>\n\u003Ch2>Blocklisting: reject specific domains\u003C\u002Fh2>\n\u003Cp>If you want to accept most emails but block a few noisy or unwanted senders:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Open the alias\u003C\u002Fli>\n\u003Cli>Go to the \u003Cstrong>Rules\u003C\u002Fstrong> tab\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Add rule\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Set rule type to \u003Cstrong>Block\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Set criteria to \u003Cstrong>Sender domain\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Enter the domain(s) to block: \u003Ccode>@spam-company.com\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Save the rule\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Combining domain and email filters\u003C\u002Fh2>\n\u003Cp>You can create multiple rules on the same alias. Common patterns:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Allow a company but block one person:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Rule 1 (Allow): Sender domain = @bigcorp.com\nRule 2 (Block): Sender email = noreply@bigcorp.com\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Allow multiple partner domains:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Rule 1 (Allow): Sender domain = @partner-a.com, @partner-b.com, @partner-c.com\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Block competitors from a shared inbox:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Rule 1 (Block): Sender domain = @competitor1.com, @competitor2.com\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2>Notifying blocked senders\u003C\u002Fh2>\n\u003Cp>By default, blocked emails are silently rejected. If you want the sender to know their email was filtered, enable \u003Cstrong>Notify sender when blocked\u003C\u002Fstrong> on the rule. This sends them a short rejection notice.\u003C\u002Fp>\n\u003Cp>Use notifications when:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Legitimate senders might accidentally be blocked\u003C\u002Fli>\n\u003Cli>You want to signal that the alias is restricted\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Skip notifications when:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Blocking spam or unwanted marketing\u003C\u002Fli>\n\u003Cli>You don't want to confirm the alias is active\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Tips\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Use domain rules over individual email rules\u003C\u002Fstrong> — they automatically cover new employees or shared addresses at that company\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Start simple\u003C\u002Fstrong> — one allow rule with your trusted domains is often all you need\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Test first\u003C\u002Fstrong> — send a test email from an allowed and a non-allowed address to verify the rule works\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Combine with spam filtering\u003C\u002Fstrong> — rules handle your specific allow\u002Fblock needs while spam filtering catches general junk\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Related\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Falias-rules\u002F\">Alias rules reference\u003C\u002Fa> — full details on rule types, evaluation order, and all filter criteria\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fspam-filtering\u002F\">Spam filtering\u003C\u002Fa> — built-in spam protection that works alongside rules\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Falias-options-explained\u002F\">Alias options\u003C\u002Fa> — other alias configuration options\u003C\u002Fli>\n\u003C\u002Ful>\n",1781207681888]