Today is the official launch of sending unlimited mail merge emails in Gmail. Now you can send mail merge campaigns as big as you want, right from your Gmail account. It works by connecting a third party SMTP service like Sendgrid or JangoSMTP to your GMass account.
Last month I announced this feature in beta. Now, I have perfected it using feedback from several hundred test users.
The advantages of this setup are:
- The ability to send virtually unlimited emails in Gmail and avoid Gmail’s sending limits.
- No risk of a Gmail account being suspended by Google.
How can you send unlimited mail merge emails from your Gmail account?
First, you need a GMass account. Then, you connect your GMass account to any external SMTP server. This will make it so your emails are sent from that server and not from your actual Gmail account, although everything will look as normal inside your Gmail account. Meaning, each email message will still show up in your Sent Mail folder, and GMass will still be able to track replies, bounces, and everything that happens after you send an email campaign.
The most noticeable differences with our launch today, compared to our beta launch a few weeks ago are that now:
- You can choose SMTP sending on a per-campaign basis. Previously, once the SMTP service was set, all emails from your account would send through it rather than your Gmail account. Now you can selectively choose which campaigns are sent with SMTP and which are sent with your Gmail account.
- If you don’t want to set up your own SMTP account, you might be able to use our internal SMTP service, which is a Sendgrid account. Now there is a process to request to use our SMTP service if you don’t want to set up your own.
- You can use the SMTP setting with the Preview as Drafts feature to first create Drafts, and then send the Drafts with the SMTP server.
Step 1: Setting up your SMTP service
Option A: Getting your own SMTP service
An SMTP server is simply an email sending server. There are many well-known SMTP service providers, including Sendgrid, JangoSMTP, Mailgun, Mailjet, and others. Pricing for SMTP services range from free plans which let you send a few hundred emails/day to around $20 USD/month for thousands of emails/month. Each service has its own advantages and disadvantages, and you’re free to use any SMTP service you like.
In our testing, we’ve found that Sendgrid and JangoSMTP are the two SMTP services that are most compatible with GMass, because of their flexibility in not requiring domain-based verification in order to start relaying email through them. This is especially important if you’re connecting a email@example.com GMass account to an SMTP service.
If you choose Sendgrid, here is a detailed guide to configuring your Sendgrid account for GMass use.
Option B: Request to use our SendGrid SMTP account
If you’re sending strictly opt-in email, you might be eligible to use our SendGrid account.
Step 2: Linking your GMass account to the SMTP service
If you set up your own SMTP service, this is how to link the SMTP service to your GMass account. Note that if you’ve been approved to use our SMTP service, you will skip this step.
- First, reload Gmail in your Chrome browser to make sure you have the latest version of GMass.
- Click Compose to launch a new window.
- Set the To field to firstname.lastname@example.org.
- Set the Subject to the word set. Wait a second for the form to appear in the Message area.
- Enter the SMTP server, port, username, and password after the colons. If your server does not require authentication, set the Username to “noauth” (without the quotes) and leave the Password blank.
- Hit the GMass button. Do not hit the Send button.
GMass will relay a test email through the server to yourself. If successful, the SMTP server will be set for your account and you will now see that setting appear in the Settings box.
To clear out the SMTP settings, set the Subject to “clear” and hit the GMass button. To view the SMTP setting currently on your account, set the Subject to “status” and hit the GMass button.
Step 3: Sending a campaign through the SMTP server
You’ll notice a new option in the GMass Settings box that allows you to set, on a per-campaign basis, whether the emails should be routed through the SMTP server for unlimited sending, or through your Google account, in which case you’d be subject to Gmail’s sending limits.
Note: This option will only appear if you have connected an SMTP account to GMass.
Frequently Asked Questions (FAQ):
Q: What’s going on here? How do I use an external SMTP server and send unlimited emails from my Gmail account?
A: You simply set up an SMTP account with a popular provider like Sendgrid, Mailgun, Mailjet, or JangoSMTP. Then, you link your SMTP account to your Gmail account. Finally, for each campaign you send with GMass, you can choose whether to send the campaign through Gmail or through the SMTP server. If you send through Gmail, you’ll be constrained by Gmail’s limits, but if you send through the SMTP server, you’ll be able to send virtually unlimited emails.
Q: I’m so confused. I would love to be able to send unlimited emails from my Gmail account, but I’m not very technical and I know nothing about SMTP.
A: If you’re sending low-volume, non-commercial, email campaigns, you can apply to use our Sendgrid account using the directions above. Otherwise, please consult your organization’s IT person for further help. Setting up an SMTP account and linking it to GMass can be accomplished by any IT person with a basic knowledge of how email works.
Q: Doesn’t sending through an SMTP service eliminate the deliverability advantage GMass “normally” has, since normally GMass sends email through Google’s servers, which are the highest deliverability email servers in the world?
A: Theoretically, your deliverability may drop slightly if you switch from sending via Gmail to sending via an SMTP server. In our testing with several hundred users though, we have not seen a noticeable difference in deliverability, as measured by open and click rates. You should monitor your own campaign statistics though once you switch to SMTP sending, to ensure this is the case for you.
Q: It sounds like you’re getting around Google’s rules by sending this way. Won’t Google get upset with me if I use my Gmail account in this manner?
A: As far as we know, sending email campaigns like this doesn’t violate any of Google’s terms. Additionally, in testing with several hundred users, there haven’t been any reports of trouble. What we are offering here is simply a way to use the Gmail user interface to create, launch, and track an email campaign, while the emails are actually sent by a non-Gmail server.
Q: Do you charge more for sending via SMTP?
A: Currently, we are not charging any extra for relaying email through an external SMTP server, whether it’s our internal SMTP account you’re using or one you set up yourself. Your only additional costs will be the cost with the SMTP service provider, which may be an additional $10+/month USD, based on what kind of account you get. So theoretically you could pay $12.95/month to GMass for a G Suite Standard account, and pay Sendgrid an additional $9.95/month and send 40,000 emails/month or $19.95/month and send 100,000 emails/month. For your low-volume campaigns, you could still elect to send natively through your G Suite account, allowing for another 1,500-2,000 emails/day.
Q: Is the SMTP option available for free GMass accounts, or do I need to be subscribed to GMass?
A: It will work with a free GMass account as well, but using this option with a free GMass account defeats the purpose. GMass already limits free accounts to sending 50 emails per 24 hours, which is well under Gmail’s own limits, so connecting to an SMTP server to send high volume campaigns wouldn’t solve anything, since a GMass free account will already limit you to 50 emails per rolling 24 hours.
Q: Why should I use two services, yours and an external SMTP provider, when I could use one service like Sendgrid, which also supports sending newsletters?
A: You are free to use any service you like, but we think that GMass with an external SMTP service makes for a powerful combination for email marketing and email automation. The ease and familiarity of the Gmail interface makes sending an email campaign a time efficient process. Additionally, by combining GMass and an external SMTP service, you can send virtually unlimited emails with the auto follow-up feature, a feat that would be impossible without GMass, since GMass integrates with your Gmail Inbox. Using just Sendgrid in a standalone fashion won’t accomplish that.
Q: I’ve read that Gmail doesn’t allow its users to send “from” their Gmail accounts using outside servers. So how are you getting away with this?
A: It was thought that in early 2017, Gmail was going to update their DMARC policy to reject emails that are “from” a gmail.com address and sent by a non-Gmail server. Here’s some more detail on that prediction. That change hasn’t happened yet though. Here is Gmail’s DMARC record as of 9/28/17 11:24 AM CST:
If you are sending campaigns from your @gmail.com address rather than your organization’s G Suite address, then this policy is relevant to you, and we’ll be monitoring it for changes. In our testing so far though, we’ve only found one email provider, AOL, that routes emails that match this criteria to the Spam folder. Even Gmail doesn’t reject email that is sent from an @gmail.com address by a non-Gmail server. For example, in my testing, I sent email “from” email@example.com through smtp.sendgrid.net to my firstname.lastname@example.org account, and the email arrived to the Inbox at my email@example.com account. If you are sending from your G Suite address, then you don’t need to worry about this policy at all, because you get to set your own policy for your domain!
Q: In my Gmail Settings under “Send mail as”, I can add another From Address to use, and then Gmail asks me to specify an SMTP server. How is that different from specifying an SMTP server this way?
A: When you set up a new From Address in your Gmail account, if the From Address is a non-Gmail address, then yes, you are asked to set an SMTP server. However, even in that case, the Gmail sending limits still apply because it is still Gmail that is relaying the emails through your SMTP server. With this new method of linking the SMTP account to your GMass account, Gmail isn’t “handling” any of the email sending and isn’t “aware” of what’s being sent, so the limits won’t apply.
Q: I want to send a 100,000 email campaign using GMass and Sendgrid. How long will it take my campaign to send?
A: Admittedly, because of how we are sending these emails, we have not optimized this process for speed. If you need to send 100,000 emails in an hour, then this isn’t the right solution. The rate of sending will be around 3,500 emails/hour. Why so slow? Because the processing power of both sending the email through an external SMTP service AND making sure your Gmail account knows about it is a “costly” procedure, from a computing perspective. So, if you need to send 25,000 emails throughout the course of the day, then this could work well for you. But if you need to send 25,000 emails in the next ten minutes, this is not the solution for you.
Q: Do I need to worry about SPF, DKIM, and DMARC?
A: It depends on which SMTP service you choose and whether you’re sending from an @gmail.com address or a G Suite address.
If sending from an @gmail.com account, you don’t need to worry about any of this, because Gmail handles it for you.
If sending from a G Suite account, then it depends on the SMTP service you choose.
The default setup with Sendgrid is such that you do NOT have to worry about SPF, DKIM, and DMARC. This is because in the default setup the MAIL-FROM used in email sending is a sendgrid.net address, so the SPF and DKIM signing is taken care of by Sendgrid’s DNS records and infrastructure.
If you opt for Sendgrid’s “whitelabel” option though, then the MAIL-FROM can be based on your own domain, and then you would need to ensure that SPF is set up to allow sending from your domain through Sendgrid, and you can then have emails DKIM-signed by your own domain as well. For other providers, like Mailgun, for example, you have to “whitelabel” your domain from the outset, and handle SPF/DKIM from the outset. Therefore we can conclude that getting set up on Sendgrid is easier because they don’t require this setup.
Q: Do you recommend certain SMTP services over others?
A: There are many SMTP services to choose from, including Sendgrid, JangoSMTP, Mailgun, Mailjet, SparkPost, Amazon SES, and others. Each has its strengths and weaknesses, and I’ll be detailing all of these in a future blog post. I’ve been testing extensively with Sendgrid, and so far, I’ve found it to be a good fit for this solution, because it doesn’t require any domain verification to get started and it sends bounces back to you. That’s not to say that another service wouldn’t fit you just as well. Personally, I’m most familiar with Sendgrid and JangoSMTP. Full disclosure: I created JangoSMTP back in the early 2000s, and it was acquired in 2013, but I’m still close to the JangoSMTP team.
When you link an SMTP account to your GMass account, you may encounter these common scenarios.
- You are sending a campaign with Gmail when before your campaign finishes sending, you start to get “You’ve exceeded your limit” bounces and GMass pauses the sending of your campaign. If you then link an SMTP account to your GMass account, GMass will switch any pending campaigns to SMTP sending so that you don’t get these bounces anymore.
- You’ve just linked your SMTP account, or we’ve just approved you to use ours. When you compose your next campaign, the option in the Settings box will default to SMTP sending. You can of course switch it to Gmail sending. The Gmail vs SMTP option in the Settings box will remember whatever you last set it to.
- You set your campaign to just create Drafts rather than send right away. When you then click the link to send the Drafts, you’ll be given a choice of whether to send them via Gmail or via the SMTP server linked to your account.
If you’d like to dive deeper into Gmail, SMTP sending, and the correct configuration for an SMTP account, you might be interested in:
Using Sendgrid? The recommended Sendgrid configuration.
If you’re setting up an SMTP account, we generally recommend against getting a dedicated IP. Here’s why.
What is an SMTP server? Here’s the Wikipedia article on SMTP.