Developers

Mailer To Go is transactional email you can wire up in a few minutes, from any language. No proprietary SDK to learn — you send over standard SMTP using the mailer you already have, and a REST API is on the way.

Quickstart

Sign up and add your sending domain (a subdomain like mtg.yourdomain.com is recommended — here’s why).
Publish the SPF and DKIM records shown in your dashboard (and a DMARC policy). Walkthrough: email authentication, end to end.
Grab your SMTP credentials and set them as environment variables.
Send.

export MAILERTOGO_SMTP_HOST=smtp.mailertogo.com   # exact host shown in your dashboard
export MAILERTOGO_SMTP_USER=...
export MAILERTOGO_SMTP_PASSWORD=...

Send from your language

Any language that speaks SMTP works. A minimal example in each:

# Ruby — the mail gem
Mail.deliver do
  from "hello@yourdomain.com"; to "user@example.com"
  subject "Hello"; body "It works."
  delivery_method :smtp, address: ENV["MAILERTOGO_SMTP_HOST"], port: 587,
    user_name: ENV["MAILERTOGO_SMTP_USER"], password: ENV["MAILERTOGO_SMTP_PASSWORD"],
    enable_starttls_auto: true
end

// Node.js — Nodemailer
const t = require("nodemailer").createTransport({
  host: process.env.MAILERTOGO_SMTP_HOST, port: 587,
  auth: { user: process.env.MAILERTOGO_SMTP_USER, pass: process.env.MAILERTOGO_SMTP_PASSWORD },
});
await t.sendMail({ from: "hello@yourdomain.com", to: "user@example.com", subject: "Hello", text: "It works." });

Full examples for Ruby, Python, Node.js, and Go — including framework config for Rails, Django, and Laravel — are in the sending quickstart. SMTP settings, ports, and the reference are in the documentation.

REST API (coming soon)

A JSON send API is in development:

POST https://api.mailertogo.com/api/v1/emails
Authorization: Bearer <your API key>

{ "from": "...", "to": "...", "subject": "...", "html": "...", "text": "..." }

It isn’t live yet — send over SMTP today, and watch the docs for the announcement.

Deploying on a platform?

Mailer To Go is a config-var-native add-on on Heroku, Addons.io, and Build.io — provision it and your credentials are injected automatically. See sending transactional email from Heroku.

Production checklist

Read credentials from environment variables, never source.
Send from a verified subdomain.
Use port 587 (STARTTLS) or 465 (SSL) — always encrypted.
Send from a background job and retry transient failures; hard bounces are suppressed automatically.

Questions? Read the docs or get started.