Who is allowed to send mail as you
v=spf1 include:_spf.lusha_com._d.easydmarc.pro ~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=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCqRoznLXM79DnCnqUhl1cgE4sNkpQDApHytpBH+pvN2XIXwzkzct6jLFOFvRrYechAIdqwvSECdo2bWjkC0m3IwIlOUS7lyKmaO/zNOlXlPGJB+snOC2x/+0PLa7VKkPW9sQ4IFl99IkuO3wsEbB1VKdBRcH8dITbh4dprxMLOkwIDAQAB
What receivers do when SPF or DKIM fail
v=DMARC1;p=reject;pct=100;rua=mailto:e5f11c2159@rua.easydmarc.asia;ruf=mailto:e5f11c2159@ruf.easydmarc.asia;ri=86400;aspf=r;adkim=s;fo=1
Where your inbound mail is delivered
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com
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.