- Customer Success
Zipbooks Switched From Mandrill To Mailgun Using Laravel
With Mandrill announcing that the Heroku add-on is no longer going to be available after April 25th, many developers are looking for an alternative solution that they can continue using from the Heroku Marketplace.
Mailgun offers several different packaged add-ons that you can select from based on the volume of e-mail you send on a monthly basis. You can upgrade to a larger plan at any time or if you need something specific to your needs, a program can be custom tailored for you.
The free starter plan can be easily installed on your application by running the following Heroku CLI command from your application’s folder:
heroku addons:create mailgun:starter
The starter plan includes 400 messages per day and is perfect to get started with.
You can open the Mailgun dashboard by running the following command:
heroku addons:open mailgun
When Mailgun is provisioned, a sandbox domain is automatically configured that can be used for testing Mailgun without setting up a custom domain. The sandbox domain is limited to 300 messages a day and is not optimized for deliverability.
For production use, setting up a custom domain is the best option. In the Mailgun dashboard, click the Add Custom Domain button.
After setting up your domain, you’ll be given a set of DNS records that need to be added to your DNS provider before your domain can be used. Setting up these records enable SPF, DKIM, incoming messages, and message tracking.
Once the records are in place, you can wait for automatic validation to occur or click the Check DNS Records Now button to force an immediate check.
At this point, you’re ready to update your application to use the Mailgun addon. If you’re using a library that uses SMTP, you can update your application’s configuration to the following:
SMTP Hostname: smtp.mailgun.org
Port: 587
Username: See Default SMTP Username on Mailgun domain page
Password: See Default Password on your Mailgun domain page
If you’re using a Mandrill library, you will need to migrate to a Mailgun-specific library or a library that is SMTP compatible. We have code samples for most major languages.
Our team is available 24/7/365 to help make sure you have a successful transition to Mailgun. From the Mailgun dashboard, click the Support button to access our help center or create a support ticket.
Last updated on September 16, 2020
Zipbooks Switched From Mandrill To Mailgun Using Laravel
Migrating From Mandrill To Mailgun
Zipbooks Switched From Mandrill To Mailgun Using Laravel
Sunset Policies: Allowing Unengaged Recipients to Ride Off into the Sunset
The Best Time To Send Emails: Cracking The Code
The Basics of Email Subdomains
How To Promote Strategic Engagement In Your Email Program
How To Improve Email Click-Through Rates
The Basics of SPF Records
Dedicated vs Shared IPs: Which One Should You Use?
Make Email Accessibility Your New Year’s Resolution
Sunset Policies: Allowing Unengaged Recipients to Ride Off into the Sunset
Email's Best of 2020
Catch-All Domain Support Is Now Available In Email Validations
The Best Time To Send Emails: Cracking The Code
Tips for Building Better Holiday Email Templates
Happy Festivus: Email Deliverability For The Holiday Season
The Basics of Email Subdomains
A Word of Caution For Laravel Developers
The Science and Art of Gmail Deliverability
Sunset Policies: Allowing Unengaged Recipients to Ride Off into the Sunset
Email's Best of 2020
Catch-All Domain Support Is Now Available In Email Validations
How To Improve Email Open Rates
Preparing Your Email Infrastructure Correctly
4 Tips To Improve Your Email Deliverability In 2020
COVID-19 Email Communications Dos and Don’ts
How To Use Parallel Programming
Mailgun’s COVID-19 Plan of Action
Password Meters Are Not For Humans
Always be in the know and grab free email resources!
Mailgun is committed to protecting your privacy. Please read ourPrivacy Policybefore providing us with your details.