Kit SMTP Settings and Configuration (2026)

People searching for Kit SMTP settings rarely want Kit’s mail servers. They want one of four things: a transactional send path, credentials for a CMS or app, sending-domain authentication, or parity with an ESP they are leaving. Kit solves exactly one — domain authentication — covered in full below, with the route for the other three.

Quick reference

Why Kit has no SMTP relay

Kit is a creator-first newsletter platform, not a mail-transport vendor. Its data model is list-centric: a message is a Broadcast or Sequence step aimed at a subscriber record carrying tags, segments, consent state and unsubscribe status. Deliverability depends on that binding — opt-in confirmation, engagement scoring, complaint suppression and the Creator Network reputation pool all key off it. An open relay would put arbitrary, unconsented traffic on that same reputation. The omission is architectural, not a roadmap gap.

The API reflects it. Kit’s machine-readable documentation index at developers.kit.com/llms.txt contains zero occurrences of SMTP, relay or transactional, and the pricing page lists no such entitlement at any tier. The evidence is positive, not merely absent: the one sending endpoint, create a broadcast, targets subscribers only by segment or tag ids. No path, SMTP or API, delivers one message to one arbitrary address.

What you actually need instead

Sending transactional email

Password resets, receipts, order confirmations, license keys and magic links cannot go through Kit at all. You need a relay, and the pick depends on workload. Postmark fits best when resets and receipts must land fast: it enforces a hard split between transactional and broadcast streams, and its per-message event detail makes a broken checkout trivial to debug. Amazon SES is cheapest at volume on AWS, at the cost of your own warmup and bounce plumbing. Mailgun and SendGrid are the pragmatic middle; Brevo and MailerSend add a template UI.

Connecting a CMS or app

WP Mail SMTP, FluentSMTP, Post SMTP, a Laravel or Rails mailer and contact-form plugins all want the same four values: host, port, username, password. Kit issues none, so no configuration will work. Point those tools at your relay — most ship a first-class integration for Mailgun, SendGrid, Postmark and SMTP2GO, skipping raw SMTP and adding bounce webhooks. Kit still owns the marketing half: push form submissions in as subscribers via the v4 API or a Kit plugin.

Routing notifications and automations

If you want an event in Kit to trigger a message elsewhere, that is an automation problem, not an SMTP problem. Kit supplies the trigger — new subscriber, tag applied, purchase — via webhooks or a Zapier, Make or n8n connector, and your relay sends. Be clear what those listings are: a Kit + SMTP page on Zapier or Pabbly glues a Kit trigger to an SMTP server you supply. None expose Kit mail servers.

Sending domain authentication

This is what most Kit SMTP searches are genuinely after, and the one thing Kit solves properly: a Verified Sending Domain. It DKIM-signs your messages with your domain, authenticates SPF with your domain, puts your from-address in the return-path machines see, and lets Kit mail pass DMARC.

SPF and DKIM setup

Kit uses a delegated CNAME model rather than a literal SPF include and a pasted DKIM key, so it can rotate keys without you re-editing DNS. Open Settings › Email › Verify your sending domain, copy the records, and add them at your DNS provider — or use Kit’s Entri flow, which writes them at supported providers. Records are per account and dashboard-only, so there is no universal value to copy from a blog post. The shape you paste:

; Kit Verified Sending Domain — values are per-account.
; Copy exact pairs from Settings › Email › Verify your sending domain

<dkim-host>._domainkey.example.com.  IN  CNAME  <target-from-dashboard>
<spf-host>.example.com.              IN  CNAME  <target-from-dashboard>
<return-path-host>.example.com.      IN  CNAME  <target-from-dashboard>

; TTL: provider default. Do not flatten. Do not proxy (DNS only).

Two failure modes cause most unverified domains. Proxying the CNAMEs through a CDN breaks resolution to Kit’s targets, so set them DNS-only. And if your registrar auto-appends the domain, a fully-qualified host yields a doubled record such as host.example.com.example.com, which silently never verifies.

DMARC alignment

Kit makes DMARC conditional on domain verification: add a record only if you send through your own verified sending domain. If verification is not done, do that first — a policy over an unaligned stream buries your own newsletter. Kit’s default record is p=none, the most permissive: monitor-only, enforcing nothing.

; Stage 1 — monitor only, collect reports
_dmarc.example.com.  IN  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com; fo=1"

; Stage 2 — once reports confirm Kit aligns
_dmarc.example.com.  IN  TXT  "v=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc@example.com"

; Stage 3 — once every legitimate stream aligns
_dmarc.example.com.  IN  TXT  "v=DMARC1; p=reject; rua=mailto:dmarc@example.com"

Run stage 1 for at least two weeks and read the reports before tightening. If you followed the pairing advice below you have two authenticated streams — confirm both align under p=none before moving to quarantine. Enforcing while a second stream is half-configured bounces your own password-reset mail, far worse than a delayed newsletter.

Sending limits

Kit publishes no hourly throughput cap, and a per-message recipient cap is not a meaningful unit here: a Broadcast targets a segment, a tag or the whole list. Neither has been reconstructed.

Common mistakes

Pairing Kit with an SMTP provider

Recommended setup

Run a two-tool split and give each its own subdomain. Kit keeps marketing on news.example.com as its Verified Sending Domain; the relay takes transactional on txn.example.com. The isolation is the point — separate DKIM keys, return-paths and reputation — so a high-complaint newsletter cannot drag password resets into spam. For most creator businesses Postmark is the cleanest pairing because it enforces the same separation internally; on AWS, Amazon SES is cheaper at volume; if a non-developer configures it, Mailgun or SMTP2GO ship drop-in WordPress plugins. Data flows one way: your app calls the relay directly, while Kit owns the list and receives customers through the v4 API.

Keeping the two systems from conflicting

Three rules prevent the usual mess. Never authenticate both providers on the same hostname — two DKIM setups and two return-paths on one subdomain break alignment in ways that are painful to diagnose. Agree on ownership per message type: welcome emails, sequences and the newsletter belong to Kit; receipts, resets and magic links belong to the relay. Anything ambiguous, such as an abandoned-checkout nudge, must live in exactly one system or the customer gets it twice. And suppress deliberately: a Kit unsubscribe must not block a password reset.

Keep one DMARC policy at the organisational domain covering both subdomains, and verify in aggregate reports that each stream aligns before moving past p=none. Arriving from an ESP that bundled marketing and SMTP in one account — usually Brevo or Mailchimp with Transactional — budget for splitting one authenticated stream into two. Creators comparing options weigh Kit against MailerLite and AWeber, which carry the same boundary.

Frequently asked questions