What’s the difference between internal vs external bounce parsing?

Bounce parsing is how you classify delivery failures: did an email permanently fail (hard bounce) or temporarily fail (soft bounce)? The question is who does that classification work.

External bounce parsing means your ESP or sending provider handles it. Most platforms automatically classify bounces and suppress addresses based on their own rules. This is what the vast majority of senders use, and it's fine. The tradeoff: you're trusting their classification logic, which may not perfectly match your suppression policy, and you have limited visibility into the raw SMTP codes behind each decision.

Internal bounce parsing means you build and maintain the classification logic yourself. You intercept bounce messages, parse the MIME structure, read the SMTP status codes and diagnostic text, and apply your own rules to decide what goes on your suppression list. Full control, custom rules, complete data visibility. The cost: you need to understand bounce codes well enough to classify reliably, and ISP response patterns change, so your rules need ongoing maintenance.

When internal parsing is worth it: if you're sending through multiple infrastructure providers and need consistent classification across all sources. Or if you have regulatory requirements around how quickly certain bounce types must be suppressed. Or if your ESP's classification is producing anomalous suppression rates you can't explain.

For most senders, external parsing via ESP is the right default. Before changing that, check what hard bounce data your ESP actually exposes. Most provide webhook events or API access to raw bounce information, which gives you visibility without having to own the full parsing stack.