SMTP

For an application that already sends mail, this is usually three environment variables and no code change. Your message is stored and sent exactly as your app composed it, including attachments and custom headers.

Not open to the internet yet

SMTP submission is waiting for its TLS certificate, because the password is your API key and must not travel unencrypted. Until this notice is gone, send with the HTTP API, which works today on every plan. The settings below are what it will use.

Host	smtp.pigeonatlas.com
Port	587 (STARTTLS)
Username	anything, since it is ignored
Password	your API key

The username is ignored on purpose. A second credential would be one more thing to rotate without making anything safer, since the key already identifies your account.

Rails

config/environments/production.rb

config.action_mailer.smtp_settings = {
  address: "smtp.pigeonatlas.com",
  port: 587,
  user_name: "pigeonatlas",
  password: ENV.fetch("PIGEONATLAS_API_KEY"),
  authentication: :plain,
  enable_starttls_auto: true
}

Anything else

Environment

SMTP_HOST=smtp.pigeonatlas.com
SMTP_PORT=587
SMTP_USERNAME=pigeonatlas
SMTP_PASSWORD=pa_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Not open to the internet yet

SMTP is running but reachable only from inside our own network while we finish its certificate. Authentication sends your API key, and putting that on the public internet without TLS would hand it to anyone on the path. Use the HTTP API until this page stops saying so.