Who is allowed to send mail as you
v=spf1 a mx include:spf.protection.outlook.com include:aspmx.pardot.com include:spf.mandrillapp.com include:mail.zendesk.com include:_spf.salesforce.com ~all
Your SPF record doesn't authorize Google to send mail. Even though FrostSender connects via Gmail, your SPF check will fail — recipients will treat your mail as suspicious.
Cryptographic signature on every send
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDNRAbs8WpdFTAVL6cpoOKXeQTbToOw5mbuXEXqThxtGU9XrmUiCjFDrLl4c8LFzZKg6B6PhgSOa1cQihyFpDKaHplobjpRjOS+ab6jGNvgXzUQHgU7kpXZEkgL+GxcmZREN2e2HAk2c8U25TDWUyeXudihtmWSMgoedRLtdmE/iQIDAQAB;
What receivers do when SPF or DKIM fail
v=DMARC1; p=reject; rua=mailto:dmarc_report@cognism.com,mailto:dmarc_agg@vali.email; ruf=mailto:dmarc_report@cognism.com; fo=1:d:s; pct=100; ri=172800; adkim=r; aspf=r
Where your inbound mail is delivered
cognism-com.mail.protection.outlook.com
Your MX records point to mail servers other than Google's. Because FrostSender connects through Gmail OAuth, Gmail and other inbox providers will treat mail you send as spoofing — outgoing delivery will fail.
Want this fixed at the source?
FrostSender ships with deliverability monitoring built in. Get on the list and we’ll let you know the moment we open access.