Relaying denied. IP name possibly forged

Hello,

I know this has been discussed in several different posts but I'm still having an issue.
Yesterday I moved my server, which changed th IP. I immediately updated my DNS lookup table.
I use google apps for our mail so I did not change the mail records.
Today I've been trying to restart a java application that sends out periodic email.

Because of the server change I've moved I'm using an ouside smtp mail server (unlimitedmail.org)
 
This is the error I'm getting when I run the app, specifically when I try to send mail.
Relaying denied. IP name possibly forged [xx.xx.xx.xx]

Is this happening because my DNS records have not been completed updated?
Is it another issue?

I generated a DNSReport
The only red flags that come up are stealth nameservers not existing, is this the issue?
Error below
FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNSreport will not query these servers, so you need to be very careful that they are working properly.

ns3.everydns.net.
ns4.everydns.net.
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).

This is the data that came out of zmailer

MX-VERIFY-CGI run for ``www.mydomain.com''

Doing resolver lookup for T=MX domain=``www.mydomain.com''
Questionable: NO MX DATA: domain=``www.mydomain.com'' We SIMULATE!
Do have at least one MX entry added!

Testing MX server: www.mydomain.com

Address lookup did yield following ones:

  IPv4 xx.xx.xx.xx

Testing server at address: IPv4 xx.xx.xx.xx

[ CONNECTED! ]

 220 mail.mydomain.com ESMTP
 EHLO z2.cat.iki.fi
 250-mail.mydomain.com
 250-AUTH LOGIN CRAM-MD5 PLAIN
 250-AUTH=LOGIN CRAM-MD5 PLAIN
 250-STARTTLS
 250-PIPELINING
 250 8BITMIME

Excellent! It speaks ESMTP!

 MAIL FROM:<>
 250 ok

Fine, it accepts NULL return-path as is mandated by RFC 2821 section 6.1

 RSET
 250 flushed
 MAIL FROM:<postmaster@z2.cat.iki.fi>
 250 ok
 RCPT TO:<postmaster@www.mydomain.com>
 250 ok


Apparently OK!


Thank you for your helpStart Free Trial