I'm running into some problems with DMARC alignment when using Greenhouse services for sending emails. Specifically, Greenhouse has instructed me to set up my SPF record like this:
Type: TXT HOSTNAME: gh-mail.[domain].com Required Value: include: mg-spf.greenhouse.io ~all
Since I utilize several different email sending services, I incorporated 'include:mg-spf.greenhouse.io' into my existing SPF record, which already contains multiple includes, and I made sure to conclude with '~all'. Despite this setup, I'm still failing the DMARC alignment. Here's what my email header looks like:
Authentication-Results: mx.google.com;
dkim=pass [email protected] header.s=k1 header.b=e56dcvDA;
dkim=pass [email protected] header.s=mg header.b=DOBjgR+U;
spf=pass (google.com: domain of bounce+9d300b.a828fb-noty77681=gmail.com@outbound-mail.greenhouse.io designates 69.72.40.98 as permitted sender) smtp.mailfrom="bounce+9d300b.a828fb-noty77681=gmail.com@outbound-mail.greenhouse.io";
dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=domain.com
Could someone guide me on how to resolve this? I'm considering adding 'include:outbound-mail.greenhouse.io' to the record, but I'm unsure if that's the right move.
3 Answers
It sounds like you're dealing with an alignment failure. To clarify, DMARC mandates that either DKIM or SPF must align with the From domain, and it seems neither is doing that here. Looking at your headers, the From domain is 'domain.com', but the SPF authenticated domain is 'outbound-mail.greenhouse.io'. So, the problem lies in the fact that you're using third-party services like Greenhouse and Mailgun but sending from 'domain.com'. To fix this:
1. You need to ensure DKIM alignment by having Greenhouse or Mailgun sign your emails using your 'domain.com' DKIM key.
2. Alternatively, for SPF alignment, add a Mailgun or Greenhouse SPF record to your domain's SPF policy and ensure the Return-Path is set from 'domain.com'.
Check out the guide on configuring DKIM with Greenhouse for more details!
Honestly, you might want to send a test email to suped.com/tester, as that can help diagnose the alignment issues more effectively. It could give you clearer insights on where exactly the problem is.
Could you share your full TXT record for SPF? Seeing all the entries would help in troubleshooting. Sometimes a small error in the text string can cause compliance issues.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures