How to Avoid Outgoing Mail being Tagged as Spam

From A2Wiki

Some other things to check in your mail content:

1. Make sure your mail content doesn't appear "spammy" including - Don't send HTML-only email if possible (do plain text or multi-part MIME with a text/plain component) - If you are sending HTML mail, make sure it is valid HTML markup (use a service like http://validator.w3.org to test it (you can check a URL, upload a file, or paste HTML into a text box) - Don't use lots of exclamation points or $ in the subject 2. Make sure all envelope headers are included (Message-ID especially)

For more details about Gmail, see http://www.google.com/mail/help/bulk_mail.html

You may also request that A2 set up an SPF record for your domain. While we don't officially support SPF records, we can set them up upon request. Here's an example:

"v=spf1 a mx ~all"

That says:

"a" - your domain's IP address is the IP address of that server which is allowed to send mail from your domain

"mx" - There are 2 names for the MX servers for yourdomain.com: yourdomain and host-IP.a2webhosting.com. (A single machine may go by more than one hostname. All of them are shown.) The servers behind those names are allowed to send mail from yourdomain.com

"~all" - SPF queries that do not match any other mechanism will return "softfail". Messages that are not sent from an approved server should still be accepted but may be subjected to greater scrutiny. The "-all" you had would be a "hard fail" and may keep mail from being delivered that you send through another source occasionally (your ISP, etc.). If you know for a fact that the only mail coming from your domain will be through our server, we can change that to "-all" but I've yet to see that be A Good Thing (if everyone used SPF it might be more helpful, but unfortunately that's not the case yet).