Changelog

What shipped, and what it changed

Every change customers can see, in the order it happened. Where something altered behaviour you were relying on, it says so — and where it changed nothing for existing keys, it says that too, because that is usually the first question.

39 entries  ·  July–November 2026  ·  updated 2026-11-15

November 2026

Two-step sign-in, with a passkey or an authenticator app

Signing in to the dashboard can now ask for a second step. Set one up on the new Security page, in either of two ways, neither of them a fallback for the other: a passkey — your face, fingerprint or device PIN, or a security key you plug in — or an authenticator app showing a six-digit code, including open-source ones such as Proton Authenticator, Aegis and Ente Auth. You can add up to ten, name each one, and remove any of them.

Where a passkey is kept is your own device’s choice, not ours. It can be saved to iCloud Keychain, Google Password Manager or a password manager and appear on your other devices, or stay on the one device and go with it. We only ever receive the public half of the key, and all we can tell you about the other half is what your device tells us.

Ten recovery codes are for the day the phone is lost or replaced. They are shown once, each works once, and using one forgets every computer you had asked us to remember.

You can ask us to remember a computer, so it skips the second step at sign-in. That is a convenience and never a way around the second step: changing anything on the Security page still asks for a code. Anyone can turn remembering off for themselves, whatever the account allows.

Owners and admins can require two-step sign-in for everyone on the account. Each person then sets up their own second step the next time they sign in and cannot use the dashboard until they have, and while it is required nobody can remove their last method. The same page sets how many days a computer may be remembered for, for the whole account; 0 means every sign-in asks for a code.

Nothing about sending changes. API keys, SMTP and your existing integrations are untouched — this is about who can sign in to the dashboard.

Webhooks for sent and deferred

Two new webhook events. sent says a message was handed to the mail server; its outcome follows. deferred says an attempt failed for now and will be tried again, with the receiving server’s own reply, its code and which server answered, and the attempt number. In the v3 format they are email.sent and email.deferred; in the SendGrid format, processed and deferred.

Both fire for every message and every retry, so an endpoint receives them only when you tick them on the Webhooks page or name them in events. An endpoint that takes every event does not start receiving them.

A dashboard page for emails sent with API v3

Emails (API v3) in the dashboard shows each email sent through /v3 whole: its id, subject and every recipient’s copy, with how many were delivered, bounced or are still scheduled. Open one to see its copies, each linked to its own message page, and to cancel every copy still scheduled with one button. Email Activity still lists the same messages one by one.

Webhooks in three formats, and Standard Webhooks signatures on every one

Each webhook endpoint now has a format. v1 is the payload you already receive, and every existing endpoint stays on it. v3 sends email.delivered, email.bounced and the rest, with each message’s email id, client and group, to match API v3. SendGrid-compatible sends SendGrid’s own Event Webhook JSON, signed with SendGrid’s ECDSA scheme and a key of your endpoint’s own, so a receiver written for SendGrid works unchanged. Choose it on the Webhooks page, or with format on /v1/webhooks.

Every delivery, in every format, is now also signed the Standard Webhooks way (webhook-id, webhook-timestamp, webhook-signature), keyed with your endpoint’s existing secret, so any Standard Webhooks library can verify it. On a v1 endpoint, X-SES-Signature and the payload are exactly as before.

API v3: one email to up to 50 recipients, in the format of the next Zedmail

POST /v3/emails sends one email to up to 50 addresses in to, with tags, metadata, tracking and TLS settings, an unsubscribe group and client, and scheduled_at, which also takes "in 2 hours" or "tomorrow 7am America/Toronto". /v3/emails/batch takes up to 100 emails, and a scheduled email can be cancelled or moved as a whole. Suppressions and unsubscribe groups have /v3 endpoints too.

It uses your existing ses_ keys and is the same account as /v1: the same suppressions, limits, history and webhooks. Each recipient’s copy is an ordinary message with its own id, so nothing about /v1 changes. Every recipient gets their own copy, so cc and bcc are refused for now, and any field Zedmail doesn’t do yet is refused by name rather than ignored. Refusals say which field to fix. See the API reference.

Schedule a send up to 72 hours ahead, and cancel it until then

Add scheduled_at to a send, as ISO 8601 with its zone (for example 2026-11-20T09:00:00-05:00), and the message waits until then, up to 72 hours ahead. Over SMTP, X-SMTPAPI’s send_at schedules every copy and send_each_at gives each to address its own time, as at SendGrid.

