This article is about whitelisting and explains why it may be a good idea for your IT team to whitelist Frankie's sending addresses.
Whitelisting is the practice of explicitly allowing a specific domain and sending IP access to a particular privilege, like delivering emails. If you're having trouble either receiving your own email campaigns or others in your company aren't receiving your campaigns, you may want to ask your IT team to whitelist our addresses.
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. Generally, 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 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; which is where whitelisting comes into play.
Have an IT professional handle your whitelisting
By having your IT folks whitelist e2ma.net and our sending IPs below, you are telling your server that we can be trusted and not to block the emails we send to your server on your behalf.
-
Sending domain: e2ma.net
-
IP Range: 139.60.0.0/22
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.