What happens during SMTP connection filtering?

Your email hasn't even said "hello" yet, and the receiving server is already forming an opinion. Before a single byte of message content crosses the wire, the server runs a set of fast, cheap checks on whoever is knocking at the door. That's SMTP connection filtering.

Here's what actually happens during those first moments of the connection.

IP reputation check. The receiving server looks up the sending IP against blocklists like Spamhaus and Barracuda. If your IP appears on one of those lists, the connection is rejected before any message data is transmitted. No content, no subject line, no headers. Just a rejection and goodbye.

Reverse DNS lookup. The server checks whether your sending IP resolves to a valid hostname (called a PTR record), and whether that hostname points back to the same IP. If there's no PTR record, or if it points somewhere unexpected, many servers will reject or heavily penalize the connection. A mismatch here is a strong spam signal because legitimate mail servers almost always have proper reverse DNS configured.

SPF check. The server checks whether your IP is authorized to send on behalf of your domain. If your SPF record doesn't list the sending IP, that's a flag. Depending on your SPF policy, it may result in a rejection or a note for later filtering stages.

Rate and connection limits. If the sending server is hammering the receiver with too many simultaneous connections or sending too fast, the receiver may issue a temporary 4xx deferral ("try again later") or a permanent 5xx rejection ("don't bother"). This is how receiving servers protect themselves from volume-based attacks.

Does one bad check kill the message? It depends on the receiving server's policy. A blocklist hit almost always means immediate rejection. A reverse DNS mismatch might mean rejection, or it might just add weight to a negative score that accumulates across all the checks. Some servers are strict. Others layer everything together and make a combined judgment. Either way, none of these problems are ones you want to have.

The reason connection filtering exists is efficiency. Rejecting a bad connection before accepting content saves the receiver from processing gigabytes of spam. It also means the rejection happens at the protocol level, which is clean and unambiguous for the sender to diagnose.

Still if you're seeing unexpected rejections early in the SMTP conversation, start by checking whether your sending IP is on any blocklists. Our free blocklist checker can tell you in seconds. If you're stuck on what a rejection code actually means, our SOS hotline is free and we actually pick up.