Blog

Email infrastructure notes.

Short, practical writing about delivery, DNS identity, abuse controls, API behavior, and compliance readiness.

Latest article

The most recent operational note from the Sendix team.

Operations

Jun 2, 20265 min read

Why system mail should use its own delivery identity

Security, billing, support, and status notifications should not compete with customer traffic. Separate identities make incidents easier to isolate and explain.

system maildeliverabilitydns

Read article

Topics

The core areas covered by the Sendix engineering journal.

Deliverability

DNS, queues, provider acceptance

Trust

Compliance, audit readiness, system mail

Developer experience

APIs, errors, logs, webhooks

All articles

Guides and engineering notes for teams operating transactional email.

Why system mail should use its own delivery identity

Latest

Security, billing, support, and status notifications should not compete with customer traffic. Separate identities make incidents easier to isolate and explain.Operations5 min read The mail operations signals every delivery team should watchPort 25, PTR, EHLO, SPF, DKIM, DMARC, queue depth, and recipient-domain acceptance rates are the difference between guessing and operating.Deliverability6 min read Preparing email infrastructure for a SOC 2 auditSOC 2 is not a badge you self-assign. It is an evidence program, a control system, and a third-party audit process.Compliance7 min read A practical taxonomy for delivery failuresStable delivery reason codes help developers decide whether to retry, fix DNS, clean recipients, or escalate reputation work.Developer Experience4 min read