// product · smtp

The relay you already know how to use.

Already have a mailer? Change four settings and you are sending through Drin. No rewrite, no SDK — point any SMTP client at smtp.drin.run, use your API key as the password, and get the same deliverability as the REST API.

four settings · then send
# point any SMTP client at Drin
host      smtp.drin.run
port      465   # TLS — or 587 for STARTTLS
username  drin
password  $DRIN_API_KEY   # your API key
from      hello@drin.run

# Nodemailer example
const t = nodemailer.createTransport({
  host: "smtp.drin.run", port: 465, secure: true,
  auth: { user: "drin", pass: process.env.DRIN_API_KEY }
});
// connection[01/03]

One endpoint, your key.

There is no separate SMTP password to provision and rotate. Your API key is the credential — the same one the REST API and SDKs use. Revoke it once and every interface stops at the same moment.

Prefer the REST API? →

Hostsmtp.drin.run
Ports465 (TLS) · 587 (STARTTLS)
Usernamedrin
PasswordYour API key — paste it as the SMTP password
EncryptionRequired — plaintext submission is refused
Project routingThe key's project; or set X-Drin-Product as a header
// what you get[02/03]

A relay, not a second-class path.

01

Any language or framework

Nodemailer, Django, Rails ActionMailer, PHPMailer, Postfix relayhost — if it speaks SMTP, it speaks to Drin.

02

Same behaviour as the API

SMTP sends behave exactly like REST sends — identical authentication, suppression and webhooks.

03

Suppression applies

Hard bounces and complaints are suppressed automatically, the same as the API. Past failures never get re-sent.

04

Per-message headers

Set Reply-To, custom headers, and an Idempotency-Key right in the message — no separate control plane needed.

// pairs well with[03/03]
// drop it in

Repoint your mailer in five minutes.

Grab a key, change four settings, and your existing SMTP stack is sending through Drin. Test freely; production starts at $3 a month.