Send email from Laravel
Laravel Mail is the canonical interface. Providers with a maintained transport beat raw SDK use.
Queues and Mailables are the standard pattern. Most providers ship a Symfony Mailer transport that Laravel composes.
Send patterns
- Mailable classes with markdown or blade templates.
- Queueable Mailables for async sends.
- Notification channels for transactional flows.
- Webhook controllers verifying provider signatures.
Common mistakes
- Forgetting ShouldQueue on Mailables in production.
- Mailtrap-style local config left enabled in staging.
- Webhook signature checks skipped because the route is unauthenticated.
provider picks for Laravel
- 01
Postmark
TransactionalMaintained Laravel transport.
100/mo developer plan · $15/mo for 10,000 emails - 02
Mailgun
TransactionalFirst-class Laravel transport.
100/day permanent free plan · $15/mo for 10,000 emails (Basic) - 03
SendGrid
Transactional MarketingStable transport and queue compatibility.
60-day free trial only (permanent free tier was removed May 2025) · $19.95/mo for 50,000 emails - 04
Amazon SES
TransactionalNative SES driver in Laravel.
Up to $200 in AWS Free Tier credits for new accounts · $0.10 per 1,000 emails
reading this as developers picking email infrastructure
The question here is which one a backend engineer would rather operate. That means SDK depth in the language already in use, whether a retry can safely be replayed, how much the event log tells you when a customer says the email never arrived, and whether the pricing curve stays sane as volume grows.
Applied to sending email from Laravel, that means weighing developer experience, SDK breadth, idempotency keys, and operating track record ahead of the rest, against password resets, receipts, and magic links shipped from application code.