Ackuna relay settings
- Host
smtp.ackuna.com
- Port
587
- Security
STARTTLS (not SSL/TLS on connect)
- Authentication
Yes, PLAIN or LOGIN
- Username
YOUR_SMTP_USERNAME (starts with smtp_)
- Password
YOUR_SMTP_PASSWORD (starts with sc_, shown once)
Before you start
You need three things from Ackuna. Each takes a few minutes, except the review in step 2.
- An Ackuna account. Create one for free; no card is needed.
- A verified sending domain. Add the domain your app sends from (for example
yourdomain.com) under SMTP Relay, Domains in the console and publish the SPF, DKIM and DMARC records it shows you. The console checks them for you. A new sending domain is also reviewed by our team before it can send; that is not instant, and until it is approved the relay answers 452. - An SMTP credential for that domain. Under SMTP Relay, Credentials, create one for the verified domain. You get a username (
smtp_…) and a password (sc_…). The password is shown once, so paste it into Ghost straight away; if you lose it, rotate the credential.
The From address in Ghost must be on exactly that domain. A credential for yourdomain.com can send as [email protected], but not from a subdomain such as mail.yourdomain.com or from another domain.
The settings
Ghost reads its mail settings from the mail block of config.production.json in the Ghost install directory. Replace that block with this one:
"mail": {
"transport": "SMTP",
"from": "'Your Site' <[email protected]>",
"options": {
"host": "smtp.ackuna.com",
"port": 587,
"secure": false,
"requireTLS": true,
"auth": {
"user": "YOUR_SMTP_USERNAME",
"pass": "YOUR_SMTP_PASSWORD"
}
}
}
secure: false means "no TLS on connect", which is right for a port without implicit TLS. Ghost's docs describe the pair: with requireTLS: true the mailer upgrades the connection with STARTTLS and fails the send if the upgrade does not succeed, instead of carrying on unencrypted. Do not add a "service" key: Ghost warns that service presets are applied after your own options and would replace the host and port.
Ghost uses mail.from as the default sender of every email, so it must be an address on your verified domain.
Environment variables instead
In Docker, or wherever you prefer environment variables, Ghost maps nested settings with two underscores:
mail__transport=SMTP
mail__from="'Your Site' <[email protected]>"
mail__options__host=smtp.ackuna.com
mail__options__port=587
mail__options__secure=false
mail__options__requireTLS=true
mail__options__auth__user=YOUR_SMTP_USERNAME
mail__options__auth__pass=YOUR_SMTP_PASSWORD
Send a test email
Run ghost restart in the install directory (or restart the container) so Ghost reads the new settings. Then do what Ghost's docs suggest and send a test invite: in Ghost Admin, invite a staff user at an address you can read. The message also appears under SMTP Relay, Messages in the Ackuna console.
Common errors
Authentication failed (535)
The username or password is wrong, the credential was revoked, or its domain is no longer active. Copy both values again from the console, with no spaces around them. If you no longer have the password, rotate the credential and paste the new one.
TLS handshake error, "wrong version number" or a connection that hangs
The app is trying SSL/TLS on connect, which the relay does not offer. Use port 587 with STARTTLS: the connection starts in plain text and is upgraded before the login. If the connection times out instead, check that your host or firewall allows outgoing connections to port 587; some cloud providers block it on new servers until you ask them to lift the block.
Sender rejected (550)
The From address is not on the domain the credential was created for. Set the From address in Ghost to an address on that exact domain. The same code is used for a recipient on your suppression list, because an earlier message to them bounced or was marked as spam.
Temporarily rejected (452)
Either you have reached your daily or monthly limit, or the sending domain is still waiting for review. Both are temporary: a mail server retries later, and the console shows your usage. A message with more than 10 recipients is also refused with 452, and one over 10 MB with 552.
Mail that is accepted but lands in spam usually points at DNS, not SMTP. Run the Email DNS check on your domain, or the SPF, DKIM and DMARC checkers one by one.
Limits
- The Free plan includes 3,000 relay emails a month and 100 a day, 1 SMTP credential and 1 sending domain. Paid plans and their limits are on the pricing page.
- New accounts start on lower limits until Ackuna has reviewed them: at most 20 Agent Mail, 200 SMTP relay and 500 newsletter emails a day, whatever the plan allows. After the review the plan limits above apply.
- Each new sending domain is reviewed before it can send.
- One message can have up to 10 recipients and be up to 10 MB.
- While we deploy an update, port 587 stays open and the relay holds the mail it accepts, then sends it when the update is done. A login it cannot check during that time gets a temporary
451; a retry goes through once the update is done.
FAQ
Ghost SMTP questions
Does this send my Ghost newsletters too?
No. This mail configuration covers Ghost's transactional email: invitations, password resets, member sign-ups and login links. Ghost sends newsletters through a separate bulk email setup, which its docs say requires Mailgun.
Should secure be true?
Not on port 587. secure: true means TLS on connect, which the Ackuna relay does not offer. Keep secure: false with requireTLS: true.
Ghost runs on a DigitalOcean Droplet and the connection times out. Why?
Ghost's docs note that DigitalOcean blocks outgoing SMTP on ports 25, 465 and 587 on Droplets by default. The Ackuna relay listens only on 587, so it cannot be reached from a Droplet until DigitalOcean lifts that block for your account.