Send transactional and newsletter email from your own domain.
Loading your mail...
Couldn't load mail
Last 7 days, all servers
-
Sent (7d)
-
Delivered
-
Bounced
-
Failed
-
Last 7 days
Sending reputation
Bounce rate -
under 5% recommended
Complaint rate -
under 0.1% recommended
Bulk mail per serverMarker = your pause limit.
| Server | State | Sent | Hard bounces | Complaints | |
|---|---|---|---|---|---|
| Loading… | |||||
Pause limits
Bulk mail stops above either limit, on every server. Keep them under your provider's own: Amazon SES pauses the whole account at 5% bounces or 0.5% complaints.
Hard bounces, %
Complaints, %
Warm-up for newsletter editions
An edition to 100 readers or more goes out in steps, and the pause limits are checked before each one.
Wait between steps minutes
Where your mail lands, last 30 daysOpens count bulk mail only; scanner hits removed
| Inbox provider | Sent | Delivered | Bounced | Complaints | Opens |
|---|---|---|---|---|---|
| Loading… | |||||
Company domains are split by who hosts their mail. Apple Mail Privacy loads every pixel, so opens read high for iCloud readers; clicks are the firmer number.
Who got your emails
-
One list for mail and newsletter
Readers who unsubscribe from your newsletter land here as "Left the newsletter": they get no more bulk mail, and still get password resets and receipts. An address that bounces or is marked as spam here is marked in your newsletter list too. Applies when your newsletter sends from your own address.
Do-not-send list
Addresses mail will not send to, across every server in this org. Readers who left the newsletter are blocked from bulk mail only.
| Address | Reason | Source | Blocked | Added | |
|---|---|---|---|---|---|
| Loading... | |||||
Server settings
How this server connects to a provider and which domain it sends from.
Sandbox: every message is quarantined and never reaches a real inbox. The providers below are saved but not used until Delivery mode is Live.
Used for DKIM/SPF/DMARC checks. Leave blank to derive from the From address later.
Save the server first - providers, policies and domain checks attach to it once it exists.
Attached providers
This server sends through these registered providers, listed in the order the active
policy would pick them. Credentials live on the
Providers screen - here you
only choose which ones this server uses, and how.
| # | Provider | Order | Weight | Caps (day / month) | Used (org-wide) | |
|---|---|---|---|---|---|---|
| No providers attached. Pick one below. | ||||||
Attach a provider
Order and weight are this server's own; caps belong to the provider and count across every server using it.
Distribution
Which policy decides between the providers above. Build them on the Distributions screen.
Sending providers
Register each provider account once - credentials and its allowance live here. Then attach
it to servers on Server settings;
caps count usage across every server it is attached to.
Account emails are always delivered.
Password resets, invites, welcome and verification emails to your organization admin are
carried by FlowPrime's own infrastructure (sent from FlowPrime's address) whenever your
providers can't deliver them - even before any provider is configured. Everything else
sends through the providers below, from the sender addresses you configure.
| Provider | Type | Caps (day / month) | Used | Attached to | |
|---|---|---|---|---|---|
| Loading... | |||||
Add a provider
The exact From addresses this account is verified to send. Mail from any other address is refused.
Caps are this account's allowance at the provider - usually its free tier. 0 means no
limit. They apply in every strategy, counted across all attached servers.
What "verified" checks
DKIM: your provider's key is published, so receivers can prove the mail is yours.
SPF: one record that includes every provider on this server and ends in -all or ~all.
DMARC: a policy is published.
Return path: bounces come back to your provider, checked where the provider fixes the record name (Postmark, Resend, an Amazon SES custom MAIL FROM).
Your sending domain
Domain
-
-
DKIM
SPF
DMARC
DNS records to publish
No domain configured yet. Set a sending domain on Server settings, then Recheck.
Distribution policies
A policy decides which provider sends and what happens when one refuses. Build it here, then select it on Server settings.
| Name | Strategy | On failure | Caps | |
|---|---|---|---|---|
| Loading... | ||||
New policy
How distribution works
Each box is one provider, in the order you set. The tinted box is the one a message goes to.
Priority order
Always the lowest Order number that is available. The rest are only there as backup. Use it when one provider is simply better and the others exist to catch an outage.
Round-robin
Each send goes to whichever provider was used least recently, so volume spreads evenly. Good for sharing load and for building reputation on more than one provider at once.
Weighted split
Each send is drawn at random in proportion to Weight. Use it to move traffic gradually - send 10% through a new provider, watch the bounce rate, then raise it.
Free quota first
Providers with a cap still under it - free tiers being filled - go before uncapped (metered) ones, whatever their Order; Order breaks ties. Use it to burn free allowances (SES, SMTP2GO, Resend) before anything paid.
Caps
A daily or monthly ceiling on one provider - usually its free allowance. 0 means no limit. Caps belong to the registered provider and count across every server attached to it: the allowance is the account's at the provider, not any one server's. They apply in every strategy, not just Free quota first: a provider that has reached its cap drops to the bottom, so round-robin and weighted quietly stop choosing it. Counting is per calendar day and per calendar month, and only counts mail actually handed to that provider - blocked and suppressed messages do not use up your allowance.
Soft (default): once every provider is over its cap, sending continues on the least-bad one. You may pay for overage, but mail keeps moving.
Hard: once every provider is over, sending stops and messages fail. Choose this only when an unexpected bill is worse than undelivered mail.
Hard: once every provider is over, sending stops and messages fail. Choose this only when an unexpected bill is worse than undelivered mail.
When a provider refuses
Try the next provider - the message is handed straight to the next one in line, usually within the same second. This is the main reason to run more than one provider.
Leave it to the retry worker - the message is queued and retried later, which may pick a different provider by then. Slower, but it does not hammer a struggling provider.
No failover - only the chosen provider is tried, and if it refuses the message fails permanently rather than being retried through someone else. Use it when a message must come from one specific sender or not at all.
Leave it to the retry worker - the message is queued and retried later, which may pick a different provider by then. Slower, but it does not hammer a struggling provider.
No failover - only the chosen provider is tried, and if it refuses the message fails permanently rather than being retried through someone else. Use it when a message must come from one specific sender or not at all.
Templates
API keys
for your dev team Copy this key now
This is the only time you'll see it. Store it somewhere safe.
New template
Preview
Message detail
Compose email
Send test email