Backup Mailer Failover: what it does

Every email provider has bad days. When your primary mailer rejects, throttles, or goes down, NimblyMail Pro automatically re-sends the message through your backup provider — after the retry budget is spent, without you lifting a finger. Amazon SES having a rough hour? Gmail or SMTP takes over, and the log shows exactly what happened.

Backup Mailer FailoverActive · configured via setup wizard

Enabled

Deliverability auditVerifies configuration weekly

Passing

Why it matters

What you get with Backup Mailer Failover

Automatic failover

Exhausted retries are re-queued through the backup mailer — no manual resends, no lost receipts.

Independent failure domains

Pair providers from different vendors so one outage never touches the other.

Full audit trail

Every failover is logged: original mailer, failure reason, backup mailer, final status.

Alerts stay on

Failover events trigger failure alerts, so you know your primary degraded even though customers never noticed.

How it works

Three steps, zero babysitting

Set a backup mailer

Connect any second provider — a different vendor from your primary for true independence.

Primary fails, retries exhaust

The queue retries with backoff. If the message still can't send, the backup mailer takes over.

Delivery continues

The email ships through the backup, marked in the log with both attempts. You get one alert, customers get their email.

FAQ

Backup Mailer Failover questions, answered

How is this different from a queue retry?

Retries send through the same provider again. Failover switches providers entirely — so if your primary's account is suspended or its API is down, messages still go out through the backup.

Which backup provider should I choose?

Is failover included in the free version?