Release Notes

New features and improvements added to BYOMailer.

October 7, 2026

The BYOMailer MCP server can now set the filters of a sequence. The create-sequence tool accepts a filters array, so only matching contacts receive the sequence. The new update-sequence tool renames a draft sequence or replaces its filters. An empty filters array clears them. Live sequences cannot be edited through the MCP server.

September 28, 2026

You can now export the emails of a newsletter as a CSV file. Open a sent newsletter and click Export CSV in the Recipients section. The file has one row for each recipient, with the email, the name, the delivery status and times, the subject, and the plain-text body that the contact got. The export uses the status filter that you selected.
Editing an email template now flows through to your not-yet-sent newsletters and sequence steps: the template is composed fresh at send time, so drafts, scheduled newsletters, and live sequence steps always go out with the latest template. Already-sent newsletters keep their original look as a historical record.

September 25, 2026

Links that add a query string after a variable now work for every contact. For example, {{ checkout_url }}?coupon=SAVE10 now joins the coupon with & when the contact's checkout_url already has a ?, so the coupon is not lost. Links in the plain-text version of an email no longer show escaped characters like =.

September 24, 2026

The BYOMailer MCP server can now send a test copy of a sequence step. The new tool send-sequence-step-test-mail delivers one step to your own inbox so you can read it before the sequence goes live. It does not send to the sequence audience and does not start or advance the sequence for anyone.

September 23, 2026

Sequence steps can now have their own filters. A contact who does not match the filters of a step skips only that email and continues to the next step. The sequence filters still remove a contact from the whole sequence. The step metrics show how many emails were skipped.
You can now set the filters of a sequence step through the API and the MCP server. The API has a new endpoint, PATCH /api/v1/sequences/{sequenceId}/steps/{sequenceStepId}/filters. The MCP tools create-sequence-step and update-sequence-step accept a filters array.
Automations can now start when a contact attribute changes, for example when plan changes to pro.
The BYOMailer MCP server can now manage automations. An AI assistant connected to your account can list automations, read one with the names of its lists, tags and sequences, create a new automation, and edit a paused one. New automations are always paused. Only the dashboard can turn an automation on or delete it.
The contacts API now returns the sequences of each contact. Before, the sequences field was always empty. The MCP contact tools, for example find-contact, now also return the sequences of the contact.

September 22, 2026

The BYOMailer MCP server can now add contacts. An AI assistant connected to your account can look up a contact by email, create or reuse one, put them on a list, label them with tags, and remove them from a list. Adding someone to a list that requires opt-in still sends the opt-in email. Tag removal is not available through the MCP server.
Sender identities now have an optional Reply-To address and name. Set them on the identity page, and replies to your newsletters, sequences and opt-in emails go to that inbox instead of the From address. Leave the email empty to remove the Reply-To.
A newsletter or sequence step cannot go out with an empty subject or an empty body. Mailbox providers treat such mail as spam. Scheduling or sending now shows what to fix, and test emails still send.
BYOMailer now stops sending when Amazon SES pauses your account, and reads your SES account status every hour.
A new Reputation page shows your SES account status and your bounce and complaint rates for the last 24 hours, 7 days and 30 days. A banner appears on every page when SES reviews or pauses your account.
Sequence emails now respect the sending rate of your Amazon SES account. Each run queues up to 200 due emails and sends them at your SES rate, so a large sequence no longer fails emails with throttling errors.
Sequence emails are no longer sent twice. A step is now marked sent as soon as your mail provider accepts it, so a slow delivery report no longer lets the next run send the same email again.
You can now sunset inactive contacts in Settings > Profile. Pick a period, and a daily run stops mailing contacts who have not clicked in that period. The page shows how many contacts the next run will stop mailing. A sunset contact shows a Sunset badge and a Reactivate button.
Bounce handling is more accurate. An SES reject no longer unsubscribes the contact, because SES refused the message for its content and the address is not at fault. Only a permanent bounce suppresses a contact at once. Temporary and undetermined bounces now count up, and three in a row suppress the contact. A successful delivery resets the count.

September 19, 2026

