Weekly product update: Inbound emails and self-service dedicated IPs
A look back on some older updates to our inbound routing and dedicated IPs. Read more...
Originally published in 2013, for updated pricing, please consult our pricing page
Hey all. Some cool thing to announce this week. First, we will no longer be charging for incoming emails. And second, you can now add a dedicated IP address to your account directly from the control panel, so no more emails to email@example.com to switch from a shared to dedicated IP.
Table of content
Table of content
Inbound email is now available through the Foundation plan
One of Mailgun’s most popular features is Routes. Routes let you set up rules for how to handle all your incoming emails. When we accept an email, we typically:
Perform spam filtering
Parse the email into structured data that can be easily consumed via another application
Forward the email to another email server or POST to your application.
As of February 2020, the Routes feature is available through the Foundation plan, and all other plans on tiers above it. We hope this feature makes it that much easier for you to handle no-reply emails, and encourages you to set up a Route to process replies to your emails.
Self-service dedicated IP
If you want to add a dedicated IP address to your account, instead of using the standard shared IP that is provisioned when your account is created, you may now upgrade to a dedicated IP within the control panel. Simply click on “switch to dedicated IP” in the control panel and voila, your very own dedicated IP. Dedicated IP addresses are $59/IP/month. You’ll be billed for the IP on your next billing date, or if you decide to downgrade or cancel your account (dedicated IP addresses are not prorated).
While you can add a dedicated IP address, it doesn’t necessarily mean you should. If your sending volume is fairly low (say less than 100,000 emails per month) or very sporadic (e.g a big send once or twice a month), you are probably better off with a shared IP address. Shared IPs have the advantage of always being warm, regardless of your particular sending patterns, and since Mailgun manages the reputation of our IPs closely, you’ll be more likely to get to the inbox with a shared IP in many instances. If you have any questions about whether you should be on a shared or a dedicated IP, reach out to us via live chat, or at firstname.lastname@example.org. We can review your account and provide a recommendation based on your specific use case. Then you can add the dedicated IP address yourself, directly through the control panel. : )
That’s it for this week. We hope your email is just a little easier to automate this week and than it was last week. Something else you’d like to see? Let us know!
P.S. I case you missed it, we rolled out the new Events API last week. Check it out!
Build Laravel 10 email authentication with Mailgun and Digital Ocean
When it was first released, Laravel version 5.7 added a new capability to verify user’s emails. If you’ve ever run php artisan make:auth within a Laravel app you’ll know the...
Here’s everything you need to know about DNS blocklists
The word “blocklist” can almost seem like something out of a movie – a little dramatic, silly, and a little unreal. Unfortunately, in the real world, blocklists are definitely something you...