Troubleshooting SPF and DKIM validation issues

Common SPF issues:


SPF, or Sender Policy Framework, is used to verify that Proposify is authorized to send email using your domain. Here are a few common issues that may arise:


  • I already have an SPF record

You will need to merge any existing SPF records on your domain with the one for Proposify. The merged record should be the only one on your domain - all others should be deleted.


Here’s an example for sending over Google. Take the Proposify SPF record:


v=spf1 a mx include:spf.mtasv.net ~all


And combine it with the Google SPF record:


v=spf1 include:_spf.google.com ~all


To create the following merged record:


v=spf1 a mx include:spf.mtasv.net include:_spf.google.com ~all


You can see all of your SPF records from your domain’s control panel. SPF records always start with “v=spf1”. Note that the merged SPF record contains, “a”, “mx”, and “~all”. Note in particular the “~all” part has a tilde. Even if one of your SPF records has “-all” or “+all”, merging records will require it to be “~all”.


  • My SPF isn’t validating

It usually only takes between one and two hours for your domain changes to work, but it may take as long as 48 hours.


  • The SPF Host field is invalid

If your domain control panel rejects the Host specified in our email setup page, try setting the Host to “@” (without the quotes).




Common DKIM issues:


DKIM, or DomainKeys Identified Mail, is an email authentication method designed to detect email spoofing by providing a mechanism to allow receiving mail exchangers to check that incoming mail from a domain is authorized by that domain's administrators.


  • My DKIM Host isn’t validating

The DKIM Host may cause many issues with validation. Please ensure that the Host is exactly as written in our email setup page.


If your DKIM continues to fail validation, you may need to remove your domain from the Host field. Here is an example Host:


20160106203825.pm._domainkey.example.com


Remove the “.example.com” so that it looks like this:


20160106203825.pm._domainkey


  • My DKIM Value isn’t validating

Please ensure that the DKIM value is exactly as written in our email setup page. The DKIM value must start with “k=rsa; ”. The line of numbers, letters, and other characters that follows is called the Key. Please ensure there are no spaces or line breaks in the middle of that key.