One-click unsubscribe now works the way Gmail, Yahoo and Apple Mail expect. The List-Unsubscribe header points at a dedicated endpoint that accepts their POST, so unsubscribe requests from the inbox toolbar succeed instead of failing silently and counting against your sender reputation.
The unsubscribe link in an email now opens a confirmation page instead of unsubscribing straight away. Corporate link scanners follow every URL in a message, and they were unsubscribing contacts who had never clicked.
Blocks are now expanded in bulk newsletters. A {{ block.footer }} placeholder used to render as nothing in newsletters sent through the SES bulk API, which silently dropped footers, postal addresses and unsubscribe links.
Suppressed addresses are excluded at send time. A contact whose address hard bounced or complained is now skipped by newsletters and sequences, not just blocked at contact creation.
DMARC is now verified in DNS. The identity page marks the _dmarc record verified once you publish it, and the check re-runs daily so a removed policy is noticed.
Plain-text versions of emails now keep link URLs and paragraph breaks everywhere. Sequence steps used to strip them out, leaving a bare wall of text for clients that show the plain part.
A contact who already unsubscribed and opens an unsubscribe link again now gets a Subscribe again button instead of a dead end. Resubscribing also asks for confirmation first, so a link scanner can no longer put someone back on the list.
The BYOMailer MCP server can now manage sender identities. An AI assistant connected to your account can list your sending domains, read the DNS records a domain needs, create a new identity in your own AWS SES, re-check verification with AWS after DNS changes, and toggle open and click tracking. Identities cannot be deleted through the MCP server.

July 23, 2026

New Attributes page under Audience: every contact attribute now supports a global default value. When an email uses a variable, BYOMailer resolves the contact's own value first, then the newsletter or sequence default, then the global default.
Newsletter and sequence variable steps now prefill empty defaults with the matching global attribute default, with a hint showing where the value came from.
Introducing Projects: create named projects and group your newsletters, sequences, automations, and visual automations under shared initiatives. Manage projects from the new Projects page in the sidebar, complete with per-resource counts that link straight to each filtered list.
Every index now filters by project: newsletters, sequences, automations, and visual automations all gained a project dropdown, project chips on each row, and a quick-assign menu so you can tag resources without leaving the page. Sequence and automation filters operate within the rows you can already see.
The Projects API is live: full CRUD at /api/v1/projects, a project filter on the newsletter and sequence list endpoints, and project_ids on newsletter create/update. The OpenAPI spec, Postman collection, and API reference docs all cover the new endpoints.

July 15, 2026

The BYOMailer MCP server can now update an existing draft sequence step, not just create new ones. An AI assistant connected to your account can revise a step's delay, subject, body, sender or template. Only draft steps can be edited — live steps are locked — and edits never change the status, so going live still happens in the dashboard.

July 3, 2026

New positioning across the marketing site: BYOMailer now leads with moving your email marketing to your own AWS SES account, flat pricing with no contact limits, and hands-on migration help included on every plan.
Pricing now has five tiers: Solo ($29), Founder ($49), Growth ($99, most popular), Portfolio ($199), and Enterprise (custom). Migration help is included on every plan, not gated to higher tiers. Existing plan checkout and billing are unchanged.
The Legendsverse case study now tells the full story: the problem, why subscriber-based pricing did not fit, what BYOMailer handles now, the migration, the result, and the commercial takeaway.
Alternative comparison pages gained who-should-switch, who-should-not-switch, migration, and FAQ sections (with FAQ rich-result schema). Six new comparison pages were added: AWS SES email marketing, EmailOctopus, MailBluster, BigMailer, Brevo, and MailerLite, plus an /alternatives comparison hub.
New Guides section at /guides with two in-depth articles: how to set up AWS SES for email marketing (domain verification, DKIM, getting out of the sandbox) and the best email marketing platform for SaaS founders (a cost comparison across the major ESPs at 1k–100k contacts). Both are written answer-first with Article schema for search and AI-answer visibility.

July 2, 2026

Newsletter click rate is now shown everywhere open rate is: a Click column on the Newsletters list and the dashboard's latest-newsletters table, plus a Click rate card on the newsletter detail page — so you can see click-through at a glance.

June 29, 2026

