Note that your SPF record fails - putting us users at risk of being labeled as spam, since infusionmail.com is not permitting the "reply to/from" domain to be a sender ... doh. Why bother to have an SPF record at Infusionmail.com? With so many different user domains, you couldn't possibly add them all or keep up.
Here is a snippet from the header (where 18.104.22.168 is my server IP for the reply-to/from domain):
Received-SPF: fail (google.com: domain of firstname.lastname@example.org
does not designate 22.214.171.124 as permitted sender) client-ip=126.96.36.199;
Authentication-Results: mx.google.com; spf=hardfail (google.com: domain of email@example.com
does not designate 188.8.131.52 as permitted sender) firstname.lastname@example.org
Please explain a more suitable method asap.
"1.7 URIBL_BLACK Contains an URL listed in the URIBL blacklist
Please have Infusionsoft.com removed from the blacklist AND ... in your email templates you have a spam checker. Please ensure this spam checker FLAGS the Infusiosoft.com spam score as above - this is deceptive to users thinking we have managed to achieve a rating below the magic "5" when your own url is adding another 1.7.