Skip to content
Jooosi
Account
JM Jooosi Mail

Mailgun

Browse documentation
Overview
Contents
On this page
  1. Before you begin
  2. Supported transport and settings
  3. Create the connection
  4. Verify delivery
  5. Webhooks
  6. Troubleshooting

Mailgun supports API, HTTPS API, and SMTP transports. The API schemes require a domain and API key. SMTP requires a username and password. An optional region field is available for the transport when your Mailgun account uses a non-default region.

Before you begin#

Have a provider account and credentials for the transport you chose. Copy credentials from the provider’s own console or account settings; never put secret values in documentation. Check the provider’s documentation for account requirements and sender acceptance.

Supported transport and settings#

  • Transport scheme: mailgun+api (default), mailgun+https, mailgun+smtp.
  • Required settings: mailgun+api or mailgun+https: Mailgun API key (secret) and Mailgun domain. mailgun+smtp: Mailgun SMTP username and SMTP password (secret).
  • Optional settings: Mailgun region is optional. It is available for each scheme and is passed to the transport when provided.

Jooosi Mail marks password, token, key, and private-key fields as secrets in the connection form. Enter only the fields shown for the selected scheme.

Create the connection#

  1. In WordPress admin, open Jooosi Mail → Connections and choose New connection.
  2. Enter a descriptive Connection name and select Mailgun in Profile.
  3. Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
  4. Review the sender, routing, and advanced settings for this connection.
  5. Choose Create connection to save it.

For the shared form workflow, see Connect a provider.

Verify delivery#

Follow Send a test email and send to a mailbox you can check. A test sends a real email. Check the mailbox and Jooosi Mail → Logs for the attempt status. For supported webhooks, see the provider note and Provider webhooks guide.

Webhooks#

Mailgun webhooks are supported. Enable Webhooks under Advanced settings, add a shared Webhook secret, save, and configure the displayed endpoint with Mailgun. The adapter requires that secret and verifies Mailgun’s timestamp/token signature. Use the shared Provider webhooks guide for event setup.

Troubleshooting#

  • For API delivery, check the domain and region along with the API key; for SMTP, use SMTP credentials.
  • If webhook requests are rejected, confirm the shared Webhook secret is the Mailgun signing key expected by your webhook configuration.

Provider reference: https://documentation.mailgun.com/.