← Back to docs

Bounce & Feedback Loops

Automatic bounce handling and complaint processing

Menu

VERP Bounce Tracking

EuroMail uses VERP (Variable Envelope Return Path) to achieve precise per-recipient bounce tracking. Each outbound email is assigned a unique return-path address that encodes the recipient and message identifier. When a bounce notification is returned by the recipient's mail server, EuroMail can immediately identify exactly which recipient and which message bounced, without relying on unreliable bounce message parsing.

Hard Bounce vs Soft Bounce Classification

Bounces are classified into two categories based on the SMTP response code:

TypeSMTP CodesMeaningAction
Hard bounce5xx (e.g., 550, 551, 553)Permanent failure. Address does not exist, domain invalid, or mailbox disabledRecipient added to suppression list
Soft bounce4xx (e.g., 450, 452)Temporary failure. Mailbox full, server unavailable, rate limitedRetried with exponential backoff

Hard bounces indicate a permanent delivery problem. Continuing to send to hard-bounced addresses damages sender reputation, so EuroMail suppresses the address after the first occurrence when the receiving server identified the mailbox as the problem with a standard status code such as 5.1.1. Some servers only say so in words (550 No Such User Here, with no status code). Those bounces are still reported and still reach your webhook, but the address stays sendable: the same wording is used for refusals that are not about the recipient at all, and a wrong suppression silently cuts off a real person.

Temporary SMTP failures are retried with backoff. Exhausting those attempts records a failed delivery; it does not by itself prove the address is invalid. Soft DSNs received after SMTP acceptance follow the cumulative suppression rule described below.

Bounce processing and retries

For a delivery-status notification (DSN), EuroMail commits the recipient's bounced status, bounce event and any required suppression in one database transaction. Soft-bounce tracking commits in that transaction too; the third recorded soft DSN for an address creates a repeated-soft-bounce suppression. A database error rolls back the work so the same notification can be retried. A duplicate notification after a successful commit does not add another event or increment the soft-bounce count.

CC and BCC notifications update their own delivery row and suppress the copy's address, leaving the primary recipient's status alone.

Webhook publication currently follows the database commit. A publication failure or a crash in that interval can still lose a notification; a durable webhook outbox remains required. Poll message events when reconciling your application's state.

Automatic Suppression List Management

When a spam complaint is received, or a hard bounce that the receiving server attributed to the mailbox with a status code, the recipient address is automatically added to your account's suppression list. Subsequent API calls that include a suppressed address will return a 422 response explaining that the address is suppressed, preventing further damage to your sender reputation.

The suppression list distinguishes between bounce-suppressed and complaint-suppressed addresses, so you can take appropriate action in your application (e.g., marking an address as invalid vs. honoring an unsubscribe preference).

ARF Complaint Parsing

EuroMail participates in ISP feedback loops and parses incoming complaints in ARF (Abuse Reporting Format). When a recipient marks one of your emails as spam in their mail client, the ISP sends an ARF report to EuroMail. We parse the report, identify the original message and recipient, and trigger a complained webhook event.

Complaint rates are a critical sender reputation metric. Major ISPs like Gmail, Yahoo, and Outlook expect complaint rates below 0.1%. The dashboard displays your complaint rate alongside delivery and bounce rates.

Suppression List API

You can manage your suppression list programmatically:

# List suppressed addresses
curl https://api.euromail.dev/v1/suppressions \
  -H "Authorization: Bearer em_live_..."

# Add an address manually
curl -X POST https://api.euromail.dev/v1/suppressions \
  -H "Authorization: Bearer em_live_..." \
  -H "Content-Type: application/json" \
  -d '{"email_address": "[email protected]", "reason": "manual"}'

# Remove an address (use with caution)
curl -X DELETE https://api.euromail.dev/v1/suppressions/[email protected] \
  -H "Authorization: Bearer em_live_..."

Dead Letter Queue

Emails that fail all delivery attempts are moved to a dead letter queue. You can inspect failed deliveries in the dashboard, review the failure reason and SMTP response, and optionally retry delivery. Entries remain available until you retry or delete them; the queue is size-capped, so the oldest entries are pruned as new failures arrive.

Send your first email in about 90 seconds

The free tier includes 3,000 emails a month. Email storage and AI processing in Finland, with a DPA on every plan.

Create free account See live delivery data