Delivery bounced
The message could not be delivered, as reported by the sending provider.
This can have a side effect on the subscriber: they are moved to
bounced so later sends skip them, which also emits
subscriber.unsubscribed with reason: bounced. A permanent (hard)
bounce does that at once, and also stops the address on every other
newsletter on Commune. A transient (soft) bounce, such as a full
inbox, does it only on the third one in a row to that address, from
any newsletter on Commune, with no delivery to it in between; then the
same as a hard bounce. Until then the subscriber stays subscribed
and this event arrives alone.
Two kinds of email reach this topic. data.source is
article_send for an article the creator sent to the list and
automation for one send_email step of an automation run. It
decides which pair of ids is filled in; the other pair is null.
This is a breaking change from the shape that only ever carried
an article, described on the body schema.
Delivered as a single HTTPS POST to the consumer's registered endpoint, with the message as the JSON request body. Respond 2xx to acknowledge. Anything else, or a timeout, is retried with backoff, so acknowledge fast and do the work afterwards.
Loading...
Waiting for a request to be sent.