Site email — Docs

A WordPress server usually sends mail as itself, from an address on a domain with no authentication behind it, which is why password resets end up in spam. Switching this on sends them from your verified sending domain over HTTPS instead. There is no SMTP host, port or password to get wrong.

What it covers

Everything that goes through wp_mail(), which is nearly everything: password resets, new user notifications, comment moderation, WooCommerce order confirmations, booking and membership plugins, contact form notifications. None of them need a setting of their own.

Turning it on

Verify a sending domain in SendBeam if you have not.
Give the site's API key the Send site email permission (transactional:send).
Settings → SendBeam → Site email, tick Send this site's email through SendBeam, and save.

Who it appears to come from

Leave From name and From address empty and each message keeps whatever the sending plugin set, falling back to the workspace sender. Set them to override both. The address must be on a domain verified in the workspace — that is the whole point of the exercise.

If SendBeam cannot send

Fall back to the server's own mailer is on, and should stay on. A refused or failed message then goes out the way it did before the plugin, so a password reset still arrives. Turn it off only if you would rather a message failed loudly than left unauthenticated.

What is not sent

Messages with attachments are left to the server's mailer.
Addresses that previously bounced or complained are refused, as everywhere else in SendBeam.

Recipients do not need to be contacts, and someone who unsubscribed from your newsletter still gets their receipt — this is transactional mail, kept separate from marketing.

Checking it works

Send a test email on the same tab sends one to your own address using the saved settings and reports exactly what happened. Below it, Recent site email lists the last twenty messages and whether each went through SendBeam, fell back to the server, or failed.