Email Service - Suppress recipients for one sending domain
- Announced
- Tags
- Email-Service
- Severity
- info, set by
reef/rss-rule-v1 - Source
- https://developers.cloudflare.com/changelog/post/2026-09-25-sending-domain-suppressions/
<p><a href="https://developers.cloudflare.com/email-service/concepts/suppressions/">Email Sending suppressions</a> now have a <strong>scope</strong>:</p> <ul> <li><strong><code>account</code></strong>: The suppression applies to every sending domain and subdomain in your account. This is the default.</li> <li><strong><code>sending_domain</code></strong>: The suppression applies to one sending domain only. A suppression for <code>mail.myappexample.com</code> does not block mail from <code>myappexample.com</code>.</li> </ul> <p>Most importantly, Email Sending now automatically creates bounce and complaint suppressions at the sending-domain level. This provides greater granularity by preventing an issue with one sending domain from suppressing the recipient across your entire account.</p> <p>To add a suppression for one sending domain in the dashboard, go to <strong>Email Sending</strong> > <strong>Suppressions</strong> and select <strong>Sending domain</strong> in <strong>Scope</strong>. Imports can also set a scope for each row or a default scope.</p> <p>In the API, pass <code>scope</code> when you create the suppression:</p> <figure class="nb-code-figure" data-nb-lang="bash"><pre class="astro-code astro-code-themes github-light github-dark nb-shiki-c6xiwz" tabindex="0" data-language="bash" data-nb-lang="bash"><code><span class="line"><span class="nb-shiki-1t8gfj">curl</span><span class="nb-shiki-mdbnqw"> https://api.cloudflare.com/client/v4/accounts/</span><span class="nb-shiki-140thh">$ACCOUNT_ID</span><span class="nb-shiki-mdbnqw">/email/sending/suppressions</span><span class="nb-shiki-dzsirb"> \</span></span> <span class="line"><span class="nb-shiki-dzsirb"> --header</span><span class="nb-shiki-mdbnqw"> "Authorization: Bearer </span><span class="nb-shiki-140thh">$CLOUDFLARE_API_TOKEN</span><span class="nb-shiki-mdbnqw">"</span><span class="nb-shiki-dzsirb"> \</span></span> <span class="line"><span class="nb-shiki-dzsirb"> --header</span><span class="nb-shiki-mdbnqw"> "Content-Type: application/json"</span><span class="nb-shiki-dzsirb"> \</span></span> <span class="line"><span class="nb-shiki-dzsirb"> --data</span><span class="nb-shiki-mdbnqw"> '{</span></span> <span class="line"><span class="nb-shiki-mdbnqw"> "email": "user@example.net",</span></span> <span class="line"><span class="nb-shiki-mdbnqw"> "scope": { "type": "sending_domain", "value": "mail.myappexample.com" }</span></span> <span class="line"><span class="nb-shiki-mdbnqw"> }'</span></span></code></pre></figure> <p>The <a href="https://developers.cloudflare.com/api/resources/email_sending/subresources/suppressions/">suppressions API</a> returns <code>scope</code> on every suppression. To list the suppressions for one domain, use <code>scope_type=sending_domain&scope_value=mail.myappexample.com</code>. If you omit <code>scope</code>, the API creates an <code>account</code> suppression, so existing integrations continue to work.</p> <p>Refer to <a href="https://developers.cloudflare.com/email-service/concepts/suppressions/#suppression-scope">Suppression lists</a> and <a href="https://developers.cloudflare.com/email-service/configuration/suppressions/">Manage suppressions</a> for details.</p>
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.