Until it goes, a scheduled message has the new status scheduled, and you can move it (PATCH /v1/email/{id}) or cancel it (POST /v1/email/{id}/cancel, or the Cancel button on the message in your dashboard). A cancelled message is never sent and isn’t billed. If the recipient unsubscribes, bounces or complains while it waits, or your account is paused, it isn’t sent then either: a suppressed one ends suppressed, unbilled, and a paused account’s mail waits until the account is cleared. A time within a minute of now is sent now; a time well in the past is refused, because it’s almost always a bug in the code that set it.

Unsubscribe groups, and clients for senders who mail on behalf of others

SendGrid’s unsubscribe groups work here now. Create a group with your own number on the new Unsubscribe groups page or through /v1/unsubscribe_groups, and send with it: unsubscribe_group in the API, asm_group_id in X-SMTPAPI, from a transactional key whose unsubscribe scope is per unsubscribe group. A recipient can then leave one group and keep the rest.

If you send on behalf of other businesses, name the one each message is for in client (unique_args.client over SMTP). Its recipients only ever see that client’s groups, and “unsubscribe from everything” stops that client’s mail, never your other clients’.

The unsubscribe link opens a page with two choices, that list or everything from this sender, and nothing changes until the recipient picks one. Gmail’s and Yahoo’s own unsubscribe button leaves just that group. A preferences page lists the client’s groups with a switch for each, and a recipient who turns one back on sends you a new resubscribed webhook. SendGrid’s <%asm_group_unsubscribe_raw_url%>, <%asm_preferences_raw_url%> and <%asm_global_unsubscribe_raw_url%> tags are filled in. You can import the opt-outs you already hold, and export them; only the recipient can undo one.

SendGrid’s X-SMTPAPI header works over SMTP, and messages can carry metadata

Until now an SMTP message carrying SendGrid’s X-SMTPAPI header was refused, so that a header we only half understood could never deliver to the wrong people. We now read it. to sends each address its own copy, category becomes the message’s tags, unique_args becomes its metadata, and filters can turn open and click tracking on or off for that message. The header is removed before the message is sent.

Some fields are still refused, with a 550 that names them, and nothing is sent: sub and section, because Zedmail sends your message exactly as written, and, for now, asm_group_id, send_at and send_each_at.

The API gained the same thing. A metadata object on a send is returned with every webhook event for that message and by GET /v1/email/{id}, and is never put on the message itself. track_opens and track_clicks override your account’s tracking for one message.

Your Overview loads in about a third less time

Nothing on the page moved. It was doing the same work more than once: the 30-day volume chart and the deliverability score each read your last 30 days of mail separately, and the transport-security panel read its own figures twice — once for the summary and again for the list of domains beneath it. Each pair is now a single read. On the busiest account on the platform the page went from about 530ms to about 350ms.

One number may look slightly different, and it is the same arithmetic over a different span. The chart has always shown 30 calendar days in your account’s timezone, while the deliverability score underneath it covered the last 720 hours. So adding up the bounces on the chart and comparing them with the bounce rate printed below could give you two answers, and nothing on the page said why. The score now covers exactly the days the chart shows.

The “not fully protected” domain table also had no fixed order when several domains were tied, so it could list a different ten of them, in a different order, on two consecutive loads. Ties now sort by domain name.

An Email Activity page, and the same log as an API

The message log used to live at the bottom of your Overview, below the charts, and it is now a page of its own: Email Activity, first in the sidebar under Overview. Search, status, stream and a date range, over everything still inside your retention window. The page says where your history begins, so an empty last page reads as the end of what we keep rather than as nothing sent.

Every filter is in the address bar, so a filtered view is a link you can bookmark or send to us with a question. Paging walks forward from a fixed point instead of using page numbers — which means a list cannot repeat or skip a message while new mail arrives underneath you, the way a numbered pager does. “Back to newest” returns to the top from any depth, and your browser’s back button steps the other way.

Two things the old list could not do. The status filter now offers every state a message can be in: it had five of eight and no blocked, so the one status with mail that was deliberately never sent could not be filtered to at all. And a blocked message that we re-sent successfully from another address now shows green here, as it already did on the message itself — the list used to call it a problem.

The same log is now readable programmatically at GET /v1/email, with the same parameter names, so a filter you paste from an API call into the page shows you the rows that call returned. Your Overview keeps the ten most recent messages and links here.

An API reference, at zedmail.com/docs

There was no reference until now, and the honest reason was that a document describing an API tends to drift away from the API until a reader cannot tell which half is wrong. The one now published covers every /v1 endpoint with the scope each needs, the error envelope with every code it can carry, idempotency, the published limits, the send request field by field, and what each message status means — in English and French.

It is checked against the router on every deploy, in both directions: an endpoint that exists with no entry fails the build, and so does an entry for an endpoint that has been removed. The second is the one that matters to you, because a documented endpoint that answers 404 sends you looking at your own request first.

