跳到主内容
@wquguru
精选75Cloudflare Email Service(Changelog)云与平台

Cloudflare Email Service 9月25日:弃用全局默认退信抑制,新增发送域名级作用域

Email Service - Suppress recipients for one sending domain

原文
发到 X
推荐理由

如果你依赖 Cloudflare Email Service 做多域名群发,这次变更会改变抑制行为的边界。请检查现有集成是否显式传递 scope,并在需要时调整 API 调用或 Dashboard 配置,防止意外扩大或缩小抑制范围。

Email Sending suppressions now have a scope:

邮件发送抑制(suppressions)现在具有作用域:

  • account: The suppression applies to every sending domain and subdomain in your account. This is the default.
  • sending_domain: The suppression applies to one sending domain only. A suppression for mail.myappexample.com does not block mail from myappexample.com.
  • account:该抑制适用于您账户中的每个发送域名和子域名。这是默认设置。
  • sending_domain:该抑制仅适用于一个发送域名。针对 mail.myappexample.com 的抑制不会阻止来自 myappexample.com 的邮件。

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.

最重要的是,邮件发送现在会自动在发送域名级别创建退信和投诉抑制。这通过防止单个发送域名上的问题导致整个账户范围内的收件人被抑制,从而提供了更细粒度的控制。

To add a suppression for one sending domain in the dashboard, go to Email Sending > Suppressions and select Sending domain in Scope. Imports can also set a scope for each row or a default scope.

要在仪表板中为单个发送域名添加抑制,请转到 Email Sending > Suppressions,并在 Scope 中选择 Sending domain。导入功能也可以为每一行或默认作用域设置作用域。

In the API, pass scope when you create the suppression:

在 API 中,创建抑制时传递 scope 参数:

代码 · 7 行
curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/email/sending/suppressions \
  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
    "email": "[email protected]",
    "scope": { "type": "sending_domain", "value": "mail.myappexample.com" }
  }'

The suppressions API returns scope on every suppression. To list the suppressions for one domain, use scope_type=sending_domain&scope_value=mail.myappexample.com. If you omit scope, the API creates an account suppression, so existing integrations continue to work.

Suppressions API 会在每条抑制记录中返回 scope。若要列出某个域名的抑制记录,请使用 scope_type=sending_domain&scope_value=mail.myappexample.com。如果省略 scope,API 将创建一个 account 级别的抑制,因此现有集成仍可正常工作。

Refer to Suppression lists and Manage suppressions for details.

有关详细信息,请参阅 Suppression lists 和 Manage suppressions。

更进一步:量化金融体系

看懂新闻只是起点——沿量化金融路径,把它变成能交付的工程能力

进入量化体系 →

相似阅读

关联信息,但可能不是同一事件