Platform mail service
Choose a provider, save its settings, check the connection, then deliberately send a test email.
This page is for platform administrators configuring login, customer portal and plan-notification email. Ordinary software licensing integration does not require a mail provider, and mail API keys do not belong in customer applications.
Verify the sender with your provider first
Verify the sender or sending domain with your provider and configure DNS as it requires. The From address must be authorized by that provider. Saving platform settings does not verify the domain for you.
Choose a provider and enter its required fields
| Email service | Prepare |
|---|---|
| SMTP | Provider host, port, username, password, sender and TLS mode. Existing Resend SMTP configurations remain usable. |
| Resend API / Brevo | An API key from that provider and an authorized From address. |
| Postmark | The Server API Token for the selected Postmark server and an authorized From address. |
| Mailgun | An API key, sending domain, From address and the US or EU region hosting that domain. |
Match SMTP implicit TLS or STARTTLS to your provider’s requirements; STARTTLS requires server support for the encrypted upgrade. API providers use HTTPS. File mode is for development diagnostics and does not deliver mail.
Complete setup in this order
- Open Platform management → System settings → Mail service, select a provider and complete its fields. Changing the selection alone does not change the live sending service.
- Choose Save and use this service. The current provider is saved; a blank existing secret is retained. Enter a new secret only to replace it.
- Check the saved mail connection. API checks are read-only and do not deliver email. Sending-only keys may produce a limited check result; continue with a test send rather than treating that as verified success.
- Enter a test mailbox you control and explicitly click Send test email. Check the delivery records and inbox; being queued does not mean the message has arrived.
- If delivery fails, confirm the job status, check the saved connection and inspect the provider dashboard for the specific rejection reason. Check key permissions, domain or region, sender verification, TLS and limits. Save corrections before retrying and avoid duplicate test sends.