---
title: "Freshly Minted: what's new in August"
description: "Our August roundup with our ISO 27001 certification and a batch of smaller improvements."
url: "https://lettermint.co/blog/freshly-minted-whats-new-in-august"
published: "2026-08-31"
last_updated: "2026-08-31"
---

# Freshly Minted: what's new in August

> Our August roundup with our ISO 27001 certification and a batch of smaller improvements.

Welcome to the third edition of *Freshly Minted*, our
monthly round-up of everything we've built at Lettermint,
including the smaller improvements that never quite make
it to the changelog. August is quiet on most calendars.
Ours wasn't, and we promised you something last month.

![Lettermint ISO 27001 certified](https://lettermint.co/content/blog/lettermint-iso-27001.webp)

## Lettermint is ISO 27001 certified

Time for some confetti. Lettermint is now
certified to ISO/IEC 27001:2022, the international
standard for information security. An independent auditor
has reviewed how we protect your email data and confirmed
that it holds up in practice, not just on paper.

For most of you, nothing changes in how you send. What
changes is what you can prove. Next time someone at work
reviews Lettermint as a vendor, point them to the
certificate in our
[Trust Center](https://trust.lettermint.co). The
certificate itself is framed and hanging in the office.
[Read the full story](https://lettermint.co/blog/lettermint-iso-27001-certified).

![Lettermint managed DKIM](https://lettermint.co/content/changelog/lettermint-managed-dkim.webp)

## Rotate your DKIM keys automatically with managed DKIM

A DKIM key is something you set up once and then forget
about. For years, usually. Security guidance says it
should have a limited lifespan, and if you work to a
standard like ISO 27001 you need to show that it does.

With managed DKIM that's now on us. Every six months we
replace the key we sign your email with, without
interrupting your sending. Two CNAME records in your DNS
take turns, so recipients keep verifying your email while
the switch happens. Need a new key sooner? Start the
rotation yourself from your dashboard.

New domains get managed DKIM from the start. Domains you
added earlier can switch over from the DNS page whenever
it suits you.
[Read the changelog](https://lettermint.co/changelog/managed-dkim-key-rotation).

## Enforced TLS for sensitive email

When we deliver your email, we encrypt the connection to
the recipient's mail server as soon as the other side
supports it. Whether that happens is up to the receiving
server. If it doesn't support TLS, the email still
arrives, just unencrypted. For a newsletter that's rarely
a problem. For an invoice or a patient record it might be.

With **Enforced TLS** you decide. Set a route to
*Enforced* and everything on that route is only delivered
over an encrypted connection, or not at all. Everything
else stays on *Opportunistic*, the default.
[Read the changelog](https://lettermint.co/changelog/send-email-only-over-an-encrypted-connection-with-enforced-tls).

![Lettermint import suppressions](https://lettermint.co/content/changelog/lettermint-bulk-suppressions.webp)

## Import and export your suppressions

Every hard bounce and every unsubscribe lands on your
suppression list, and we check that list before every
send. Until now you could only work with it one address at
a time.

Migrating from another provider? Upload their list as a
CSV and the addresses you already know are trouble stay
blocked from day one. Running your own marketing tools
alongside Lettermint? Export the list, filtered the way
you would in the overview, so both systems know the same
opt-outs. And when a block shouldn't last, like a mail
server that was down for a day, tick the rows and unblock
them in bulk.
[Read the changelog](https://lettermint.co/changelog/import-and-export-suppressions).

## Improvements & fixes

Beyond the headliners, we polished a lot of smaller things
too:

- **Webhooks with scope**: one webhook for your whole team, a set of projects or a set of routes, instead of one per route. Every payload now tells you which project and route it came from, and two new events fire when an address is added to or removed from your suppression list. [Read the changelog](https://lettermint.co/changelog/webhooks-for-team-projects-or-routes).
- **Better open and click detection**: we improved how we filter out scanners and other automated opens, so your rates are more accurate. Tracking stays opt-in, per route.
- **Proton Mail on Time to Inbox**: our public delivery speed monitor now includes Proton Mail, next to Gmail, Outlook, iCloud and the rest. [See the numbers](https://lettermint.co/time-to-inbox-tti).
- **Multiple tags per email**: next to the single `tag` you can now attach up to 20 name and value pairs, like `campaign=welcome`, and filter on them.
- **Keep your own Message-ID**: relaying from a ticketing system? Ask us to preserve your `Message-ID` and replies thread back to the right ticket.
- **Block disposable addresses**: a new route setting suppresses recipients on throwaway email services before they hurt your list quality.
- **Edit pending invitations**: change the role or fix the email address without deleting and resending the invite.

This month again, a good share of this started as a
message from someone using Lettermint. So keep it coming.
You can reach us through the dashboard or
[Discord](https://lettermint.co/r/discord). We read every
message and genuinely build with it.

*See you in September, when the out-of-office replies
stop.*
