Package Data | |
---|---|
Maintainer Username: | YOzaz |
Maintainer Contact: | yozaz.mandac@gmail.com (Marijus Planciunas) |
Package Create Date: | 2015-03-30 |
Package Last Update: | 2017-03-01 |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-11-29 15:02:44 |
Package Statistics | |
---|---|
Total Downloads: | 66,840 |
Monthly Downloads: | 532 |
Daily Downloads: | 49 |
Total Stars: | 24 |
Total Watchers: | 2 |
Total Forks: | 3 |
Total Open Issues: | 0 |
This package was deprecated, as starting from Laravel 5.0 and above, original Mail class automatically theoretically reconnects on every message. See commit here: [Force reconnection to fix mailing on daemon queues] (https://github.com/laravel/framework/commit/af8eb1face000f82e5c85e6eb822075fc313cbb9).
However, it looks like just calling stop
on a transport doesn't do full reset, therefore may throw an error - see discussion here:
https://github.com/laravel/framework/issues/4573#issuecomment-211889196
Package, which tries to solve long-term daemon worker issue. For reference:
Compatible with Laravel 4th and 5th versions.
Begin by installing this package through Composer. Edit your project's composer.json
file to require yozaz/laravel-swiftmailer
.
"require": {
"yozaz/laravel-swiftmailer": "~4.0"
}
Next, update Composer from the Terminal:
composer update
Once this operation completes, the next step is to add the service provider. Open app/config/app.php
(or config/app.php
), and add a new item to the providers array.
'YOzaz\LaravelSwiftmailer\ServiceProvider',
The final step is to replace Laravel's native Mailer Facade with the one, provided in a package. Open app/config/app.php
(or config/app.php
), and replace "Mail" alias with:
'Mail' => 'YOzaz\LaravelSwiftmailer\Facade',
That's it! You're all set to go.
This package works in two possible error-safe modes: sends STOP command after every email is sent, and/or sends RESET/STOP+START commands before every email is sent. As a default, both modes are activated (so called "aggressive" mode). Such approach ensures SMTP connection is closed to avoid timeouts and broken pipes, or maintains it active for whole application living cycle. This is extremely important for long-living applications. E.g. when emails are sent through Beanstalkd + Supervisor + Laravel Queue Daemon Worker architecture, Laravel application never quits - therefore SMTP connection is kept active and timeouts after some time. Stopping, resetting and/or restarting SMTP connection automaticaly solves this problem in general.
N.B. While auto-reset feature is great, sometimes it's not a preferred behaviour. Be sure to check your SMTP server configuration before using this package.
Package is built in a way, that nothing special needs to be done. It's basically a wrapper, so all Mailer::send()
and similar functions will work out of the box.
Package starts, stops or resets SMTP adapter every time when email is sent. You can manipulate this through special helper functions:
// disable auto reset
Mailer::disableAutoReset();
// enable it back
Mailer::enableAutoReset();
// Set my status
Mailer::setAutoReset(true);
// check if auto-reset is enabled
if ( Mailer::autoResetEnabled() ) { ...
You can switch between STOP or RESET behaviours using native constants as a flag:
// send only STOP after every email
Mailer::setModeStop();
// send only RESET before every email
Mailer::setModeReset();
// aggressive mode - STOP and RESET (default)
Mailer::setModeBoth();
It is possible to stop or reset SMTP adapter explicitly.
Mailer::reset()->send(...);
Mailer::stop();
By default, failed emails will throw an Exception
. If that's unexpected behaviour - e.g. because you don't need retry sending it - you can turn this mode on.
Mailer::setSilent(true);
N.B. Even if email will fail, before carrying over an Exception
, package will try sending STOP command anyway (if such mode is enabled).
Package has separate IoC binding. N.B. This package does not overwrite 'mailer' IoC binding in Laravel for legacy purposes.
var $mailer = App::make('laravel-swiftmailer.mailer');
If you prefer object initialization against Facades, you can instantiate Mailer
class by yourself, with additional parameters if required. Package will try to instantiate required objects automatically as defaults.
var $mailer = new \YOzaz\LaravelSwiftmailer\Mailer();
Optinally, if you have custom wrapper for Laravel's Mailer, or want to manipulate with auto-reset functionality, you can pass additional parameters to IoC binding or class instantiation. Take a look at class constructor for details.
var $my_custom_mailer = App::make('mailer');
// pass custom mailer and disable auto-reset
var $mailer = new \YOzaz\LaravelSwiftmailer\Mailer( $my_custom_mailer, false );
To set custom mailer instance, call this method:
Mailer::setMailer( $my_custom_mailer );
All credits go to xdecock, author of Swift Mailer, for providing ready-made solution implemented in this package.
Laravel-SwiftMailer package is open-sourced software licensed under the MIT license.