Webhook payloads, signature verification and the retry schedule stay on the Webhooks page inside your account, where the examples can name your own endpoints.

The webhook verification example named a field that does not exist

The signature-verification example on your Account page told you to read $event['type']. There is no type field — it is event. Anyone who copied that example got null and had to work out why, from our documentation rather than in spite of it. It is corrected, and it was checked against real production deliveries rather than against the example itself.

Two more things it was not saying. The event list omitted blocked, opened and clicked. And unsubscribed is shaped differently from the rest: message_id is null, there is no top-level email, and the address is under data.email — so a handler written from the old sample would have read an empty address on precisely the event that must never be missed.

The example now also shows what to do about replay, which is the pair of fields people ask about. The signature header carries t=, the Unix time the request was signed, and it is inside the signed string — so reject anything whose t is more than a few minutes old; the sample uses 300 seconds. Then de-duplicate on id, the delivery’s uuid, which is the same on every retry. Together those two make a replayed delivery indistinguishable from a retry of it, and a retry you have already processed is a no-op.

October 2026

Webhook deliveries now carry a stable id for de-duplication

Every webhook delivery now carries its own identifier: id in the JSON body, repeated as an X-SES-Delivery-Id header. It is a UUID, and it is the same on every retry of that delivery — so you can store it and safely ignore anything you have already processed.

Retries always re-sent the body byte-identically, so the body itself was usable as a de-duplication key, but nothing in the payload said so. Now there is a field for it. Read it from the body rather than the header when it matters: the signature covers the body, and the header sits outside it.

The retry schedule is documented on the Webhooks page as well: up to seven attempts — immediately, then after 1 minute, 5 minutes, 30 minutes, 2 hours, 8 hours and 24 hours. Any 2xx stops it. Nothing else about the payload changed.

Transactional mail no longer advertises one-click unsubscribe

A transactional key already added no unsubscribe footer. It was still sending the List-Unsubscribe headers, which is what draws the native unsubscribe button in Gmail and Apple Mail — and that button takes no confirmation. A recipient who used it on a receipt was opted out of every receipt from you, with nothing on screen telling them so. Those headers are now withheld on the transactional stream. Broadcast and older keys without a stream are unchanged.

If you want the button on transactional mail, turn on key-scoped unsubscribe for that key: the headers come back and an opt-out reaches only that key’s mail. The {{unsubscribe_url}} merge tag was never affected and still works on either stream — it lands on a page that says what it will do before it does it.

Every message now also carries a List-Help header (RFC 2369) pointing at a page for your recipients: who sent the message, why only you can say how their address reached you, how to stop further mail on that stream, and how to report mail they never agreed to. It names your sending domain and nothing about the recipient — no address, no token, no message id.

Your own headers, on the message and back on the webhook

Send up to ten headers of your own with a message — a survey id, an invoice number, a case reference — and they travel on the message and come back on every webhook event for it. Names are checked against a published reserved list, and anything that would overwrite one of ours, or carry a line break, fails the send with a 422 naming the header rather than being quietly stripped. If nothing at the receiving end needs to read the value, tags still does the same job and keeps it private.

One-click unsubscribe headers are now signed

List-Unsubscribe and List-Unsubscribe-Post are now inside the DKIM signature on both sending paths, not merely present on the message. RFC 8058 asks for that, and a receiver who checks will see them covered by the h= list. Nothing changes on your side, and nothing already sent was affected.

A public FAQ, in both languages

A public FAQ at /faq, answered in English and French: what we hold and what we do not, where the data lives, what happens to a suspended account, how suppression works, and which stream a key should be on. Written from questions customers actually asked, which is why some of the answers are less flattering than a sales page would allow. It grows as questions arrive rather than being finished.

New keys can diagnose, not just send

A new API key is created as Send and diagnose: it can send, and it can read back what happened — delivery status, bounces, suppressions, which DNS record a domain is missing. It still cannot suppress an address, create a webhook endpoint, add a sending domain or touch your team. Existing keys keep the scope they were made with; rotate one to pick up the new default.

Retries that can't send twice

Pass an idempotency_key of your own on a send and a retry stops being a risk. An identical retry within 24 hours returns the first response again, with HTTP 200 and an Idempotent-Replay: true header, and no second message goes out. A retry while the first is still running answers 409; the same key with a different message is refused with 422 rather than quietly handing back the first message's id. A send we reject releases its key, so a bad address is something you fix and retry with the same key. Without a key, nothing changes.

A webhook endpoint per API key

