Skip to content

Documentation

Send Strapi email through Mailtruss.

Strapi's email plugin uses Nodemailer, so the relay's SMTP settings are all it needs.

Before you start

You need a verified sending domain (see Domains) and an API key (under API keys in the dashboard; it is shown once). For SMTP the key is the password, and a sending-only key is enough. Keep the key in an environment variable on your server, never in code that runs in a browser or an app.

Install the provider

Strapi's email plugin sends through a provider. The Nodemailer provider speaks SMTP.

Terminal
npm install @strapi/provider-email-nodemailer

The plugin configuration

Set the relay as the SMTP server. The API key is the password and any username works. The default from address must be on a verified domain.

config/plugins.ts
export default ({ env }) => ({
email: {
config: {
provider: "nodemailer",
providerOptions: {
host: "smtp.mailtruss.com",
port: 587,
auth: { user: "mailtruss", pass: env("MAILTRUSS_API_KEY") },
},
settings: {
defaultFrom: "Acme <hello@yourdomain.com>",
defaultReplyTo: "hello@yourdomain.com",
},
},
},
});

Try it without sending real mail

Strapi's admin panel has a test button in the email settings. You can also send from code with the plugin's service.

In a controller or script
await strapi.plugin("email").service("email").send({
to: "delivered@mailtruss.test", subject: "Test", text: "Hello from Strapi",
});

See what happened

Open the message under Emails in the dashboard: it shows the recorded timeline, what each event proves, and a diagnosis if something went wrong. Mail sent over SMTP appears there like any other message. To be told as it happens, add a webhook.

If it fails

The relay answers with a reply code:

  • 535: the API key is wrong or revoked. Fix the password.
  • 550: refused for good (unverified domain, suppressed recipient, invalid message). Do not retry; the reply says why.
  • 552: too large, or the monthly limit is reached.
  • 451 or 452: temporary (rate limit, daily limit, or a brief problem on our side). Retry later; mail servers do this automatically.

Problems that happen after a message is accepted (bounces, complaints) are explained under delivery errors.

Other guides

Last updated

Something wrong or unclear on this page?

Report an issue