Download the PHP package skitlabs/laravel-mailgun-multiple-domains without Composer
On this page you can find all versions of the php package skitlabs/laravel-mailgun-multiple-domains. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download skitlabs/laravel-mailgun-multiple-domains
More information about skitlabs/laravel-mailgun-multiple-domains
Files in skitlabs/laravel-mailgun-multiple-domains
Package laravel-mailgun-multiple-domains
Short Description Multiple sender domains, without modifying calling code
License MIT
Informations about the package laravel-mailgun-multiple-domains
Multiple Mailgun Domains in one Laravel app
Sending email through Mailgun is a breeze, when sending from one domain only.
For any additional domains, the calling code needs to determine which mailer transport to use.
This can be especially annoying when the mailer to use depends on the sender, which is often set inside the mailable.
Using this package, the calling code is no longer concerned with the configured mailers.
Installation
You can install the package via composer:
How it works
This package contains a listener that hooks into the Illuminate\Mail\Events\MessageSending
event, which is dispatched just before sending the e-mail.
It then reconfigures the current Transport
, based on the from
domain in the message. This works for direct and queued messages alike, with no extra configuration!
Thanks to Laravel's auto-discovery (❤), no assembly required!
Requirements
There are a few requirements for this to work;
- PHP 8.0, or 8.1
- Laravel >= 9.0
- Laravel needs to use
symfony/mailer
internally (default)
Older versions
Not using laravel 9 (yet)? Version 2 of this package supports laravel 7 and 8.
Usage
If you've configured mailgun under mg.{domain.tld}
, and your secret works for all domains you are sending from; you're ready to start sending e-mail! 👍
Let's say you're sending a message as [email protected]
. Just before sending the message, this package will set the mailgun domain to: mg.acme.app
.
What if I need to customize my settings, per domain?
Add the sending domains to your mailgun configuration in the key domains
.
If a domain is not specified, it defaults to
mg.{domain.tld}
.
If thesecret
orendpoint
are not configured, these fallback to your configured global defaults.
What if I need to customize how these settings are determined?
If the standard way of resolving sender properties is not suitable for your use-case, create a custom resolver that implements MailGunSenderPropertiesResolver. See the default implementation for inspiration.
Once you have your own concrete implementation, overwrite the default bind in any of your service providers;
What if my mailer has a different name?
Specify the name of your mailer, as the second argument, when instantiating ReconfigureMailGunOnMessageSending
.
Testing
Changelog
Please see CHANGELOG for more information on what has changed recently.
License
The MIT License (MIT). Please see License File for more information.