Mailgun notifications
Before you start
- Verify a sending domain in Mailgun and configure its required DNS records.
- Create a sending API key authorized for that domain, and select the US or EU region where the domain resides.
- Enter the sending domain, a sender email address and one recipient. Sandbox domains have additional recipient restrictions.
Configuration
| Field | Required | Default |
|---|---|---|
| Sending API key | Yes | — |
| Sending domain | Yes | — |
| Region | Yes | US |
| From email | Yes | — |
| To email | Yes | — |
Test and enable
- In CertOne, add a notification target and choose this channel.
- Fill in the configuration and send a test message.
- Check that the message arrived at the intended destination, then save the target.
- Select the saved target in the settings for the notification events you need.
A successful API response means the service accepted the request. It does not prove that the final client or mailbox received it. If a request times out, delivery may already have occurred; check the destination before retrying.
Email targets send UTF-8 plain text and escaped HTML. Sender verification, account approval, quotas, suppression lists and mailbox filtering are controlled by your email provider. Only one sender and one recipient address per target are supported.
Troubleshooting
- Use a sending API key authorized for this domain and choose its region. Verify your sending domain first. API acceptance does not guarantee inbox delivery.
- Check token permissions, account quota, destination ID and server reachability.
- Sensitive credentials are not included in returned error messages.