Documentation
Send Auth0 emails through Mailtruss.
Auth0 can send its verification and password emails through any SMTP server. Enter five values.
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.
Where to enter it
In the Auth0 Dashboard, open the email provider settings (under Branding, Email Provider, as of this writing) and choose to use your own provider, then an SMTP server. Auth0 moves menu names occasionally: its documentation page for configuring an SMTP server shows the current path.
The values
Use these in the SMTP fields. The API key is the password, and any username works.
The from address
The from address must be on a domain you have verified in Mailtruss. Mail from any other domain is refused with a 550, and Auth0's test will show that error. Verify the domain first: see [Domains](/docs/domains).
Templates
Auth0 keeps its own email templates (welcome, verification, password change). Only delivery moves to Mailtruss: the content and the triggers stay in Auth0.
Try it without sending real mail
Auth0's email provider screen has a button to send a test email. It sends through the relay and the message appears under Emails in the Mailtruss dashboard within a few seconds. If it fails, the error is the relay's reply code.
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.451or452: 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.