Mailgun

Use Mailgun when you want Drip Drop to send email through a domain-based email delivery provider instead of a personal mailbox. Mailgun can handle outbound sending, event webhooks, engagement tracking, and inbound routing for replies.

Note
Mailgun is different from Gmail and Outlook. It is a domain-based email service provider, not a mailbox OAuth login flow.
  • You want application-style or domain-based email sending instead of sending from a mailbox account.
  • You want provider-side delivery, failure, complaint, unsubscribe, open, and click events in Drip Drop.
  • You want reply handling through Mailgun inbound routes on a parse domain instead of mailbox polling or OAuth inbox subscriptions.
  1. Confirm you have Mailgun account access and permission to work with domains, webhooks, and routes.
  2. Choose the Mailgun Sender Domain Drip Drop should send from.
  3. Decide whether you need only outbound sending, or also webhooks, Track Opens/Track Clicks, and inbound routing.
  4. If you want inbound replies, plan the parse subdomain or hostname that should receive those messages.
  1. Open Dashboard → Admin → Integrations.
  2. Click New Integration and choose Mailgun.
  3. Enter the Mailgun API key.
  4. Enter the Sender Domain Drip Drop should use for outbound mail.
  5. Save the provider, then open the Webhook Settings area if you want Events or Inbound Replies.

The Mailgun Provider Form can expose the Sender Domain Field, Webhook Configuration, Tracking Toggles, Signed Webhook Controls, and Inbound Parse settings after the API key is in place.

Mailgun sending depends on the sender domain saved in the provider. This is different from mailbox-based providers, where the connected mailbox is the sender identity.

  • Use the exact Mailgun Domain that should send outbound email from Drip Drop.
  • Outbound sending can work even if inbound routing is not configured yet.
  • If the wrong domain is saved, sending and webhook setup may target the wrong Mailgun configuration.
  • The current Mailgun integration needs a valid Mailgun API key and access to the selected domain.
  • Admins should expect webhook configuration to be domain-specific, not account-global in the same way as SendGrid event webhooks.

Helpful Mailgun references: Mailgun domains, Mailgun webhooks, and Mailgun routes.

Mailgun webhooks send delivery and engagement events from the sender domain back to Drip Drop. This is separate from inbound routes.

  • Drip Drop can use delivered, permanent fail, temporary fail, complained, and unsubscribed events from Mailgun.
  • Opened Events only appear when Track Opens is enabled.
  • Clicked Events only appear when Track Clicks is enabled.
  • Drip Drop tries to add its webhook URL while preserving existing Mailgun webhook URLs where possible.
  • Mailgun supports a limited number of URLs per event type, so replacement behavior may matter if a domain already has several webhook destinations configured.

Track Opens and Track Clicks are Mailgun-backed event controls that determine whether Mailgun sends opened and clicked events to Drip Drop.

  • If Track Opens is off, Drip Drop should not expect Mailgun open events.
  • If Track Clicks is off, Drip Drop should not expect Mailgun click events.
  • If Drip Drop also exposes internal link or open tracking, keep that explanation separate from Mailgun webhook events.

Mailgun can sign webhook payloads with a token, timestamp, and signature. When Signed Webhooks are enabled in Drip Drop, admins may need the Mailgun webhook signing key saved in the provider.

  • The Signing Key is separate from the main Mailgun API key.
  • If Signed Webhooks are enabled but the signing key is missing, webhook verification can fail even though the webhook URL itself is correct.
  • Verification state should be described from the admin point of view: Webhook Saved, Key Saved, and Events arriving successfully.

Mailgun inbound handling is route-based. Instead of mailbox polling or OAuth subscriptions, Mailgun receives messages on a parse hostname and forwards them to Drip Drop.

  • Enable Inbound Parse in the provider form if you want Mailgun-hosted reply handling.
  • Set the Inbound Parse Domain to the Hostname or Subdomain that should receive reply emails.
  • Drip Drop can attempt to create or update the Mailgun route automatically, but some accounts may still need manual route or DNS work in Mailgun.
  • For reply matching, Drip Drop first tries the In-Reply-To tracking header and then falls back to the most recent outbound message to the sender if needed.
  1. Open the selected domain in Mailgun if Drip Drop cannot auto-configure webhooks.
  2. Add or verify the event webhook URLs for the event types Drip Drop needs.
  3. Enable Opened and Clicked Events only if you want those engagement events in Drip Drop.
  4. If signed webhook verification is required, copy the webhook signing key into Drip Drop.
  5. Open Mailgun routes or inbound routing settings if you need reply handling.
  6. Configure the Inbound route expression and forward action for the parse hostname, along with any required MX or DNS records for that hostname.
  • After webhook traffic starts arriving, Drip Drop can attach delivery and engagement events to outbound messages.
  • Inbound replies can appear even though they come through Mailgun routes rather than the event webhook endpoint.
  • Verification or configured state may lag until the provider has received real webhook traffic or the admin has completed the required Mailgun-side settings.
API key, domain, and auth problems
  • If setup fails immediately, confirm the Mailgun API key is valid and has access to the intended account/domain context.
  • If sending fails, confirm the sender domain is set and matches the Mailgun domain you intend to use.
  • If the wrong domain was entered, update it before debugging webhook or route behavior.
Webhook and verification problems
  • If not all events are arriving, check whether every needed event type is configured on the Mailgun domain.
  • If another set of webhook URLs is already present, review how many URLs are already attached for that event type.
  • If signed validation fails, confirm the webhook signing key is saved and that Mailgun is sending the expected token, timestamp, and signature fields.
Tracking problems
  • If opens are missing, confirm Track Opens is enabled and that you are expecting Mailgun event tracking rather than only internal tracking.
  • If clicks are missing, confirm Track Clicks is enabled and that the messages are using links Mailgun can track.
Inbound routing problems
  • If replies never appear, verify the parse domain is configured correctly and that MX or DNS routing for that hostname points to Mailgun.
  • If the route exists but forwards to the wrong URL, update the forward action to the Drip Drop inbound endpoint.
  • If replies arrive but do not match the expected outbound message, test again with a fresh send so the tracking headers are present.
  • See Integrations for the shared provider setup flow and provider management basics.
  • Compare SendGrid if you want a similar ESP-based workflow with different provider-side controls.
  • Compare Gmail or Outlook if you need a mailbox-style sender instead of a domain-based ESP.