Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I guess you didn't publish any SPF / DKIM authentication record</p> <blockquote> <p>Received-SPF: neutral (google.com: 8.22.200.47 is neither permitted nor denied by best guess record for domain of test@bookmytakeout.com) client-ip=8.22.200.47; DomainKey-Status: bad format</p> </blockquote> <p>Most of the time, Gmail (as well as the other major ISPs) will place the non-authenticated messages in the junk folder. </p> <p>An SPF record or a DKIM guarantees that you are allowed to use a certain domain as a sender. For example, if you don't own "paypal.com", you can't send an email from "contact@paypal.com". If you've published the right SPF / DKIM, the ISP will consider you as a trusted sender. </p> <p>SPF &amp; DKIM were first designed to fight against phishing. </p> <p><strong>DIY SOLUTION:</strong> Publish some records by following these instructions: <a href="http://dkim.org/specs/rfc5585.html" rel="noreferrer">http://dkim.org/specs/rfc5585.html</a> <a href="http://www.openspf.org/FAQ" rel="noreferrer">http://www.openspf.org/FAQ</a></p> <p><strong>EASY SOLUTION:</strong> Use a service that will do everything for you. A good ESP will usually sign your emails with DKIM / SPF by default. The problem is that you will sometimes get a "sent via ESP_NAME" mention (in Gmail). </p> <p>So the best thing to do is to choose an ESP which will provide you personalized DKIM &amp; SPF. This way, it will be 100% transparent. </p> <p>I work for Mailjet and we offer this service for free. Most of our competitors offer this as an option. </p> <p>Here's a useful post about this "via-mention" you get when your ESP signs "by default" and how to get rid of it. <a href="http://blog.mailjet.com/post/16922561593/personalized-spf-dkim" rel="noreferrer">http://blog.mailjet.com/post/16922561593/personalized-spf-dkim</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload