Send with SMTP
Send from any tool that has SMTP settings, without writing code.
Supabase Auth, WordPress, a CMS, a framework's mailer: if a tool can send through an SMTP server, it can send through Mailmus. Each email goes through the same checks as an API call and shows up in the same logs, analytics and webhooks.
Settings
| Setting | Value |
|---|---|
| Server | smtp.mailmus.app |
| Port | 587 (STARTTLS, recommended), 465 (SSL/TLS) or 2525 (STARTTLS, when your network blocks 587) |
| Username | mailmus |
| Password | a Live secret API key of your project |
The same values, with copy buttons, are on the SMTP page of your project in the dashboard.
- The connection is always encrypted. On 587 and 2525 the server refuses to authenticate before STARTTLS, so your key never travels in clear.
- Test keys are refused: SMTP sends real email. Create a Live secret key under API keys.
- The
Fromaddress must use a verified domain of the project the key belongs to.
Supabase Auth
In your Supabase project, open Authentication, then the SMTP Settings of the emails section, and enable custom SMTP:
- Sender email: an address on your verified domain, for example
auth@yourdomain.com - Sender name: your product's name
- Host:
smtp.mailmus.app - Port:
587 - Username:
mailmus - Password: your Live secret key
Invitations, magic links and password resets then leave through Mailmus.
Node.js (Nodemailer)
import nodemailer from "nodemailer";
const transport = nodemailer.createTransport({
host: "smtp.mailmus.app",
port: 587,
auth: { user: "mailmus", pass: process.env.MAILMUS_SECRET_KEY },
});
await transport.sendMail({
from: "Acme <hello@yourdomain.com>",
to: "recipient@example.com",
subject: "Welcome!",
html: "<h1>Welcome!</h1>",
});What the server answers
| Code | Meaning | What to do |
|---|---|---|
250 | Accepted. The reply carries the email's id, the one shown in your logs. | Nothing. |
451, 454 | Temporary: rate exceeded, a short outage, or the same message still being sent. | Retry later. SMTP clients do it on their own. |
535 | The key is invalid, revoked, a Test key, or the account cannot send. | Check the password. |
550 | The sender's domain is not verified on this project, or the recipient is on your suppression list. | Verify the domain, or check the recipient. |
552 | The message is too large. | Send fewer or smaller attachments. |
554 | Refused for good: the content was refused by the sending policy, your plan's limit is reached, or sending is paused on your account. | Read the reason given in the reply. |
A retry never sends twice: the same message sent again within 24 hours gets the first answer back, with the same id.
Limits
- Up to 150 recipients per message (To, Cc and Bcc together).
- Up to 10 attachments, 8 MB in total.
- Up to 120 messages per minute for each key.
Status
Whether SMTP sending works right now is on the SMTP page of your project and on the status page.