What is a sending pipeline?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

A sending pipeline is the full path a single email takes from the moment you hit send to the moment it lands (or doesn't) in an inbox. It's not one step, it's a chain of them, and if any link in the chain breaks, your mail doesn't arrive.

But Here's what actually happens when you send a campaign. First, your ESP pulls the recipient list and runs it against your suppression list to drop anyone who has bounced, unsubscribed, or complained. Then it renders the HTML and plain-text versions for each recipient, swapping in personalization tokens along the way. Then it signs each message with your DKIM key. Then the messages go into a delivery queue, where the system decides pacing, which IP to send from, and which receiving domain gets mail in what order. Finally, the pipeline opens an SMTP connection to Gmail or Outlook or whoever, hands the message over, and listens for the response.

The response is where the pipeline earns its keep. A clean 250 response means delivered. A 4xx means try again later, and the queue retries on a schedule. A 5xx means bounce, and the pipeline writes that address to your suppression list so you don't hit it again. Opens, clicks, and unsubscribes get logged too, usually streamed to you as webhook events.

Knowing these stages exist matters because every deliverability problem lives in one of them. "Why didn't my email arrive?" has very different answers depending on where it got stuck. Was it suppressed on the way out? Did rendering break because a personalization token was empty? Did DKIM signing fail because a DNS change hadn't propagated? Did the message hit the queue fine but get deferred by the receiving server? Each stage leaves different footprints.

If you're picking an ESP or auditing the one you have, ask for visibility into every stage, not just "delivered" and "bounced." The more granular the pipeline logs, the faster you can find where mail is leaking. When you want a second pair of eyes on where your pipeline is dropping messages, Review My Emails does exactly that (why not try us ;)).

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Map your sending pipeline and find the leak.

I want to map my own sending pipeline end to end so I can find where mail is getting stuck or lost. Help me: 1. Identify the stages my current ESP actually exposes (logs, dashboards, webhooks) 2. Pinpoint which stage is the most likely culprit for the symptoms I'm seeing 3. Build a simple runbook I can use when a specific campaign underperforms My setup: - ESP: Klaviyo, Customer.io, SendGrid, Postmark, etc. - Volume: daily / monthly - Current symptom: [low inbox placement, random bounces, specific ISP issues, rendering bugs] - Webhook/event access: yes, into warehouse / yes, raw / no - DKIM/SPF/DMARC status: aligned / partial / unknown

Edit the yellow boxes, then send to the AI of your choice.