ElasticEmail SPF Bug ?

Jamie Whittingham

Active Member
Hi guys,

So I setup an ElasticEmail account and added to our MW installation.

The issue is, when we generate SPF records for domains, _spf.elasticemail.com does not appear.

Can anyone confirm this or does anyone have a solution? this does NOT happen with Amazon SES, ManDrill or other providers within the MW platform, only Elasticemail.

Thanks
 

Jamie Whittingham

Active Member
when you add a sending domain it gives you SPF and DKIM

within the SPF section its listing the delivery server IP's for our servers like SMTP IP's and Amazong and Mandrill but nothing for ElasticEmail
 

twisted1919

Administrator
Staff member
Maybe because EE is not a smtp but a web api type?
Anyway, For services like EE/Amazon/Mandrill/Etc you should not have sending domains since they do the signing and all anyway, you just introduce overhead otherwise.
 

Jamie Whittingham

Active Member
Web API

Also, of course clients need to add the SPF records for ElasticEmail otherwise the SPF will fail when they send emails using their own domain name via the ElasticEmail API service.....
 

twisted1919

Administrator
Staff member
Only smtp servers will be added to spf records. For web apis you have to do it from your web api provider dashboard.
 

Jamie Whittingham

Active Member
v=spf1 +a +mx +ip4:96.127.135.42 include:_spf.google.com include:_spf.elasticemail.com include:spf.mandrillapp.com ~all

This was taken from another thread on here so mailwizz 'should' be adding the SPF

Why does ManDrill API get added to the SPF records then?

How do customers adding their own sending domains know to add the SPF records for ElasticEmail? they wouldn't unless the system told them to add it.
 

twisted1919

Administrator
Staff member
How do customers adding their own sending domains know to add the SPF records for ElasticEmail? they wouldn't unless the system told them to add it.
They don't have to, EE takes care of this automatically. Other services will make you add these records when you create your account so that you can actually send, so there's nothing mailwizz can do for you in this case, that's why it doesn't even generate the spf records for web api implementations.

P.S: If you look in /apps/common/models/SendingDomain.php at line 314 where the actual code for generating the spf records reside, you will see that it generates only for servers of type SMTP and SMTP-AMAZON, that's all :)
 

Jamie Whittingham

Active Member
Thanks for that info - so when I added Mandrill, why did Mandrip (which was the API instance) get added into the SPF strings given to customers?
 

twisted1919

Administrator
Staff member
I doubt it did, the code clearly states it will do it only for smtp/smtp-amazon and usually the code is right :)
 
Top