Published 1 week ago by deansatch
For years when building websites with or without laravel I have been using smtp for sending mail. Generally I would add a mail settings page in the cms where the user can set their email, password, port etc...
This has worked fine so far apart from occasions when they change their email password and forget to reflect that within their site which can cause serious nightmares for the ones that rely on the emails for their business to function. Also more recently I’ve noticed gmail blocking them
What are people’s best solutions for sending email from sites, baring in mind that some sites may be one man bands on a tight budget and some might need their site to send 100s of emails a day, or even 100s per minute
I don’t mean queues...just the outgoing server setup and avoiding failed jobs due to password changes or email downtime (a fall back second address could be another subject)
@deansatch I use a mixture depending on the client but Mailgun and Postmark are two I use a lot.
Mailgun has 10k free per month and it's dirt cheap after that as well. Postmark is good for deliverability and support. Both work great in Laravel using the API (I don't use SMTP these days. Lots of noise).
@deansatch Basically, you add a new subdomain to send the mail. Some domains have multiple (mail1. mail2. mail3. etc). I use something like mail. and then add the required DNS entries to that subdomain. This includes SPF, A, MX, and CNAME for everything relating to email tracking and sending.
You would then set the from address as [email protected] and add reply-to etc. You can route inbound emails but not really had to do that before.