vormkracht10 / laravel-mails
Laravel Mails can collect everything you might want to track about the mails that has been sent by your Laravel app.
Fund package maintenance!
vormkracht10
Installs: 1 615
Dependents: 1
Suggesters: 0
Security: 0
Stars: 7
Watchers: 1
Forks: 3
Open Issues: 2
Requires
- php: ^8.1
- illuminate/contracts: ^10.8.0|^11.22.0
- laravel-notification-channels/discord: ^1.6
- laravel-notification-channels/telegram: ^4.0|5.0
- laravel/helpers: ^1.7.0
- laravel/slack-notification-channel: ^2.5|^3.3.2
- mailgun/mailgun-php: ^4.3
- spatie/laravel-package-tools: ^1.14.0
- wildbit/postmark-php: ^4.0
Requires (Dev)
- larastan/larastan: ^2.9.8
- laravel/pint: ^1.17.0
- nunomaduro/collision: ^7.5.0|^8.4
- orchestra/testbench: ^8.5.0|^9.4.0
- pestphp/pest: ^2.35.1
- pestphp/pest-plugin-laravel: ^2.4.0
- phpstan/extension-installer: ^1.4.2
- phpstan/phpstan-deprecation-rules: ^1.2.0
- phpstan/phpstan-phpunit: ^1.3.11
- phpunit/phpunit: ^10.5.17
This package is auto-updated.
Last update: 2024-11-04 12:59:24 UTC
README
Nice to meet you, we're Vormkracht10
Hi! We are a web development agency from Nijmegen in the Netherlands and we use Laravel for everything: advanced websites with a lot of bells and whitles and big web applications.
Why this package
Email as a protocol is very error prone. Succesfull email delivery is not guaranteed in any way, so it is best to monitor your email sending realtime. Using external services like Postmark email gets better by offering things like logging and delivery feedback, but it still needs your attention and can fail silently but horendously. Therefore we created Laravel Mails that fills in all the gaps.
Using Laravel we create packages to scratch a lot of our own itches, as we get to certain challenges working for our clients and on our projects. One of our problems in our 13 years of web development experience is customers that contact us about emails not getting delivered.
Sometimes this happens because of a bug in code, but often times it's because of things going wrong you can't imagine before hand. If it can fail, it will fail. Using Murphy's law in full extend! And email is one of these types where this happens more than you like.
As we got tired of the situation that a customer needs to call us, we want to know before the customer can notice it and contact us. Therefore we created this package: to log all events happening with our sent emails and to get automatically notified using Discord (or Slack, Telegram) when there are problems on the horizon.
Features
Laravel Mails can collect everything you might want to track about the mails that has been sent by your Laravel app. Common use cases are provided in this package:
- Log all sent emails, attachments and events with only specific attributes
- Works currently for popular email service provider Postmark
- Collect feedback about the delivery status from email providers using webhooks
- Get quickly and automatically notified when email hard/soft bounces or the bouncerate goes too high
- Prune all logged emails periodically to keep the database nice and slim
- Resend logged emails to another recipient
- View all sent emails in the browser using complementary package Filament Mails
Upcoming features
- We're currently in the process of writing mail events support for other popular email service providers like Mailgun, Resend, SendGrid, Amazon SES and Mailtrap.
- Relate emails being send in Laravel directly to Eloquent models, for example the order confirmation email attached to an Order model.
Looking for a UI? We've got your back: Filament Mails
We created a Laravel Filament plugin called Filament Mails to easily view all data collected by this Laravel Mails package.
It can show all information about the emails and events in a beautiful UI:
Installation
First install the package via composer:
composer require vormkracht10/laravel-mails
Then you can publish and run the migrations with:
php artisan vendor:publish --tag="mails-migrations"
php artisan migrate
Add the API key of your email service provider to the config/services.php
file in your Laravel project, currently we only support Postmark:
[
'postmark' => [
'token' => '...',
]
]
When done, run this command with the slug of your service provider:
php artisan mail:webhooks [service] // where [service] is your provider, e.g. postmark
And for changing the configuration you can publish the config file with:
php artisan vendor:publish --tag="mails-config"
This is the contents of the published config file:
return [ // Eloquent model to use for sent emails 'models' => [ 'mail' => Mail::class, 'event' => MailEvent::class, 'attachment' => MailAttachment::class, ], // Table names for saving sent emails and polymorphic relations to database 'database' => [ 'tables' => [ 'mails' => 'mails', 'attachments' => 'mail_attachments', 'events' => 'mail_events', 'polymorph' => 'mailables', ], 'pruning' => [ 'enabled' => true, 'after' => 30, // days ], ], 'headers' => [ 'uuid' => 'X-Mails-UUID', 'associate' => 'X-Mails-Associated-Models', ], 'webhooks' => [ 'routes' => [ 'prefix' => 'webhooks/mails', ], 'queue' => env('MAILS_QUEUE_WEBHOOKS', false), ], // Logging mails 'logging' => [ // Enable logging of all sent mails to database 'enabled' => env('MAILS_LOGGING_ENABLED', true), // Specify attributes to log in database 'attributes' => [ 'subject', 'from', 'to', 'reply_to', 'cc', 'bcc', 'html', 'text', ], // Encrypt all attributes saved to database 'encrypted' => env('MAILS_ENCRYPTED', true), // Track following events using webhooks from email provider 'tracking' => [ 'bounces' => true, 'clicks' => true, 'complaints' => true, 'deliveries' => true, 'opens' => true, ], // Enable saving mail attachments to disk 'attachments' => [ 'enabled' => env('MAILS_LOGGING_ATTACHMENTS_ENABLED', true), 'disk' => env('FILESYSTEM_DISK', 'local'), 'root' => 'mails/attachments', ], ], // Notifications for important mail events 'notifications' => [ 'mail' => [ 'to' => ['test@example.com'], ], 'discord' => [ // 'to' => ['1234567890'], ], 'slack' => [ // 'to' => ['https://hooks.slack.com/services/...'], ], 'telegram' => [ // 'to' => ['1234567890'], ], ], 'events' => [ 'soft_bounced' => [ 'notify' => ['mail'], ], 'hard_bounced' => [ 'notify' => ['mail'], ], 'bouncerate' => [ 'notify' => [], 'retain' => 30, // days 'treshold' => 1, // % ], 'deliveryrate' => [ 'treshold' => 99, ], 'complained' => [ // ], 'unsent' => [ // ], ], ];
Usage
Logging
When you send emails within Laravel using the Mail
Facade or using a Mailable
, Laravel Mails will log the email sending and all events that are incoming from your email service provider.
Relate emails to Eloquent models
...
Resend a logged email
...
Get notified of important events such as bounces, high bounce rate or spam complaints
...
Prune logged emails
...
Events
Depending on the mail provider, we send these events comming in from the webhooks of the email service provider.
\Vormkracht10\Mails\Events\MailAccepted::class, \Vormkracht10\Mails\Events\MailClicked::class, \Vormkracht10\Mails\Events\MailComplained::class, \Vormkracht10\Mails\Events\MailDelivered::class, \Vormkracht10\Mails\Events\MailEvent::class, \Vormkracht10\Mails\Events\MailEventLogged::class, \Vormkracht10\Mails\Events\MailHardBounced::class, \Vormkracht10\Mails\Events\MailOpened::class, \Vormkracht10\Mails\Events\MailResent::class, \Vormkracht10\Mails\Events\MailSoftBounced::class, \Vormkracht10\Mails\Events\MailUnsubscribed::class,
Testing
composer test
Changelog
Please see CHANGELOG for more information on what has changed recently.
Contributing
Please see CONTRIBUTING for details.
Security Vulnerabilities
Please review our security policy on how to report security vulnerabilities.
Credits
License
The MIT License (MIT). Please see License File for more information.