EonMailer Help
Home Open app

Deliverability

Handle spam complaints

Feedback loops, list hygiene, and client communication.

A complaint is when a recipient clicks “Report spam.” Providers expect complaint rates well under 0.1% — sustained higher rates pause sending.

Automatic handling

When webhooks include spam report events, EonMailer suppresses complainers like hard bounces. Verify webhook config per provider.

Root causes

  • List without clear opt-in
  • Stale list (no send in 12+ months)
  • Misleading subject/from
  • Missing unsubscribe
  • Frequency too high

Agency response playbook

  1. Pause scheduled campaigns for affected segment.
  2. Pull complaint recipients — confirm suppressed.
  3. Review signup source and consent language with client.
  4. Send re-permission campaign only to engaged subset if appropriate (legal review first).
  5. Document incident in client QBR.

Client communication

Explain complaints hurt domain reputation for all mail including transactional — not just marketing. Use white-label report metrics if client doesn’t access EonMailer directly.

Feedback loops

Major ISPs send FBL data to ESPs; API webhooks surface the same. You rarely need separate FBL signup when using SES/SendGrid/Mailgun correctly.

Prevention