In the last few months, several of the emails I've sent through Opalstack's SMTP have been marked as spam on the recipient's end.
I use the Squarespace Domains email forwarding service, with Opalstack’s nameservers, and one of the DNS records they ask you to create is:
v=spf1 include:mailgun.org ~all
From what I understand, this has been overriding the SPF record from Opalstack. So, to fix this, I've created a merged SPF record, like this:
v=spf1 include:spf.opalstack.com include:mailgun.org ~all
I ran a test that said my domain had no DMARC record. So I also added a _dmarc subdomain and a new record, based on the docs.
v=DMARC1; p=none;
I also tested DKIM, and that seemed to be fine as-is, so I left it alone.
1. Is a merged SPF record the correct approach for using both Squarespace email forwarding and Opalstack's SMTP?
2. Is it expected that adding a manual SPF record will disable the automatic DMARC record?
Thank you,
Chad
