Question : Relaying denied. IP name possibly forged.  PLEASE HELP

I've done research on this site regarding this problem, and seen a few of the conversations about it.  I thought I had it figured out, but I still get:

=======================================
Reporting-MTA: dns;myMailServerName.myDomain.local

Final-Recipient: rfc822;outsideEmailAddress@something.com
Action: failed
Status: 5.7.1
Diagnostic-Code: smtp;550 5.7.1 hing.com>... Relaying denied. IP name possibly forged [65.xxx.xx.xx]
=======================================

I have updated my public DNS records so that I have these relevant entries:
(1) myMailServerName.myDomain.local         IN      A       65.xxx.xx.xx
(2) 65.xxx.xx.xx                                           IN      PTR     myMailServerName.myDomain.local.

I can only say that this problem is driving me ultimately insane.  We send email out directly from our Exchange 2003 server, but our incoming email is routing through a filtering service first.  So, our MX records point to this filtering service's names/IPs and not ours.  Maybe this is causing some of the difficulty??

Any input on a resolution to my problem would be great appreciated.  Thanks.

Answer : Relaying denied. IP name possibly forged.  PLEASE HELP

Having .local in your PTR records is useless. That domain is not valid for the internet so the name cannot be resolved.
You can only use valid internet domains.

If your email is filtered by a third party, then you really should route your outbound email through them, at least as an interim measure.

Ask whoever hosts your domain name to setup a new host for your Exchange server - outbound.domain.com or whatever.
Then get the reverse DNS setup correctly for that public name.

http://www.amset.info/exchange/dnsconfig.asp

Simon.