Follow one email from WordPress to the inbox

WordPress sends an email (wp_mail())

A contact form, a password reset, an order receipt: WordPress hands the message to wp_mail(), and BooleanSMTP takes it from there.

Simulation check (Simulation check)

Simulation mode is off, so the message goes out for real.

The connection is chosen (Choose the connection)

BooleanSMTP uses the connection that owns the From address, or your default connection when none does.

It is sent (Send: API or SMTP)

Out it goes, over the provider’s API or over SMTP, whichever the connection uses.

The provider accepts it (Mail provider)

Your mail provider takes the message and handles delivery from here.

It is logged as Delivered (Email Logs)

Email Logs records the recipient, subject, mailer and time.

It reaches the recipient (Recipient)

Inbox or spam then depends mostly on your domain’s SPF, DKIM and DMARC records.

WordPress sends an email (wp_mail())

A contact form, a password reset, an order receipt: WordPress hands the message to wp_mail(), and BooleanSMTP takes it from there.

Simulation check (Simulation check)

Simulation mode is off, so the message goes out for real.

The connection is chosen (Choose the connection)

BooleanSMTP uses the connection that owns the From address, or your default connection when none does.

It is sent (Send: API or SMTP)

Out it goes, over the provider’s API or over SMTP, whichever the connection uses.

The provider refuses it (Mail provider)

Your primary provider turns the message away: an expired key, a suspended account, an outage.

The fallback takes over (Fallback connection)

BooleanSMTP immediately tries the message once more on your fallback connection, and this time it goes through.

It is logged as Delivered (Email Logs)

The log shows it went out on the fallback, on the second attempt, so you know the primary needs a look.

It reaches the recipient (Recipient)

Your customer never knew anything went wrong.

WordPress sends an email (wp_mail())

A contact form, a password reset, an order receipt: WordPress hands the message to wp_mail(), and BooleanSMTP takes it from there.

Simulation check (Simulation check)

Simulation mode is off, so the message goes out for real.

The connection is chosen (Choose the connection)

BooleanSMTP uses the connection that owns the From address, or your default connection when none does.

It is sent (Send: API or SMTP)

Out it goes, over the provider’s API or over SMTP, whichever the connection uses.

The provider refuses it (Mail provider)

Your primary provider turns the message away: an expired key, a suspended account, an outage.

The fallback fails too (Fallback connection)

The immediate retry on your fallback connection is refused as well.

It waits and retries (Retry queue)

With Retry on other connections on, as it is by default, the message is retried on your other active connections: after about 1 minute, then about 5 minutes.

It is logged as Failed (Email Logs)

When nothing is left to try, Email Logs marks it Failed, with the provider’s error, ready to resend.

You are alerted (Alert)

Slack, Discord or Telegram tells you, with a link to the log entry, so you hear about it before your customers do.

WordPress sends an email (wp_mail())

A contact form, a password reset, an order receipt: WordPress hands the message to wp_mail(), and BooleanSMTP takes it from there.

Simulation mode is on (Simulation check)

Handy on a staging copy: BooleanSMTP stops the message here, before any connection is chosen.

It is logged as Simulated (Email Logs)

Email Logs records it as Simulated, so you see exactly what would have gone out.

Nothing is sent (Captured, not sent)

No provider ever sees it. Turn simulation off when the site goes live.