http://www.openspf.org/Tools and http://www.kitterman.com/spf/validate.html and http://dkimcore.org/tools/dkimrecordcheck.html
Also, you might learn about warming up an IP address for mail sending if you're going to be pushing volume: http://docs.sendgrid.com/documentation/get-started/sending-p...
Sendgrid's reputation checking and interface for seeing and clearing bounces, spam reports, etc. are extremely useful too.
I imagine you already know all this, but others may not :)
Of course, it would also mean those of us sending legitimate e-mails that get canned by these ever-more-aggressive spam filters know that someone did not receive the information they asked us for so we can do something about it.
Silent failure breaks e-mail. It is irresponsible, and the damage due to not getting a legitimate message through can be far greater than the damage due to letting a spam through (which you wouldn't be anyway, the spammer would just know they're not making it).
"v=spf1 a mx include:sendgrid.net ~all"
You can check your current one with: host -t txt yourdomain.com
Yours will likely differ based on your needs, but you need the include: for SG there.Send an email through SG to a Gmail address and check the full headers. Look for spf=pass and that they're attaching all the DKIM info.
We did a mailing to a few select people on our new mail server. For the 20 or so people using gmail that received the mailing, those who had never received an email from colin @ newdomain had the email go to spam. Those who had received a message from colin @ newdomain had the email (from a different user) in their inbox. Anecdotally, it seems gmail highly values a previous email from that domain, but only for that one recipient.
Email is tricky. We're sorting through the issues of sending from a new IP and new domain. We're learning that email sending is like a credit score. No score is as bad as a crappy one.