Weave Code
Laravel Mailbox Laravel Package
beyondcode/laravel-mailbox
Laravel Mailbox lets your Laravel app catch and process incoming email. Define mailboxes with fluent rules, handle messages via webhook drivers like Mailgun and Postmark, store attachments, and reply, turning inbound email into application logic.
Handle incoming emails in your Laravel application.
Frequently asked questions about Laravel Mailbox
- How do I handle incoming email in Laravel with Laravel Mailbox?
- Laravel Mailbox lets your Laravel app receive inbound email through webhook drivers such as Mailgun, Postmark, and SendGrid, or an IMAP poller. The package registers an endpoint, parses the incoming message, and dispatches it to a mailbox class you define. You implement matches() to decide which mailbox owns the message and handle() for your application logic. It fits use cases like email-to-ticket, email-to-comment, shared inboxes, and inbound lead capture.
- How do I install and configure beyondcode/laravel-mailbox?
- Install it with composer require beyondcode/laravel-mailbox, publish the package config, and configure the webhook URL or provider credentials for your inbound email service. Generate mailbox classes with php artisan make-mailbox, then implement matches() and handle(). Most integration work is product logic such as routing, deduplication, persistence, and threading rather than protocol plumbing. For 6.0.0, confirm the Laravel and PHP constraints before upgrading an existing integration.
- Which Laravel and PHP versions does Laravel Mailbox 6.0.0 support?
- The 6.0.0 release notes state Laravel 13 compatibility, but the exact minimum Laravel and PHP versions should be confirmed from the package composer.json and release diff. The major version bump from 5.0.2 likely raises the framework floor even if breaking changes are not spelled out. Treat Laravel upgrades as gated on package compatibility and review the diff before upgrading. There is no formal LTS commitment.
- Which inbound email providers does Laravel Mailbox support?
- The package supports webhook drivers including Mailgun, Postmark, and SendGrid, plus an IMAP poller for mailbox polling. Correctness depends on the provider's payload format and webhook behavior, so provider format drift or throttling can become package-adjacent incidents. Choose a provider whose inbound parsing and retry behavior match your operational needs. The package is an ingest adapter with routing, not a general-purpose MTA.
- How do I create a mailbox class and route incoming messages?
- Run php artisan make-mailbox to generate a mailbox class, then implement matches() to determine whether that mailbox should handle a given message. Put your application behavior in handle(), such as creating tickets, comments, leads, or other records. The package parses the inbound provider payload and dispatches to the matching mailbox. Fluent rules and handler-per-intent designs align well with Laravel conventions.
- Can Laravel Mailbox store attachments and send replies?
- Yes. Laravel Mailbox exposes parsed message data and attachment access so you can store attachments through Laravel's storage facades and reply to messages from your handler logic. You should still enforce attachment size limits and sanitize HTML because email content is attacker-controlled input. Persistence, threading, and reply policies remain your application's responsibility. The package handles parsing and routing, not full inbox platform behavior.
- How do I prevent duplicate inbound email processing in Laravel Mailbox?
- Inbound providers retry webhook deliveries on non-2xx responses, so without explicit deduplication you can process the same email more than once. Track provider message IDs or a stable message hash and enforce uniqueness with a database constraint before running side effects. Queue processing can also help absorb retries and provider throttling. Laravel Mailbox mitigates parsing work but does not remove the need for idempotent handlers.
- How do I secure the Laravel Mailbox webhook endpoint in production?
- The webhook endpoint is publicly reachable, so explicitly configure signature verification, IP allowlisting where supported, payload size limits, and HTML sanitization. Treat every inbound email as attacker-controlled input, including headers, bodies, inline images, and attachments. Monitor provider signature scheme changes and throttling because they can affect delivery. Keep the endpoint behind HTTPS and avoid running expensive work synchronously.
- How do I test Laravel Mailbox handlers?
- Mailbox classes are ordinary application classes, so unit test matches() and handle() directly with representative parsed messages. Use Laravel's fakes for queues, storage, and mail where your handlers touch those services, and test provider payload edge cases such as MIME multipart, encodings, malformed headers, and large attachments. Keep parsing expectations realistic because the package mitigates but does not eliminate MIME edge cases. Integration tests should cover webhook signature verification and duplicate delivery.
- Is beyondcode/laravel-mailbox maintained and suitable for production?
- It is a niche utility package with roughly 1.1k stars and a small maintainer base, but it shows recent activity and community-driven Laravel 13 work. There is no enterprise SLA or formal LTS commitment, so treat it as a targeted dependency rather than a foundation dependency. Plan for a gap between future Laravel majors and package support, and review major version diffs before upgrading. For production, pair it with idempotency, security controls, and monitoring.
Weaver
How can I help you explore Laravel packages today?