[Simon Lloyd]

Ok, firstly the SMTP greeting has issues

Malformed greeting or no A records found matching banner text for following servers, and banner is not an address literal. RFC5321 requires one or the other (should not be a CNAME). If this is not set correctly, some mail platforms will reject or delay mail from you, and can cause hard to diagnose issues with deliverability. Mailserver details:

109.201.138.227 | WARNING: The hostname in the SMTP greeting does not match the reverse DNS (PTR) record for your mail server. This probably won't cause any harm, but may be a technical violation of RFC5321

The SPF record has this

"v=spf1 a mx -all"

use this tool to create yours http://www.spfwizard.net/ and go for a soft fail. And finally if you are not on dedicated serevr ask your hosts to fix your SOA record

One or more SOA fields are outside recommended ranges. Values that are out of specifications could cause delays in record updates or unnecessary network traffic. The SOA fields out of range are:

serial | 2016258234 | SERIAL - we check that your serial number matches the recommended format found in RFC1912 section 2.2.
expire | 604800 | EXPIRE - RFC1912 suggests a value between 1209600 to 2419200.

You may want to add address literals too

Mailserver rejected mail to address literals. Mailservers are technically required by RFC1123 section 5.2.17 to accept mail to domain literals (i.e. IP addresses instead of domains). This ensures backwards compatibility and can help with delivery in certain non-optimal situations, like a DNS server being down/unresponsive.

109.201.138.xxx | unexpected response to [RCPT TO: ] | 501 : domain literals not allowed

--------------- Added [DATE]1411107133[/DATE] at [TIME]1411107133[/TIME] ---------------

Your ip is listed as spam here DDNSBL, go here to get it removed from the list http://v4bl.org/