What to do if you're not receiving Emma emails internally
It’s possible that you may run into an issue where everyone except people at your company are receiving your emails sent through Emma. Emma’s not trying to shun you; she just needs your server to unlock the door when she comes knocking. Here’s some information on how to let Emma emails in.
While everything that you are sending via Emma is coming from the Emma servers, sometimes there can be a problem when the account owners send emails from Emma to their own email account on their own server. The reason for this is that you set an RSVP address within your Emma account that claims to be coming from “@yoursite.com” so none of your recipients will be wise to the fact you are using Emma.
This is all fine and dandy, but when the emails come from Emma 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 Emma can be trusted and not to block the emails she sends to your server on your behalf.
*Sending domain: e2ma.net
*IP Range: 22.214.171.124/24 (126.96.36.199 to 188.8.131.52)
*IP Range: 184.108.40.206/27
*IP Range: 220.127.116.11/25
*IP Range: 18.104.22.168/26