Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Any suggestion on how to avoid a spam filter are just guess work. If it was that obvious, wouldn't spammers use the same tricks?</p> <p>What I can tell you is that you need to build a reputation of <strong>not</strong> sending spam emails from your servers. And that takes a while to happen. Then you should guard that reputation by not letting spammers relay from your servers.</p> <p>There are hundreds of settings you need to do on your MTA. Listing here a few</p> <ol> <li>Stick to one IP address to relay your emails</li> <li>Get a reverse DNS mapped to that IP address</li> <li>Set SPF record</li> <li>Sign your emails with DKIM</li> <li>Setup DMARC</li> <li>Signup for FBL, so that you get a feedback whenever your email is marked as a SPAM by your recipient. </li> <li>Setup correct headers. There are a bunch of those. You can test your outgoing email headers using <a href="http://spamcheck.postmarkapp.com/" rel="nofollow">this free tool from Postmark</a></li> <li>...</li> </ol> <p>All these measures will help an Email service provider (or ESP) (such as Gmail, Hotmail, Yahoo etc.) to validate that the email actually originated from where it claims it did. </p> <p>Beyond this, there is little you can do. Despite of doing all these, your email can continue to land in spam folder if your recipients keep marking it as spam. So make your users happy. Don't send them emails if they don't want to receive. </p> <p>In the meanwhile, you could use some professional help by using an ESP such as <a href="http://www.sendgrid.com" rel="nofollow">Send Grid</a> for your outgoing emails. They would have already built a good reputation of sending high quality emails. They will take all the pains to ensure their IP addresses maintain high reputation.</p> <p><a href="https://support.google.com/mail/answer/81126" rel="nofollow">Read about some advice from Google</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