My application already handles bounces

If you are using a 3rd party application or your custom application already has built-in bounce processing, you have two options to support bounces using SocketLabs.

Most 3rd party bounces are handled by processing messages from a POP email account. We can support that via the following:

  1. We can turn off our platform's bounce processing and bounces will be processed just as they were before you began using our service. There are, however, a few drawbacks with this setup that you should consider.
    1. You will not receive the synchronous failures/bounces that occur during the SMTP conversation, only the bounce backs that are returned as messages to your specified return-path address - i.e.
    2. You will have to deploy your own DKIM DNS TXT records.
    3. You will have to apply separately for Feedback Loops based on your DKIM records and have it directed back to SocketLabs for us to process with your account.
  2. SocketLabs is configured by default to handle all bounces and feedback loops. We can forward all bounces and failures as Non-Delivery Reports(NDRs) to the POP email account that your software uses to process bounces so your lists are automatically updated accordingly. This is the ideal setup as you can configure it yourself in the Control Panel, and it enables us to track accurate statistics for your account and provide all of the DKIM and Feedback Loop support for you.
    1. To configure SocketLabs to forward your Non-Delivery Reports, select the Configuration Drop-down from the menu bar at the top of the page and select Non-Delivery Reports.
    2. The configuration page allows for a number of different customized options. You  first need to Enable the feature. From there you will see the following options:
      1. NDR to Original Sender
        Enabling this option will send an NDR message to the original sender when a message fails delivery during the SMTP transmission process. This option can be enabled alone or in conjunction with "NDR to Static Address"
      2. NDR to Static Address
        You may also provide a static address to receive NDRs when a message fails delivery during the SMTP transmission process. This option can be enabled alone or in conjunction with "NDR to Original Sender"
      3. Send NDR on Suppression
        Enabling this option will send an NDR in cases where a message is never attempted for outbound delivery due to the address existing on your Suppression List.
      4. Bounce Message Recipient
        In order to prevent a potential infinite loop, bounced messages are often returned without the original "From" address. For this reason, you can only specify a static address to receive all bounced messages.
      5. Feedback Loop Recipient
        Specify an address at which you would like to receive any spam complaints generated in response to your messages.

If you need us to support the forwarding of Non-Delivery reports, please contact Support and provide the email account to which you would like them to be forwarded.


Further reading can be found here:

How SocketLabs Handles Non-Delivery Reports & Bounces

Synchronous vs. Asynchronous Failures (NDRs/Bounces)