What is pre-delivery vs post-delivery filtering?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
You hit send. Your email gets accepted. Inbox placement confirmed. Job done, right? Not always. Email filtering doesn't stop the moment a message lands in the inbox, and understanding where it happens changes how you think about your sender reputation.
Pre-delivery filtering is everything that happens before a message reaches the inbox. The receiving mail server evaluates your IP reputation, checks your SMTP connection, scans content for spam signals, and runs authentication checks. If something looks wrong at this stage, the message gets rejected or quarantined before the recipient ever sees it.
Post-delivery filtering happens after the message has already been accepted. This kicks in when a recipient reports spam, when a background scan detects a newly identified threat, or when fresh threat intelligence flags a link or payload that looked clean on arrival. At that point, the mailbox provider can move the message to spam, slap a warning banner on it, disable links inside it, or pull it from the inbox entirely.
Gmail and Microsoft 365 both do post-delivery remediation. It's not a rare edge case. It's a standard part of how modern mailbox providers protect their users.
For senders, the practical takeaway is this: inbox placement isn't permanent. A message that lands in the inbox today can be reclassified as spam tomorrow if enough recipients report it or if a threat scan catches up with it. That's why complaint rates matter even after delivery, and why sending to disengaged lists is risky long after the campaign ends.
You can influence pre-delivery filtering directly through authentication, reputation management, and content quality. Post-delivery is harder to control, but keeping complaint rates low is your best lever there.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.