
Email one-time codes: expiry, length and what to tell users
A good email one-time code is six digits, expires in about 10 minutes, works once, and is rate limited. Here is how to choose each setting and word the email.
5 min read

A good email one-time code is six digits, expires in about 10 minutes, works once, and is rate limited. Here is how to choose each setting and word the email.
5 min read

A verification email arrives late when the delay is in your queue, in the provider, or at the receiving server. Time each hop to find which, then fix that one.
5 min read

Why a one-time confirmation link can arrive already used, how mail scanners cause it, and a simple two-step design that works for real users and for scanners.
4 min read

Preheader text is the preview line next to your subject. Learn what it is, a sensible length, how to set it in HTML, and how to hide the filler that sneaks in.
4 min read

Follow a Koltrix send from the 202 Accepted response through the queue, DKIM signing, SMTP delivery and the webhook events your app receives.
6 min read

Decisions that make an email-sending API pleasant for years: async acceptance, idempotency, explicit errors, stable fields and a clean event model.
4 min read

Which bulk sender rules apply to receipts and password resets, which apply only to marketing, and why mixing both streams on one domain is risky.
4 min read

Reset emails are a top account takeover vector. Design single-use, short-lived tokens, avoid account enumeration and make the email arrive fast.
4 min read

Passwordless login lives or dies on email delivery. Compare magic links and one-time codes on security, link scanners, latency and cross-device use.
5 min read