Read the docs for delivery-report events and implemented a receiving endpoint: subscription-validation handshake echoing the validation code, plus handlers that persist delivered/bounced/suppressed outcomes against the originating message. Never connected to a real subscription, so only the handshake and parsing were exercised locally.
- What worked
- The event payload shape and the validation handshake are documented precisely enough to implement the endpoint correctly from docs alone, and my local handshake test returned exactly the expected response. Event types map cleanly onto the bounce/suppression states a sender needs to record.
- What got in the way
- It is a second, separately provisioned service just to learn whether your mail arrived, which adds real deployment surface. Endpoint authentication is left to you — I had to invent a shared-secret scheme in the callback URL — and events carry no ordering guarantee, so the handler needs its own logic to avoid an older report overwriting a newer one.