The BYOMailer MCP server can now create sequences and add steps to them. An AI assistant connected to your account can draft a whole drip campaign for you to review. Sequences and steps are always created as drafts — they can never be activated or sent through the MCP API, so going live still happens in the dashboard.
The MCP server can now create tags. An AI assistant connected to your account can add the tags you use to label contacts and build audiences. Tag names stay unique per account.
The MCP server can now update an existing draft newsletter, not just create new ones. An AI assistant can revise the title, subject, body, sender, template or audience filters of a draft. Only drafts can be edited — once a newsletter is scheduled or sent it is locked — and edits never change the status, so the newsletter stays a draft you review and send from the dashboard.

June 26, 2026

Outbound webhooks: register HTTPS endpoints under Settings → Webhooks and receive signed POST callbacks in real time when contacts subscribe, unsubscribe, or resubscribe, when a newsletter finishes sending, when a sequence step is sent, and when a contact completes a sequence.
Each delivery is HMAC-signed (X-Byomailer-Signature) so you can verify authenticity, retries with backoff on failure, and every attempt is recorded in a per-endpoint delivery log you can inspect and test from the dashboard or the API.
While building or editing a segment, you now see a live count of how many contacts currently match — updated as you adjust the filters, just like the newsletter audience preview.
Segments are now archived instead of deleted. Archiving hides a segment from the picker so it can't be picked for new newsletters or sequences, while anything already referencing it keeps its audience unchanged. Restore an archived segment anytime from the new Archived view.

June 25, 2026

Contacts who finish a sequence are now tracked as Completed instead of lingering in the final step. The last step's contact count and list now show only contacts still waiting there, so the numbers match what's actually pending.
Sequence and per-step views gained a Completed metric, and you can filter a sequence's contacts down to just those who finished. Existing finished contacts were backfilled automatically.
You can now save reusable Segments — named, dynamic audiences built from the same filters you already use on newsletters and sequences. Build a segment once (for example 'Opened in the last 30 days' or 'US contacts on the Pro plan') and reuse it instead of rebuilding the same filters every time.
When targeting a newsletter or sequence, pick a saved segment instead of custom filters. Segments are evaluated live: edit a segment and every draft newsletter and live sequence using it updates automatically.
Each segment shows exactly who matches, with a contact count and a browsable list, and tells you which newsletters and sequences use it.

June 15, 2026

The MCP server can now help you compose newsletters, not just read stats. Four new tools let an AI client build a draft for you: view the audience filters available on your account, calculate how many contacts a set of filters would reach, create a draft newsletter, and send yourself a test copy.

June 9, 2026

You can now send your first 25,000 emails free, before subscribing. Newsletters and sequences both count toward the allowance, so you can test real deliverability through your own SES before paying.
You can now add contacts to a sequence directly from the Contacts screen. On a contact's detail page, a new Sequences section lets you enroll that contact; from the Contacts list, select multiple contacts with checkboxes and add them all at once.
Both entry points open the same modal: pick a live sequence, confirm, and the contacts are enrolled. Sequence filters still apply, so contacts that don't match are skipped, and one failed contact never blocks the rest.
A summary message tells you how many contacts were added and how many were skipped (already enrolled or filtered out).

June 4, 2026

New read-only MCP server at /mcp lets AI clients (Claude Desktop, Claude Code and other Model Context Protocol clients) read your campaign data using your existing API token as a bearer token.
Eight tools cover discovery and reading: list newsletters and sequences, plus newsletter stats, newsletter content, sequence stats, sequence content, individual sequence step content and per-step stats.
Every tool is read-only and scoped to your own account — the assistant can analyse your campaigns but cannot send, edit or delete anything. See the new MCP Server guide in the documentation.
Sequences now have read-only REST API endpoints to match: GET /api/v1/sequences (list), /sequences/{id} (content with steps), /sequences/{id}/stats (sequence totals), /sequences/{id}/steps/{stepId} (step content) and /sequences/{id}/steps/{stepId}/stats (per-step stats). The API and MCP return identical data. Added to the API reference, OpenAPI spec and Postman collection.

June 1, 2026

New SES Savings Calculator at /ses-savings-calculator shows the raw Amazon SES sending cost ($0.10 per 1,000 emails, no per-contact fee) versus Mailchimp, Kit, Klaviyo and ActiveCampaign — for people pricing out SES on its own.
Both calculators now cross-link, and the new one is linked from the site footer under Product.
The SES calculator is honest that SES is just the sending pipe — no lists, editor or sequences — and points to the full BYOMailer comparison for the product layer.

