Tag
8 articles tagged with transactional email.
An email API POSTs JSON over HTTPS; SMTP relay runs a multi-step protocol conversation on port 587. This guide compares the two on latency, batching, error handling, templates, and vendor lock-in, includes a full port reference table, and shows the hybrid setup most teams actually end up running.
A practical reference for SMTP error codes: how to read a reply in ten seconds, the difference between 4xx soft bounces and 5xx hard bounces, lookup tables for the codes you will actually hit, and fixes for the five that cause most real-world pain — plus the ports that quietly cause silent failures.
The nine transactional email templates every product needs, with copy examples for password resets, receipts, failed payments, and shipping notices. Includes a transactional vs. marketing comparison table, sending-stream separation advice, variable-naming rules, and a pre-launch QA checklist.
How to choose the best email API in 2026 without getting lost in feature checklists. Covers the eight evaluation criteria that actually predict deliverability, the four categories providers fall into and their tradeoffs, how to read API docs like an engineer, a REST-versus-SMTP comparison table, and a safe migration sequence.
A transactional email is a one-to-one message triggered by a user action. Here is how it differs from marketing email, 16 examples to audit your product against, the SMTP ports and DNS records you need, and where promotional content crosses the line.
An SMTP relay forwards your outgoing email through trusted servers so it reaches the inbox. Learn how relays work, how they differ from direct delivery, and when to use one.
How SMTP relay services deliver your email, and the concrete criteria to evaluate one: authentication, IP reputation, own-domain sending, reporting, and pricing.
Transactional emails are triggered by a user's action; marketing emails promote to a list. Here's the difference in purpose, consent, deliverability, and design.