Send transactional and newsletter email from your own domain.
Couldn't load mail
Is mail working?
Yes. lumen-app sends from hello@lumen.studio, noreply@lumen.studio, billing@lumen.studio, news@lumen.studio and a test reached an inbox.
Sandbox: this server keeps every message inside FlowPrime, so nothing reaches a real inbox.
-
✓A provider is connectedPostmark - transactional sends for lumen-app.
-
✓Sender addresses are sethello@lumen.studio, noreply@lumen.studio and billing@lumen.studio can send.
-
✓lumen.studio is verifiedDKIM, SPF and DMARC records were found and match.
-
✓Send a testDelivered to ana@lumen.studio.
Connect a provider
A provider is the service that actually delivers your mail. Resend is the simplest: create an account at resend.com, add your domain there, then create an API key and paste it here. FlowPrime checks the key with the provider before saving it.
Other providers (SMTP, Amazon SES, Mailgun) are on the Providers screen.
Inbox 6
Mail sent to ana@lumen.studio and its + variants, kept inside FlowPrime instead of sent (last 7 days). Only you see it.
Select an e-mail to read it.
Last 7 days, all servers
3 of 3 servers
Sent (7d)
7,523
Delivered
7,393
98.3% delivered
Bounced
34
Failed
6
Sent per day
7 Nov - 13 Nov
Sending reputation
7,508 attempted - last 7 days
Bounce rate 0.45%
under 5% recommended
Complaint rate 0.03%
under 0.1% recommended
15 send(s) blocked by the do-not-send list in this window.
Sending normally on every server
Bulk mail pauses by itself if bounces or complaints pass your limits, and this page and the Overview say so.
Bulk mail per serverLast 30 days or since the last Resume. Pauses only after 200 bulk messages. Marker = your limit.
| Server | State | Sent | Hard bounces | Complaints | |
|---|---|---|---|---|---|
| lumen-app | Sending | 6,120 | 0.3% |
0.00% |
|
| lumen-newsletter | Sending | 11,240 | 0.6% |
0.03% |
|
| lumen-staging | Sending | 402 | 0.2% |
0.00% |
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 |
|---|---|---|---|---|---|
| Gmail | 7,410 | 99.4% | 0.4% | 0.03% | 52% |
| Apple iCloud | 3,122 | 99.6% | 0.3% | 0.00% | 97% |
| Outlook / Hotmail | 2,874 | 98.5% | 0.9% | 0.03% | 41% |
| Company domains | 2,290 | 98.3% | 1.0% | 0.00% | 39% |
| Yahoo | 911 | 98.7% | 0.8% | 0.00% | 31% |
| Proton | 405 | 99.5% | 0.2% | 0.00% | 0% |
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
1-25 of 60252
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 | |
|---|---|---|---|---|---|
| jordan.wells@gmial.com | Bounce | postmark - 550 5.1.1 Recipient address rejected: domain does not exist | 2 | 11/10/2026 | |
| info@oldstudio-photo.com | Bounce | ses - 550 5.1.1 Mailbox unavailable | 1 | 11/1/2026 | |
| m.fontaine@orange.fr | Complaint | ses - Marked as spam in Orange Mail | 0 | 10/23/2026 | |
| bookings@sunsetvows.co.uk | Bounce | postmark - 552 5.2.2 Mailbox full | 4 | 10/19/2026 | |
| noreply-test@peakandpine.co | Manual | operator - Added by operator: test address from Peak & Pine onboarding | 0 | 10/11/2026 | |
| kevin.hart.photo@yahoo.com | Complaint | brevo - Spam report from Yahoo feedback loop | 0 | 10/3/2026 | |
| studio@lumiere-old.fr | Bounce | ses - 550 5.4.1 Recipient address rejected: Access denied | 6 | 9/27/2026 | |
| a.nowak@wp.pl | Bounce | postmark - 550 5.1.1 User unknown | 1 | 9/16/2026 | |
| hello@closedphotoco.com | Bounce | ses - Domain has no MX record | 2 | 9/11/2026 | |
| ella.m@icloud.com | unsubscribed | newsletter - Left the newsletter from the edition footer | 0 | 11/4/2026 |
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) | |
|---|---|---|---|---|---|---|
| 1 |
Postmark - transactional
postmark · sends as hello@lumen.studio, noreply@lumen.studio, billing@lumen.studio
|
1 | 100 | - / 50,000 | 107 today · 3,060 mo | |
| 2 |
Amazon SES - bulk
ses · eu-west-1 · email-smtp.eu-west-1.amazonaws.com · sends as news@lumen.studio, ana@lumen.studio
|
2 | 0 | - / - | 16 today · 2,094 mo |
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.
Priority order · Try the next provider · hard caps
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 | |
|---|---|---|---|---|---|
|
Postmark - transactional
sends as hello@lumen.studio, noreply@lumen.studio, billing@lumen.studio
|
postmark | - / 50,000 | 214 today · 6,120 mo | lumen-app | |
|
Amazon SES - bulk
eu-west-1 · email-smtp.eu-west-1.amazonaws.com · AKIA4LUMENSES7Q2
sends as news@lumen.studio, ana@lumen.studio
|
ses | - / - | 31 today · 4,188 mo | lumen-newsletter, lumen-app | |
|
Brevo - free tier backup
sends as hello@lumen.studio, news@lumen.studio
Webhook for Brevo (Transactional > Settings > Webhook; events delivered, hard bounce, soft bounce, blocked, spam, invalid email, error):
|
brevo | 300 / 9,000 | 12 today · 402 mo | lumen-newsletter, lumen-staging |
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
lumen.studio
Mode: live
DKIM
SPF
DMARC
DNS records to publish
checked 9:30:00 AM
Domain: lumen.studio
DKIM ffmail._domainkey.lumen.studio (TXT)
verified
Signing with the ffmail selector.
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAx3Lm...QIDAQAB
SPF lumen.studio (TXT, v=spf1...)
verified
Covers Postmark, Amazon SES and Brevo.
v=spf1 include:spf.mtasv.net include:amazonses.com include:spf.brevo.com ~all
DMARC _dmarc.lumen.studio (TXT)
verified
Policy: quarantine.
v=DMARC1; p=quarantine; rua=mailto:dmarc@lumen.studio; pct=100
Return path where bounces come back
verified
Bounces come back to Postmark.
pm-bounces.lumen.studio CNAME pm.mtasv.net
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 | |
|---|---|---|---|---|
| Postmark first, SES on failure active | Priority order | Try the next provider | Hard |
New policy
Always the lowest Order number first. Caps still skip an exhausted provider.
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
8 total 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