May 28, 2026

Landing page now reads as a live product, not a waitlist — the hero leads with the real number (100k emails ~$10 vs $600+ on Mailchimp) and the Legendsverse case study is cited as proof.
Every paid pricing tier now has a Create-your-account button, and a 30-day money-back guarantee (full refund, no questions asked) sits under the pricing grid.
Features now lead with Automations — the part raw SES can't do — instead of basic campaigns.

May 25, 2026

Sequence detail page now shows email performance across all steps — sent, delivered, deliverability, opened, open rate, pending, bounced, unsubscribed and complained — matching the newsletter detail layout.
Each step in the sequence list shows the same per-step metrics inline so you can spot which step is dragging deliverability down.
Sequence step detail page now has its own email performance card scoped to just that step.

May 22, 2026

Newsletter detail page progress bar now advances correctly while batches dispatch — the total recipient count locks in at send time instead of growing alongside the sent count.
Preview text (inbox preheader) is now available on newsletters and sequence steps — write the short teaser shown next to the subject in Gmail, Apple Mail and other clients. Supports template variables like the subject, with separate values for A/B variants and through the API.

May 21, 2026

Custom tracking domains now serve open and click tracking links over HTTPS through a managed proxy that issues a valid TLS certificate for your subdomain automatically.
Setup is now a single A record pointing your tracking subdomain at the IP shown on the Email Identity settings page — no more CNAME to awstrack.me.
Automations index redesigned: clearer Live/Paused status, status filter tabs, search, and a When → Then chip flow so you can read each rule at a glance.

May 16, 2026

Custom link domains let you serve unsubscribe and preference-center links on your own domain (e.g. mail.yourbrand.com) instead of byomailer.com. Add a CNAME, and Cloudflare issues and renews the TLS certificate automatically.
Configure a custom link domain per email identity from its settings page, with a one-click status check while the certificate is being issued.
Custom link domains only ever serve unsubscribe and preference pages — every other route stays locked to the main app.

May 15, 2026

Newsletter and sequence filters gain three new categories. Date filters target when a contact signed up — before or after a date, in the last N days, more than N days ago, or between two dates.
Engagement filters target newsletter activity: opened, clicked, or received (and the negatives — not opened, not clicked, not received). Scope it to any newsletter or a specific one, and to all time or the last N days.
Location filters target contact country or timezone, matching any of a set or excluding them.
Contact attribute filters now support operators beyond exact match — contains, does not contain, greater than, less than, is set, and is not set — with each filter only offering the operators that make sense for it.
Newsletter detail page adds a Deliverability stat — the share of sent emails confirmed delivered by SES — alongside the existing sent, open rate, and bounce metrics.

May 14, 2026

