Webhooks for failures
If you want to receive realtime notifications about failed deliveries, you can set up a failures webhook. You will receive notifications for both synchronous failures (failures during the SMTP handshake) as well as asynchronous failures (messages that were initially accepted, but for which we received a failure report later on).
Synchronous vs. asynchronous
The SMTP protocol allows receiving servers to either accept or reject a message. When a message is rejected, SMTPeter simply makes a call to the URL that you set up for the webhook. However, when a message is accepted, it still is possible that the receiving server sends back a bounce email later on to report that the delivery failed after all. These asynchronous errors are also picked up by SMTPeter, and when they are recognized, are also passed to the failures webhook.
Mail servers often use the official Delivery Status Notification standard for sending back bounce messages. This standardized format allows SMTPeter to automatically recognize bounces, log them and report them via the webhooks. However, this standard has not been adopted by all mail servers, and even a couple of big email senders still send back notifications in a format that they invented themselves. Although we do our best to recognize all types of bounce messages and pass them on to the webhooks, it is not always possible to process such non-standardized asynchronous bounces, and to pass them to webhooks.
If you want to receive all failures, even the ones that we did not recognize, you can set up a webhook for bounces besides the failure webhook.
SMTPeter uses HTTP POST calls to send the data to you. This can be done over HTTP or over HTTPS. The following variables are used in the POST calls:
|id||Unique id of the message for which this is a failure report|
|recipient||Email address for which this is a failure|
|state||State in the smtp protocol where the failure occured ("bounce" for async bounces)|
|code||Optional smtp error code|
|extended||Optional extended smtp status code|
|description||Optional description of the error|
|time||Timestamp of the error|
|action||Action that occurred|
|tags||Tags you associated with this mailing|