Weave Code
Mailgun Mailer Laravel Package
symfony/mailgun-mailer
Symfony Mailer integration for Mailgun. Configure via DSN and send mail over SMTP (mailgun+smtp), HTTP (mailgun+https), or API (mailgun+api) using your Mailgun API key, sending domain, and optional region.
Symfony Mailgun Mailer provides seamless Mailgun integration for Symfony Mailer, letting you send transactional email through Mailgun with just a DSN. It supports SMTP, HTTPS, and API transports, with optional region selection for EU or US endpoints.
- Configure via a single
MAILER_DSNenvironment variable - Three transports:
mailgun+smtp,mailgun+https, andmailgun+api - Optional
regionparameter for Mailgun's EU/US infrastructure - Native integration with Symfony Mailer's
TransportInterface - Maintained as part of the official Symfony monorepo
Frequently asked questions about Mailgun Mailer
- How do I install and configure symfony/mailgun-mailer?
- Install it with Composer as symfony/mailgun-mailer, then configure Symfony Mailer using a Mailgun DSN. The DSN can use mailgun+smtp, mailgun+https, or mailgun+api with your API key, sending domain, and optional region. No Laravel-specific configuration is provided because this is a Symfony Mailer transport bridge.
- Is symfony/mailgun-mailer compatible with Laravel?
- No, it is not a drop-in solution for Laravel's Illuminate Mail stack. Laravel's mail integration depends on a different symfony/mailer version line, so this package conflicts with Laravel's constraints. Laravel applications should use Laravel's native MAIL_MAILER=mailgun driver instead.
- What DSN schemes does symfony/mailgun-mailer support?
- The package supports mailgun+smtp for SMTP delivery, mailgun+https for HTTP delivery, and mailgun+api for Mailgun's API service. You provide credentials and the sending domain in the DSN, with an optional region parameter. This makes it suitable for Symfony Mailer projects that need Mailgun transport options.
- Does symfony/mailgun-mailer support Mailgun regions?
- Yes, the DSN configuration includes an optional REGION query parameter. You can set region=REGION alongside your Mailgun API key and sending domain. This allows Symfony Mailer to target the appropriate Mailgun regional endpoint.
- What changed in symfony/mailgun-mailer 8.1.6 for webhook security?
- Version 8.1.6 strengthens webhook signature validation by rejecting non-string signature fields instead of throwing a TypeError. It also rejects stale webhook timestamps for Mailgun, SendGrid, and Vonage. This reduces malformed-payload and replay-attack exposure, but it is a behavioral change for webhook senders.
- Do I need symfony/mailgun-mailer to send Mailgun email from Laravel?
- No. Laravel's native Mailgun mail driver is the supported path for Laravel applications and integrates with Illuminate Mail, queues, and notifications. This package is a Symfony Mailer bridge and does not bridge Laravel's mail abstractions. Forcing it into Laravel adds version conflicts and maintenance burden.
- Is upgrading to symfony/mailgun-mailer 8.1.6 safe for Symfony applications?
- For Symfony applications already using the package, 8.1.6 is described as a low-risk security-focused patch with no indicated new configuration requirements or public API changes. You should still test webhook validation with stale timestamps and malformed signature fields. Monitor webhook 4xx rates and delivery retries after rollout.
- What are alternatives to symfony/mailgun-mailer for Laravel projects?
- Laravel applications should use Laravel's built-in Mailgun mail driver rather than this Symfony bridge. Symfony-based services that specifically need Symfony Mailer can use symfony/mailgun-mailer. Custom forks or adapters for Laravel should be treated as unsupported custom code.
- Why are my Mailgun webhooks rejected after upgrading symfony/mailgun-mailer?
- The stricter validation in 8.1.6 rejects stale webhook timestamps and non-string signature fields. Check that webhook-receiving hosts use NTP or equivalent clock synchronization and account for delayed delivery or queue backlogs. Also verify that senders provide string signature fields and review 4xx alerting and retry behavior.
- Does symfony/mailgun-mailer support Symfony 7.4 and Symfony 8.0?
- Yes, the package constraints cover Symfony 7.4 and 8.0, and version 8.1.6 is a patch upgrade for existing Symfony Mailer deployments. The release notes do not indicate new PHP or Symfony platform requirements beyond existing constraints. This does not change Laravel compatibility, which remains blocked by the symfony/mailer version conflict.
Weaver
How can I help you explore Laravel packages today?