- Best Practices
So, you wanted to send out a lot of emails but found that when you did, a lot of them either ended up undelivered or in the spam folder.
Think of it like this: When you start working out, you want to make sure that you stretch and warm up properly so that you don’t injure yourself. The same is true for when you start sending emails. An excellent warmup process is needed to ensure that you don’t overdo it and damage your reputation.
You might already be familiar with the need for warming up a new IP, and domains are much in the same. Still, it’s important to note that both reputations are important considering that IPs and domains build and maintain separate reputations.
A good warmup period ensures that your IP and domain both build reputations with mailbox providers, which increases your chances of delivering to their inbox.
While the warmup process can seem slow and tedious, it’s vital if you want to avoid the dreaded spam folder. Otherwise, you’ll start to experience other issues like throttling, greylisting, or outright blocking of your messages.
When we talk about the warmup process, we talk about two major forms of warmup: IP warmup and domain warmup. Depending on your current scenario and warmup needs, you will want to look at doing one or both of these.
In one scenario, you already have an established mail stream and domain. However, you’re looking to increase your sending and will require a second dedicated IP to share the load of that sending.
This is where IP warmup comes in: a new dedicated IP will be “cold.” In other words, the IP hasn’t seen traffic for a certain amount of time, and will not have a reputation attached to it. To build up this reputation, you need to warm up the IP. You can do this one of two ways: Manually or automatically. When you warm up manually, you set hourly/daily sending limits in your system and slowly ramp up as you go. Alternatively, you can use Mailgun’s automated IP warmup which takes that work off your hands.
Another scenario could be that you are adding in a new domain to handle a new type of messages you want to send out. Volume-wise, you are still well within recommended limits for your current amount of IPs, but want to build better domain reputations with more concise sending domains (firstname.lastname@example.org, email@example.com, etc.).
Here is where many senders would say, “Well, my IP is already warm and has a good reputation, so I can just start sending at volume day 1.” While this is technically true, you could run the risk of your domain getting assigned a poor domain reputation due to its newness. In doing so, you endanger your overall deliverability.
Lastly, you might have a scenario when domain and IP are both new and need warming up. In this case, you will want to warm them up in tandem with each other. Generally, this means that you forego the automated IP warmup in favor of a manual warmup that benefits both the IP and the domain.
The manual warmup process will generally look the same for IP and domain warmups in term of the daily sending limits. Here’s a snippet of a warmup plan:
It’s especially important to note here that a plan with daily limits like this assumes daily sending. For example, you send days 1-5, then do not send on days 6 and 7, you cannot pick back up with the limit for day 8. Don’t rush it — slow and steady wins the race!
The daily send numbers can also vary based on multiple factors such as list hygiene and engagement. Your sending needs to be monitored during the warmup process so that changes can be made as necessary if you see a high rate of errors or your emails consistently go to the spam folder.
Not all mailbox providers are created equal, and the same is true for warmup plans. In some cases, you might want to develop and follow a more targeted warmup plan for messages going to a specific mailbox provider. Targeted warmup plans ensure that you meet their criteria - as much as they are known - to build reputation and land in the inbox. This can mean lower hourly and daily quotas, slower ramping, or spreading your traffic out over more time.
It’s important to note that domain reputation is generally tied to the DKIM authority domain. By default, domains created within Mailgun are created with their own DKIM authority. This means that subdomains do not inherit and share a reputation with their parent domain unless specified during domain creation.
With a new domain, whether it’s a subdomain or a root domain, you’ll most likely need to warm up of the domain itself. This is done almost the same way as the manual IP warmup. You start by limiting the volume going out of the domain every day and ramping this up slowly over time.
Also, we recommend targeting your most engaged recipients during the warmup process to ensure that you see good open and click rates. Sending to engaged recipients is a huge boost to reputation, and for some mailbox providers like Gmail, it is especially important. Gmail uses engagements as one of its main metrics to determine mailbox placement. Every little bit helps, right? Regardless, it’s worth asking...
Having gone through all of the warmup exercises and stretches, you’ll ask yourself this — was it successful? The answer is largely going to lie in your event logs. You will want to keep an eye on failed events and their error messages, as well as your engagement numbers, for signs of success/failure. Tools like Google Postmaster Tools help you monitor your IP and domain reputation specifically how Google sees it, so this might be a great solution for you if you’re only sending to Gmail.
As with anything in life, there are no guarantees that following a set warmup plan will net you 100% delivery and great deliverability. However, if you execute your warmup correctly, it should get you off to a good start and give you a foundation to build on further.
Need some extra help with your sending? Mailgun’s Managed service can assist you with building this foundation, by working with you to develop the warmup plan that works best for you and your goals and providing advice along the way.
Last updated on December 31, 2019