You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every team gets a hosted address that works without DNS changes, with +tags to tell senders apart
Receive on a subdomain of your own domain (for example reply.acme.com) by adding one MX record
New Inbox page with the message, attachments, headers and SPF, DKIM, DMARC, spam and virus results
New email.received webhook event, with signed attachment links that last an hour
GET /v1/inbound/emails and GET /v1/inbound/emails/{id} in the API
Replies to email you sent are linked to the original through inReplyToEmailId
Forwarding rules for an address, a local part or everything
Monthly allowances on every plan (from 1,000 on Free to 250,000 on Scale); mail is kept for 30 days
The local SES emulator can deliver test mail to ByteSend
DMARC reports:
Every team gets a report address; add it to your domain's DMARC record and providers' daily reports are read automatically
New DMARC page: pass rate over time, every server sending as your domains (ByteSend's own traffic marked), and each report in full
The setup tab shows your current DMARC record and the exact record to publish, keeping your existing policy
Reports don't count toward your receiving allowance and are kept for 90 days
Test mode:
Create test API keys (bs_test_...) that never send: emails appear in the dashboard marked Test
Deliveries, bounces and complaints are simulated with real webhooks (flagged "test": true), chosen by the recipient address
Works before your domain is verified, and doesn't touch usage, bounce rates or suppressions
Email page: every email has its own page at /emails/<id> with a larger preview (desktop and mobile widths), all recipients, the domain, campaign and API key it came from, its events, and any replies received in your inbox
Set up DNS on Cloudflare: paste a Cloudflare API token on a domain's page and ByteSend adds the records for you. Existing MX, SPF and DMARC records are never overwritten, and the token isn't stored
Website: the pricing, features and comparison sections now cover receiving, DMARC reports and test mode, and the homepage has a new backdrop drawn from the ByteSend mark
Fixed
Batch sends now respect an API key's domain restriction
Pages no longer run off the right edge on phones: cards and sections fit the screen, and long IDs and file names wrap or are shortened
Moving a domain that receives email to another sending region keeps receiving working: the identity it receives through is kept, and removed when receiving is turned off or the domain is deleted
Deleting a domain works again when its Amazon SES identity is already gone, shows an error if it fails, and accepts the name typed in any case (phone keyboards capitalise it)
Verify again on a verified domain now re-checks its DNS straight away, updates the problem banner, and says what it found. Record rows show a problem the DNS monitor found instead of an old "Verified"
Moving a domain to another region now waits until its MX record points at the new region. Before, a move could finish with the MX still on the old region, which sent bounces and complaints to the wrong place
Installing the repo with pnpm 9 no longer fails on Prisma Studio's pnpm 8 requirement, so the web tests run in CI again