Simple Email Marketing
Home > Have a question? We're here to help. > Account how-to > How to whitelist

How to whitelist

Table of contents
No headers

While everything that you are sending via your account is coming from our servers, sometimes there can be a problem when the account owners send emails from us to their own email account on their own server. The reason for this is that you set an RSVP address within your account that claims to be coming from “@yoursite.com” so none of your recipients will be wise to the fact you are using us.

This is all fine and dandy, but when the emails come from us to your server, your server is going to be sophisticated enough to know that the email claims to be internal (@yoursite.com) but is actually coming from our sending domain (e2ma.net).

Since external emails claiming to be internal emails is a somewhat common spamming tactic, your server may prevent this from happening.

By having your IT folks whitelist e2ma.net and the IP ranges below, you are telling your server that we can be trusted and not to block the emails she sends to your server on your behalf.

Sending domain: e2ma.net
IP Range: 128.136.37.0/24 (128.136.37.1 to 128.136.37.255)
IP Range: 66.179.147.160/27
IP Range: 66.179.102.0/25
IP Range: 66.179.68.0/26
*IP Range: 139.60.0.0/22
*additional sending IP range, effective April 16, 2018

Additionally, it may be necessary for external recipients with private domains (not Gmail, Yahoo, etc.) to whitelist our IP range if they have stringent cybersecurity measures in place. This is often the case with government agencies, financial institutions, medical groups and the like.

Last modified

Tags

Classifications

This page has no classifications.

Announcements

Emma phone support will be unavailable on November XX, between the hours of XX:XX and XX:XX. You can still contact support using the link above and we will respond as soon as we can.

App status