Lernen / E-Mail-Anleitungen / Was zwischen dem Versand und dem Posteingang passiert
Was zwischen dem Versand und dem Posteingang passiert
2:11 Min.
Bird beantwortet Ihren Send mit einem 202 in Bruchteilen einer Sekunde — aber das ist eine Empfangsbestätigung, keine Zustellung. In diesem Short verfolgen wir eine Nachricht den ganzen Weg: die Prüfungen, die sie auf dem Weg nach draußen durchläuft, die IP, von der sie abgeht, und die Reputation, die damit verbunden ist, den Moment, in dem der empfangende Server entscheidet, und die drei möglichen Ausgänge. Wenn also das nächste Mal eine Nachricht nicht ankommt, wissen Sie, an welcher Stelle Sie nachschauen müssen.
Was wir behandeln
- Was zwischen Ihrem API-Aufruf und dem Sendenetzwerk passiert
- Wie Postfachanbieter über Posteingang, Spam oder einen Hard Bounce entscheiden
- Zustellstatus in Ihren E-Mail-Statistiken ablesen
Transkript
Automatisch aus dem Video generiert.
Vollständiges Transkript
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.
Verwandte Videos
In die Praxis umsetzen.
Weiter mit der Dokumentation, Anleitungen und Beispielen zu diesem Thema. Die Ressourcen sind auf Englisch.