This message is an automatic response from Port25's authentication verifier service at verifier.port25.com. The service allows email senders to perform a simple check of various sender authentication mechanisms. It is provided free of charge, in the hope that it is useful to the email community. While it is not officially supported, we welcome any feedback you may have at <email@example.com>.
Thank you for using the verifier,
The Port25 Solutions, Inc. team
Summary of Results
SPF check: neutral
DomainKeys check: neutral
DKIM check: neutral
Sender-ID check: neutral
SpamAssassin check: ham
yes you didnt come up as spam (1.5 is kinda high though) HAM is good.
you don't have anything above configured based on the results tho - they would say passed instead of nuetral. some mail server are very strict and require additional checks before they receive mail - i am betting that is what your problem is.
also, one peice of advice. im not sure the exact location off the top of my head in exchange 2003. but change your FQDN that your exchange server responds with from helo mesages to mail.yourdomain.com instead of exchangesrv.yourdomain.com
this way everyone doesnt know your internal mail servers fqdn.
in 2010 it is under server config, hub transport, receive connectors. just go to the propertys and you will see the fqdn
Changing the FQDN announcement as you suggested solved the problem...I sent a test mail to the contact who couldn't recieve anything from us, and then I looked in the queue...nothing hung up! Then he replied back! Solved!