Send transactional email from your projects using your organization's ploy.email domain or your own domain.
Ploy can send transactional email for your projects, such as sign-up confirmations, password resets, and receipts. Every organization gets its own sending domain, and you can add your own domains so mail comes from addresses your users recognize.
Request access
Email sending is enabled per organization after a manual review. The review helps keep deliverability high for every organization that sends through Ploy.
- Open the dashboard and go to Email in your organization's sidebar.
- Describe what your projects will send and to whom, for example "account verification and password reset emails for users of our app".
- Submit the request. The page shows Under review until we have looked at it.
Only organization owners and admins can request access. If a request is not approved, the dashboard shows the reason and you can update your use case and request again.
Your ploy.email domain
Once access is approved, your organization gets a fixed sending domain of the
form <name>.ploy.email. Ploy manages its DNS records, so it works right away
without any setup. This domain cannot be removed or renamed.
Custom domains
To send from your own domain, open Email in the dashboard and click Add domain.
Use a subdomain such as mail.example.com rather than your apex domain. It
keeps the reputation of your sending separate from your main domain. Sending
email does not change your existing MX records, so the mail you receive keeps
working.
A custom domain needs these DNS records. The dashboard shows the exact names and values for your domain, each with a copy button:
| Records | Type | Name | Purpose |
|---|---|---|---|
| 3 DKIM records | CNAME | <token>._domainkey.<domain> | Sign your messages so receivers can verify they come from you |
| Bounce MX | MX | bounce.<domain> | Receive bounce notifications for your messages |
| Bounce SPF | TXT | bounce.<domain> | Authorize Ploy to send on behalf of the bounce domain |
| DMARC, optional | TXT | _dmarc.<domain> | Tell receivers how to handle unauthenticated mail; only suggested if your domain has none |
The bounce records live on bounce.<domain>, a subdomain only used for
bounces, so they never conflict with records on the domain itself.
Domains on Ploy DNS
If the domain's DNS is managed by Ploy (added under Domains in the dashboard with Ploy-managed DNS), Ploy adds all of these records for you. The dashboard marks the domain as Records managed by Ploy DNS and there is nothing to copy.
Checking records
DNS changes can take a while to show up. Ploy checks pending domains periodically, and you can click Check now on a domain at any time. The dashboard then shows the status of every record:
- OK: the record is set up correctly.
- Missing: no record was found at that name yet.
- Mismatch: a record exists but has a different value. The dashboard lists the values it found and a hint on how to fix it.
A domain is Verified once its required records are in place. You can remove a custom domain from the dashboard at any time; your projects can then no longer send from it.
Limits
Each project has a daily limit on the number of emails it can send. The current limit is shown on the Email page. If you need a higher limit, contact support and we can raise it.
Bounces and complaints
When a message bounces permanently or a recipient marks it as spam, Ploy adds the address to a suppression list and stops sending to it, which protects your domain's reputation.
If bounce or complaint rates get too high, Ploy can pause sending for the organization. The Email page then explains why sending is paused; contact support to resume it.
How is this guide?
Last updated on