An endpoint can be bound to a single key, so staging events reach your staging receiver and production reaches production. Leave it on All keys and it behaves as it always has — every endpoint that existed before this is unbound. Every event we can attribute to a key now carries api_key_id as well, so one shared endpoint can route on it instead.

Seven more tools for AI assistants

Zedmail's MCP server gained the diagnostic tools: check a domain's DNS, find out why an address is not receiving, read bounce and complaint rates, list and test webhook endpoints. An assistant can now answer “why did that bounce” without anyone opening a ticket. A key only ever sees the tools its own scopes permit.

90 days' notice if we ever shut down

Section 7 of the terms now commits to at least 90 days' written notice, with the service running normally throughout, nothing billed past the stop date, unused prepaid credit refunded, and your sending data, delivery logs and suppression lists exportable the whole time. A municipal customer asked for it in writing, which was a fair thing to want and something we should have stated already.

An opt-out can be scoped to one key

Somebody declining your newsletter should not thereby decline their own password resets. On a transactional key the unsubscribe can be narrowed to that key alone, instead of the whole account. Spam complaints and hard bounces stay account-wide, deliberately: a complaint is a statement about you and that recipient, and a dead mailbox is dead for every key you own.

You hear it from us, not from a 401

If sending is ever held on your account — a bounce or complaint rate over threshold, say — you are emailed at once with the reason. Until this, the only notice an account got was its own next API call failing.

A public authentication checker

/email-check reads any domain's SPF, DKIM and DMARC the way a receiver does and says what is wrong with it. Free, no account, and it works for domains that have nothing to do with us.

Suppression lists hashed at rest

The service-wide suppression list is stored hashed rather than in the clear. Service-wide entries persist while any account still suppresses the address, on a three-year clock, and legal holds are permanent.

A published data processing agreement

Drafted with counsel and published at /dpa.php rather than produced on request. It forms part of the terms and is accepted with them; we will execute a signed copy if your process needs one on file.

September – early October 2026

Attachments

Up to ten files and 10 MB per message. We do not keep them — the bytes are deleted as the message leaves us, and only the filename, type and size stay on the record.

Choose your own retention, 7 to 365 days

Set per stream, so your transactional logs and your campaign logs need not keep the same schedule. When the window passes the whole record goes together: recipient, subject, body and delivery status. Seven days is the floor.

Transactional and broadcast streams

Every API key you create is now one or the other, and the choice changes behaviour rather than labelling it. Transactional sends no unsubscribe footer — nobody should be able to opt out of their own password reset. Broadcast always adds one, in your recipient's language. The two also keep their reputation apart, so a campaign having a bad week does not follow your receipts into the spam folder. Existing keys are unchanged.

A second and third sending address

Separate IP pools, warmed deliberately over months, so that one sender's list problem stops being everyone's deliverability problem. The warming moves a measured fraction of real traffic rather than moving a sender, because receivers judge a new address on the shape of its volume.

Verified TLS you can require

Per key, you can demand that a message is encrypted to a server that proves its identity. If the receiver cannot, the message is held rather than sent in the clear, and we tell you which recipients were affected — and they are not unsubscribed for it. For the major consumer providers it is enforced regardless, because they publish policies saying their servers should never accept unencrypted mail.

August 2026

Erasure that is distinct from suspension

A user-initiated GDPR or Law 25 erasure is now its own terminal state rather than a suspension that looks like one, so reporting, support and every access gate can tell the two apart.

Encrypted off-site backups, verified nightly

Nightly encrypted backups to Québec object storage, with the decryption key held offline so a compromised server cannot read them. Freshness, size and checksum are verified every night, and a full decrypt-and-restore is tested on a schedule. A backup nobody has restored is a hope, not a control.

Pause sending, without suspending an account

A reversible, send-only hold. An account under review stops sending but keeps its dashboard, its keys and its data — which is the difference between a question and a punishment.

July 2026

A plain guide to the DNS

/domain-setup, written for the person who has been handed a registrar login and a list of records, and linked from the dashboard where that person actually is.

Dates in your timezone

Every timestamp in the dashboard renders in the timezone on your account. It had been collected, validated and stored for years while every date on screen was still UTC.

French, properly

The dashboard, the public pages, the account emails and the unsubscribe and feedback pages your recipients see. Subscriber-facing pages negotiate the language from the browser, because a recipient has no account with us to carry a preference.

Billing in your own currency

Canadian dollars, pounds, euros or US dollars, chosen at signup, with their own price points rather than a conversion. Invoices keep the currency they were issued in.

Smaller fixes are not listed. Deliverability work mostly is not either, because it is continuous rather than datable — but when it changes something you can observe, like a sending address or a bounce you would otherwise have seen, it appears here.