Whitelist Update: New Emma Sending IP Range and API Address

  • 1
  • Announcement
  • Updated 4 months ago
  • (Edited)
Whitelisting sending IPs is a common practice in delivery troubleshooting and you (or your IT team) may have whitelisted Emma’s sending IP's in the past to alleviate some internal delivery issues — like sending campaigns to someone with your same work email address. If you haven’t already, whitelisting is recommended best practice any time you’re using an email service provider like Emma.

If you’ve previously whitelisted Emma’s sending IPs, you’ll need to add the following new IP range to that whitelist as soon as you can. 

New sending IP range

Whitelisting this new range of IPs will help ensure mailings sent from Emma are successfully delivered to your internal addresses (addresses with the same domain as your sender email address). Please pass this information along to your IT team — or whomever is in charge of your sending domain — to make sure this sending range is whitelisted before April 16, 2018 so they can take appropriate measures.

You can also find the new IP range listed in our whitelist documentation here.

In addition, we are also going to be updating our public API address on April 16, 2018.

New public API address

If you aren’t sure if you use Emma's public API, check in with your IT team and pass them along this article to make sure they have everything they need in case you do. Our public API is generally only accessed by customers that write their own internal software integrations with Emma.

We have set up a testing address of apitmp.e2ma.net that can be used to test your custom applications that use our public API before we go live on April 16. This temporary address will be disabled after April 16th so be sure to switch back before then.
Photo of Grey Stepp

Grey Stepp, Support Team Manager

  • 1699 Posts
  • 135 Reply Likes

Posted 5 months ago

  • 1
Photo of Tianhua Zheng

Tianhua Zheng

  • 1 Post
  • 0 Reply Likes
For new public API IP, if we were using the domain name (https://api.e2ma.net) instead of IP, we don't need to change anything right? I believe you guys will bind the new IP to the domain.
$url = "https://api.e2ma.net/";.$account_id."/members/add";
Photo of Grey Stepp

Grey Stepp, Support Team Manager

  • 1695 Posts
  • 135 Reply Likes
Hi there!  I checked in with my systems folks and they said this:

"Yes, that hostname will be pointed to the new IP. You don’t need to change that."  
Photo of ClientView


  • 2 Posts
  • 0 Reply Likes
Our current DNS TXT entries are:
v=spf1 include:e2ma.net -all

v=spf2.0/pra include:e2ma.net -all 

I have used http://www.openspf.org/SPF_Record_Syntax as a resource and it seems that our current entries may not always work.  Therefore, I am seeking Emma's input on taking the following steps:

1. remove the current TXT entries

2. Add which one?

a) v=spf1 ip4: ip4: ip4: ip4: ip4: include:e2ma.net -all

b) v=spf1 ip4: ip4: ip4: ip4: ip4: include:e2ma.net ~all

c)  v=spf1 mx a ip4: ip4: ip4: ip4: ip4: include:e2ma.net -all

d)  c)  v=spf1 mx a ip4: ip4: ip4: ip4: ip4: include:e2ma.net ~all

e) other please specify
Photo of Grey Stepp

Grey Stepp, Support Team Manager

  • 1697 Posts
  • 135 Reply Likes
Hey there!   I have asked my Deliverability team to weigh in on this one.  I'll post back here as soon as I hear back from them! 

- G
Photo of Grey Stepp

Grey Stepp, Support Team Manager

  • 1697 Posts
  • 135 Reply Likes
From my Delivery team:

You do not need to make any changes to their TXT records. By having "include:e2ma.net" in your SPF record, you are including any Emma IP that will be used to send their mail in their SPF record. This basically means they are saying "everything that is in e2ma.net's SPF record, include it in ours". We will always keep our SPF record updated with the IPs we are using, so you should be good to go.  

Please let me know if you have any additional questions.