Thanks Kim - however the goal is to allow the aliased domain to pass both SPF and DKIM, not restrict those emails. I do agree that the aliaseddomain.com SPF record should be fixed, but again, it looks like that record isn't even being looked at it.My...

We do have SPF set up for both domains:primarydomain.com: v=spf1 include:_spf.google.com include:servers.mcsv.net +a +mx +ip4:xx.xx.xx.xx include:spf.mandrillapp.com ~allaliaseddomain.com:v=spf1 include:dc-aa8e722993._spfm.asliaseddomain.com ~allI am...

In my review of email headers sent from an aliased domain directly from web-based Gmail, the headers list primarydomain.com as the return path, while the DKIM selector indicates aliaseddomain.com - this results in a misaligned (but verified) SPF and ...

This is because you need to change the selector to Google (assuming the domain is a Google Workspace domain)