Lernen / Email guides / Was zwischen dem Versand und dem Posteingang passiert

Was zwischen dem Versand und dem Posteingang passiert

2:11 min

Bird answers your send with a 202 in a fraction of a second — but that's a receipt, not a delivery. In this short we follow one message all the way through: the checks it passes on the way out, the IP it leaves from and the reputation that comes with it, the moment the receiving server decides, and the three ways it can end. So the next time a message doesn't arrive, you know which stop to look at.

What we cover

  • What happens between your API call and the sending network
  • How mailbox providers decide inbox, spam, or a hard bounce
  • Reading delivery status from your email stats
Transcript

Auto-generated from the video.

Hey, and welcome back to another video. Uh today I want to walk you through the email delivery pipeline. Um so you set up your API, you set up everything that you do, and then you click send. What actually happens the moment that you click send on an email within the Bird platform?

Now let's have a look. So when you start to send, you have your API set up, you send it to someone, you add or a template or specific message, and the message gets sent. When it reaches our system, we check the content, we check if there's any suppressions on the recipient, and we check if the domain is okay to send from. Now these checks happen within milliseconds and don't necessarily cause any issues. Then dependent on the sending IP that you use, uh there might be a poor history, so your message might get throttled, meaning that we just hold it for a few seconds. But if your reputation is okay, we move on to the final delivery state.

Now here there's a specific gate on the recipient, so either Gmail or Outlook, dependent on who you're sending it to, who checks all of the records if these are all okay. In the event that all of the records are indeed correctly submitted, and we as Bird are allowed to send, the message gets sent into the actual inbox.

Now when receiving on the inbox, there's a few outcomes that can happen. The message can get delivered, which is the happy path. It might be that it gets deferred, so meaning it's on hold, or it needs to get retried, and then upon the retry it can still go into a delivered state, or it might get bounced in the event that the recipient email address actually doesn't exist, or if the address had its own suppression on their end as well.

Then after all of that, all of the events actually get reported back within the Bird system within milliseconds, giving you a full overview of exactly what has happened to your messages, and what state they currently are at. Sending an email is as easy as that.

Uh Um quick review. Happy sending.

Starten Sie mit einem Kanal.
Fügen Sie die anderen hinzu, wenn Sie bereit sind.

Ein Test-API-Key steht Ihnen sofort zur Verfügung. Der Produktivzugang wird freigeschaltet, sobald Sie eine Zahlungsmethode hinzufügen und einen Absender verifizieren.

Sie nutzen Claude Code, Cursor oder Codex? Kopieren Sie einen Setup-Prompt und Ihr Agent installiert die Bird CLI und Skills für Sie. Wählen Sie Ihren:

Cursor