Editor toolbar adds font family, font size, text color, and a block-type picker. Family options are limited to email-safe stacks (Arial, Helvetica, Georgia, Times, Verdana, Tahoma, Courier, JetBrains Mono, system) so what you pick is what recipients see.
Font size uses a named scale (XS, S, M, L, XL, 2XL → 12, 14, 16, 18, 24, 32 px). Color picker accepts any hex (#RRGGBB), remembers your 5 most recent colors per device, and resets cleanly.
Block type is now a single dropdown with Paragraph, Heading 1, Heading 2, Heading 3 — replacing the three heading buttons. Selecting multiple lines and changing block type now applies to every line, not just the first.
Headings, paragraphs, lists, and blockquotes ship with sensible defaults baked into the saved HTML, so a plain message lands looking intentional in Gmail and Apple Mail without you styling every block.
When a template is applied, the editor now shows the template's header and footer above and below the editable area as faded read-only sections, so you see the full email shape while you write — without the schema mangling that used to break custom template HTML.
Newsletter Preview step and the Newsletter detail page now render the email inside an isolated iframe at full container width and auto-grow to the content height. App theme styles can no longer leak into the preview, and what you see matches what recipients receive.

May 12, 2026

Add Identity is now a full-screen wizard at /settings/identities/create instead of an inline form. Pick an existing domain identity from your AWS account (verified or pending) or register a new one.
Existing AWS domain identities show their AWS verification status. Domains already in BYOmailer are clearly marked as such and disabled in the picker so you never re-add by accident.

April 27, 2026

Interactive API reference is live at /docs/api with the OpenAPI 3.x spec at /docs/api.json — try endpoints, browse schemas, and download the spec for your own tooling.
API is now versioned at /api/v1/. Old /api/... URLs keep working via a permanent redirect (preserving method and body), but please update your integrations to /api/v1/ directly.
All list endpoints now use cursor pagination — page through results with meta.next_cursor and meta.prev_cursor.
Test-mail (5/min) and recipient-preview (30/min) endpoints now have per-user rate limits to keep things fair.
Newsletter html_content is now capped at 500KB. The list endpoint omits html_content / text_content for faster responses — use the show endpoint for the full body. scheduled_at is required when status is 'live' and rejected otherwise. Deleting a newsletter is now restricted to drafts.
Newsletters API supports the full creation flow over HTTP: POST /api/v1/newsletters/{id}/test-mail to send yourself a preview, POST /api/v1/newsletters/{id}/ab-winner to lock in an A/B winner, POST /api/v1/newsletters/contacts/preview for recipient counts, and GET /api/v1/newsletters/{id}/variables to inspect detected {{ var }} placeholders.
Newsletter create and update accept ab_test_enabled with subject_b and html_content_b for split tests, content_variables for {{ variable }} defaults, and email_template_id to wrap content inside a saved template.
Newsletter responses now embed the email_identity object, expose A/B side fields and content_variables, and return 0 (instead of null) for open_rate and unsubscribe_rate when there are no sends yet.
Newsletter index accepts ?search=<title or subject> and rejects unknown ?status values.
Updating or deleting a non-mutable newsletter (queued, ab_testing, sent, failed) now returns 422 with a clear status validation error instead of 404.
New read-only API endpoints for browsing email templates: GET /api/v1/email-templates, /api/v1/email-templates/default, and /api/v1/email-templates/{id}. Email identities also gained GET /api/v1/email-identities/{id}.

April 23, 2026

Email templates now use a {{ content }} placeholder that marks the editable slot inside a reusable template shell.
Starter picker replaces the legacy create page. Pick a system starter or start blank to create a new template; system templates are no longer used directly.
Each client gets a default template on registration and can mark any template as default from the templates list. Newsletter and sequence step editors auto-apply the default on empty drafts.
When a template is applied to a newsletter or sequence step, the shell becomes read-only inline and only the content slot stays editable.
Templates must contain exactly one {{ content }} placeholder to save. Removing the unsubscribe link triggers a deliverability warning and requires explicit confirmation.
Removed the automatic unsubscribe footer from outgoing newsletters and sequence emails; the template provides the link.

April 16, 2026

Contacts API gained GET /api/contacts (paginated, filterable by list, tag, topic, search, unsubscribed) and GET /api/contacts/{id} with tags, lists, and topics included.
Contact API endpoints now scope by client instead of the individual user, so teammates on the same client share read and write access.
Newsletter API gained DELETE /api/newsletters/{id}, a status filter on the index, pagination capped at 100 per page, a filters array cap of 20, and a new 'scheduled' status for future-dated sends.
Email Identity API exposes identity_status and accepts ?identity_status= to filter. Live newsletter sends now require a verified email identity.
Newsletter responses include delivery + engagement metrics (total, sent, opened, bounced, unsubscribed, complained, open_rate, unsubscribe_rate) plus total_contacts_reached and ab_test_enabled.
Newsletter scheduling now distinguishes 'draft' (editable, not sending) from 'scheduled' (editable until the scheduled time) so the scheduler never auto-dispatches a pure draft.

April 15, 2026

Topics let subscribers opt out of individual content categories inside a list while staying subscribed to the rest.
New preference center, linked via the {{ preferences_url }} template variable, lets contacts toggle topic subscriptions without unsubscribing globally.
Creating a topic on an existing list now auto-subscribes every current list member in the background.
Topics can be used as a new filter category when building segments for newsletters and sequences.
New Topics API endpoints under /api/lists/{listId}/topics for full CRUD.

April 14, 2026

Saved email templates let you create, duplicate, and reuse content across newsletters, sequences, and opt-in emails.
A template picker is built into every content editor for quick one-click insertion.

April 7, 2026

Email logging tracks every SES API request, response, and SNS delivery event per client.
Email log detail page shows the full request payload, response payload, and SNS event data.
Email logs API endpoints let you list and retrieve logs programmatically.

March 29, 2026

Newsletter API endpoints allow listing, viewing, creating, and updating newsletters programmatically.

March 25, 2026

Custom tracking domains let you replace the default awstrack.me links with your own branded subdomain for better deliverability.
New documentation guide walks through setting up a custom tracking domain step by step.
SES API permission checks verify your AWS credentials have the right access before sending newsletters or sequences.
Email Credentials settings page shows a permission status dashboard with a manual recheck button.
Hourly sync command automatically keeps SES permissions and tracking settings up to date.
Release notes now pull entries from a shared JSON file.
Release notes UI is powered by a reusable timeline component.

March 24, 2026

Create contacts inline on the contacts index with attribute editing plus instant list and tag assignment.
Contact detail screen gained one-click unsubscribe and resubscribe actions with polished attribute management.
Newsletter builder uses reusable blocks with a TipTap editor and HTML sanitization for safer content.
Blocks API endpoints now exist with SafeHtml validation for anyone integrating BYOMailer programmatically.
Documentation, API reference pages, and the Postman collection were refreshed to include the new unsubscribe endpoint.

March 23, 2026

Reusable content blocks gained a TipTap builder, request validation, and safer rendering so marketing teams can drop polished sections into newsletters with confidence.
We launched a savings calculator that compares BYOMailer against other providers, helping finance and leadership evaluate switching costs.

March 22, 2026

Documentation moved into dedicated Guides and API reference sections with a matching UI, making it easier for teams to find the exact playbook or endpoint they need.
Blocks now use the TipTap editor everywhere, so content stays consistent between creation forms and the actual newsletter experience.

March 21, 2026

Introduced reusable 'block.*' template namespaces so product and marketing teams can share modular email sections across newsletters.

March 20, 2026

SES webhook ingestion and newsletter processing jobs are now more resilient, preventing dropped delivery signals.
Horizon monitoring and default environment settings were tuned to keep large-scale sending stable.

March 19, 2026

SES webhook handling includes smarter retries and better scoping to keep subscriber status accurate.
Newsletter batch dispatch hardened with additional fixes to prevent race conditions during large sends.

March 18, 2026

Shipped an onboarding checklist widget that floats throughout the app, guiding new workspaces through critical BYOMailer setup tasks.

March 17, 2026

Published alternative comparison pages (Mailchimp, Kit, Klaviyo, ActiveCampaign) so prospects can evaluate pricing at a glance.
The contact detail screen now lets you add or remove lists, tags, and custom attributes inline, eliminating context switches when updating someone's profile.

March 16, 2026

Sequence scheduling and background job coordination were tightened so steps fire exactly when expected.
Unsubscribe pages now include a resubscribe button so contacts can opt back in with a single click.

March 15, 2026

Email tracking now supports configurable open and click tracking right inside BYOMailer.
Custom tracking domains follow your SES identity DNS records, simplifying setup for every sender.

March 13, 2026

Expanded automated test coverage for registration, dashboards, and visual automations to keep new releases stable.

March 11, 2026

Launched the visual automations builder with a drag-and-drop workflow canvas, enrollment engine, and step-by-step contact progression.
Visual automations integrate with sequences so contacts automatically advance when a sequence finishes.
Processing commands and jobs handle enrollment and step execution in the background for hands-off automation.

March 10, 2026

Newsletter sending refactored with a dedicated transport layer, improving reliability and testability of the mail pipeline.

March 7, 2026

Newsletter batch dispatch refactored for atomicity, moving batch creation into a dedicated orchestrator job that adds chunk jobs incrementally.

March 5, 2026

Team management launched with invite-based onboarding, role assignments, and the ability to archive inactive members.
Weekly summary email digest keeps workspace owners informed about sending activity on a recurring schedule.

March 4, 2026

SES quota summary card added to the dashboard so senders can monitor their sending limits at a glance.
Newsletter recipients table now includes a status filter for easier delivery tracking.
Contacts remain attached to sequences after completion instead of being detached.

March 3, 2026

Lists now support double opt-in, sending a confirmation email before fully subscribing a contact.
Contacts can be exported from the contacts index for use in external tools or reporting.