DocsDigest
Back to listLanguage: JA
OpenAICloudflare Developer PlatformJul 15, 2026, 12:00 AM

Email Service, Queues - Subscribe to Email Sending events with Queues

A condensed section focused on the key takeaways first.

Original Post
OpenAIClaude

Quick Digest

Summary

A condensed section focused on the key takeaways first.

openaienmodel: gpt-5-mini-2025-08-07

Subscribe to Email Sending events with Queues

emailqueueseventssmtpdeliverabilitycloudflare

Key Points

  • six lifecycle email events
  • per-domain queue subscriptions
  • payload includes SMTP status

Summary

You can now subscribe to Email Sending events via Queues event subscriptions to receive outbound transactional email lifecycle events for a single sending domain (either a zone apex like example.com or a verified subdomain like send.example.com). Six event types are published: message.delivered, message.deferred, message.bounced, message.failed, message.rejected, and message.complained. Email Routing events are not published on this source.

Key Points

  • Scope: subscriptions are per sending domain (zone apex or verified subdomain).
  • Event types: message.delivered, message.deferred, message.bounced, message.failed, message.rejected, message.complained.
  • Payload: includes message identifiers, recipient, terminal flag, delivery.status, and delivery.smtpStatusCode for each event.
  • Use cases: track deliverability, react to bounces/complaints, drive suppression lists, and implement retry logic.
  • Next steps: create a Queues event subscription scoped to your sending domain and consume events; see the Event subscriptions docs for full payload examples and types.

Practical tip

Treat events as authoritative for outbound lifecycle transitions and use the SMTP status and terminal flag to decide suppression vs retry workflows.

Full Translation

Translations

A translation section that keeps the flow of the original article.

openaijamodel: gpt-5-mini-2025-08-07

Email Service、Queues — Queuesを使ってメール送信イベントを購読する

概要

Queues のイベント購読を通じて Email Sending イベントを購読し、送信されるトランザクショナルメールのライフサイクルイベントをキューで受信できます。

スコープ

  • 各サブスクリプションは 1 つの送信ドメインにスコープされます — ゾーンアペックス（例: example.com）または検証済み送信サブドメイン（例: send.example.com）。

公開されるイベントタイプ

  • message.delivered
  • message.deferred
  • message.bounced
  • message.failed
  • message.rejected
  • message.complained

これらを使用して配信率を追跡し、バウンスや苦情に対応し、抑止（suppression）や再試行（retry）ロジックを駆動できます。Email Routing イベントはこのソースでは公開されません。

イベントペイロード

各イベントにはメッセージの詳細、配信ステータス、および SMTP レスポンスが含まれます:

{ " type " : "cf.email.sending.message.delivered" , " source " : { " type " : "email.sending" , " zoneId " : "023e105f4ecef8ad9ca31a8372d0c353" , " domain " : "example.com" }, " payload " : { " messageId " : "0101018f7d0c4d9a-msg-deadbeef" , " recipient " : "user@example.net" , " terminal " : true , " delivery " : { " status " : "delivered" , " smtpStatusCode " : "250" } } }

詳細と他のイベントタイプおよびサンプルペイロードについては Event subscriptions を参照してください。