Options for customers that won't whitelist

  • 0
  • 2
  • Question
  • Updated 9 months ago
We recently asked a customer company to whitelist the Emma domain and IPs because no one in their company was receiving our emails. They said they identified e2ma.net as being leveraged by numerous spam senders and therefore they refuse to whitelist the domain and IP addresses for security purposes. 

What are our options to make sure they receive our messages? For example, they asked if we can configure a different sending address so they could customize the mail filter to allow just these messages through.
Photo of Minnesota Housing

Minnesota Housing

  • 7 Posts
  • 0 Reply Likes

Posted 9 months ago

  • 0
  • 2
Photo of Heather Sturm

Heather Sturm, Integrations Support Specialist

  • 99 Posts
  • 3 Reply Likes
Hi!

Whitelisting is an approach that is typically completed for internal sending. For instance, sending to other users within your company or organization on the same domain.

When sending to users outside of your organization, we recommend updating your SPF record. This process attaches a type of virtual "permission slip" to your Emma mailings that indicate that you have given Emma permission to send on your behalf.

Here is some useful information about how to update your SPF record: Instructions for Setting Up Emma as an Authorized Sender as well as some general information about SPF records.

You can also ask your recipients to add your sending address to their address books, as this will help increase delivery to the inbox.

I hope this information is helpful! Please note that it can take 24-48 hours for any SPF record updates to take effect on your domain!

Cheers,
Heather
Photo of Minnesota Housing

Minnesota Housing

  • 7 Posts
  • 0 Reply Likes
Hi Heather,

Thanks for this info. Unfortunately, we are part of a larger email system (we're one state agency within the state network), so we can't update the SPF record on our own and the state won't do it either. If there are any other alternatives, please let me know!

Thanks,
Amy
Photo of Heather Sturm

Heather Sturm, Integrations Support Specialist

  • 99 Posts
  • 3 Reply Likes
Hi Amy,

I'm sorry to hear that your organization is unwilling to update your SPF record. The alternative solution that we have for this is to ask your IT team to create a subdomain that you could use when sending with Emma (for instance, emma.yourdomain.org).

You'd still have to apply the SPF update to this domain, but it would not impact the main state network domain.

You could then use the new domain (with its updated SPF record) as the sender address on your Emma mailings. Of course, you'd want to be sure to monitor the inbox of the new sender address! 

Hopefully this will resolve the dilemma! Please let us know if you have further questions! 
Cheers,
Heather