[{"data":1,"prerenderedAt":12},["ShallowReactive",2],{"$fUD-aoJ0hI5GOzFPN-bpVDvgoyK8CDD8KdSVc8xKsiEg":3},{"title":4,"slug":5,"excerpt":6,"category":7,"order":8,"screens":9,"html":11},"Spam check names","spam-check-names","What the names in spam.symbols mean, where to find them, and how to block, allow or tag mail on a specific spam check whatever its total score","settings",3,[10],"aliases","\u003Cp>Every email we receive on a custom domain goes through a series of spam checks. Each check that fires adds (or subtracts) points, and the sum is the \u003Cstrong>spam score\u003C\u002Fstrong>. The checks themselves are listed by name in your webhook payload, under \u003Ccode>spam.symbols\u003C\u002Fcode>, and you can write \u003Ca href=\"\u002Fhelp\u002Falias-rules\u002F\">alias rules\u003C\u002Fa> on those names directly.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> Spam analysis and alias rules are Maker+ features.\u003C\u002Fp>\n\u003Ch2>Where to find the names\u003C\u002Fh2>\n\u003Cp>Every scored payload carries the checks that fired, with what each one added:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-json\">&quot;spam&quot;: {\n  &quot;score&quot;: 9.2,\n  &quot;symbols&quot;: [\n    { &quot;name&quot;: &quot;FROM_BRAND_LOOKALIKE&quot;, &quot;weight&quot;: 5, &quot;description&quot;: &quot;kraken.com.example-attacker.nl&quot; },\n    { &quot;name&quot;: &quot;FROM_LOOKALIKE_DOMAIN&quot;, &quot;weight&quot;: 3, &quot;description&quot;: &quot;kraken.com.example-attacker.nl&quot; },\n    { &quot;name&quot;: &quot;TO_DN_RECIPIENTS&quot;, &quot;weight&quot;: 2, &quot;description&quot;: null }\n  ]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ccode>name\u003C\u002Fcode>\u003C\u002Fstrong> is what you put in a rule. Copy it exactly from a payload rather than guessing.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ccode>weight\u003C\u002Fcode>\u003C\u002Fstrong> is what the check added to the score. A check can fire with a weight of 0: it is listed, adds nothing, and still counts in a rule.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ccode>description\u003C\u002Fcode>\u003C\u002Fstrong> is the detail the check reported, such as the domain it looked at, or \u003Ccode>null\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>To see which checks mark the mail you want to catch, open that email in your logs and view its webhook payload, or look at what your webhook received.\u003C\u002Fp>\n\u003Ch2>Acting on a check: &quot;Spam rule fired&quot;\u003C\u002Fh2>\n\u003Cp>In the alias rules editor, the \u003Cstrong>Spam rule fired\u003C\u002Fstrong> condition matches when any of the checks you name fired on the message:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Action:    Block\nCondition: Spam rule fired  is one of  FROM_BRAND_LOOKALIKE, PHISHED_OPENPHISH\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>It matches \u003Cstrong>whatever the total score\u003C\u002Fstrong>. That is the point of it: a phishing email can score low overall because it passes sender authentication, while one check identifies exactly what it is.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Whole names, any case.\u003C\u002Fstrong> \u003Ccode>phished_openphish\u003C\u002Fcode> matches \u003Ccode>PHISHED_OPENPHISH\u003C\u002Fcode>; \u003Ccode>PHISH\u003C\u002Fcode> matches nothing.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Several names, commas.\u003C\u002Fstrong> The condition matches if any one of them fired.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Only names are accepted\u003C\u002Fstrong> (letters, digits and underscores). A misspelt name matches nothing, and under an \u003Cstrong>Allow\u003C\u002Fstrong> rule that would reject everything, so the editor refuses anything that is not a name.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Unscored mail is not decided by it.\u003C\u002Fstrong> If the spam scanner did not run for a message, the condition is undecidable; when the outcome depends on it, the email is \u003Cstrong>delivered\u003C\u002Fstrong>, not blocked. A message that was scored but on which none of your checks fired is an ordinary &quot;no match&quot;.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Not sure yet? Use \u003Cstrong>Tag\u003C\u002Fstrong> instead of \u003Cstrong>Block\u003C\u002Fstrong>: matching mail is delivered with an \u003Ccode>X-EmailConnect-Tagged: spam\u003C\u002Fcode> header, so you can see what the condition would catch.\u003C\u002Fp>\n\u003Ch2>Common checks\u003C\u002Fh2>\n\u003Cp>The scanner has many checks; these are the ones most useful in a rule. All of them appear by these exact names in \u003Ccode>spam.symbols\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Name\u003C\u002Fth>\n\u003Cth>Fires when\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Ccode>FROM_LOOKALIKE_DOMAIN\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The sender&#39;s domain has the shape \u003Ccode>&lt;name&gt;.com.&lt;domain&gt;.&lt;tld&gt;\u003C\u002Fcode>, for example \u003Ccode>support@brand.com.example-attacker.nl\u003C\u002Fcode>: a registrable-looking name used as part of someone else&#39;s domain. Adds 3\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>FROM_BRAND_LOOKALIKE\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The same shape, with a known brand (a bank, a payment or crypto service, a big tech company) in front. Adds 5, on top of \u003Ccode>FROM_LOOKALIKE_DOMAIN\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PHISHING\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>A link&#39;s visible text names a different site than the one it leads to\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>PHISHED_OPENPHISH\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>A link points to a page listed in the OpenPhish feed of known phishing sites\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DBL_SPAM\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>A domain in the message is on Spamhaus&#39;s list of spam domains\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>R_SPF_FAIL\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The sending server is not allowed to send for the sender&#39;s domain (SPF). Common on forwarded mail, so on its own it proves little\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>VIOLATED_DIRECT_SPF\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The SPF check failed on mail that was not forwarded\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>DMARC_POLICY_QUARANTINE\u003C\u002Fcode>, \u003Ccode>DMARC_POLICY_REJECT\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The message failed DMARC, and the sender&#39;s domain asks receivers to quarantine or reject such mail\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cp>Lookalike domains deserve a word: they \u003Cstrong>pass\u003C\u002Fstrong> sender authentication (SPF, DKIM, DMARC), because the attacker set those up properly for their own domain. Authentication proves who sent a message, not that it is from the brand it names. That is why the lookalike checks look at the shape of the domain instead.\u003C\u002Fp>\n\u003Ch2>Recipes\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Block lookalike-domain phishing, whatever it scores\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Action:      Block\nCondition 1: Spam rule fired  is one of  FROM_BRAND_LOOKALIKE, FROM_LOOKALIKE_DOMAIN\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Block known phishing links, and spam above a threshold\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Action:      Block\nCondition 1: Spam rule fired  is one of  PHISHED_OPENPHISH, PHISHING\nCondition 2: OR  Spam score  greater than  15\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2>When a name stops matching\u003C\u002Fh2>\n\u003Cp>The check names come from the spam scanner. A scanner upgrade can occasionally rename a check, after which a condition naming the old name no longer matches. A \u003Cstrong>Tag\u003C\u002Fstrong> rule on the same names makes that easy to notice: tagged mail stops arriving.\u003C\u002Fp>\n\u003Ch2>Related topics\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Falias-rules\u002F\">Alias rules\u003C\u002Fa> — how conditions, actions and exceptions work\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fspam-filtering\u002F\">Spam filtering\u003C\u002Fa> — where the spam score comes from\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fwebhook-payload-reference\u002F\">Webhook payload reference\u003C\u002Fa> — every field in \u003Ccode>spam\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n",1795012918776]