Can't email to external email addresses

Hello Experts!

Running SBS2003 with Exchange Server 2003.
Up until last week we had T1 voice an data Internet service with Integra Telecom.
Last week we added Comcast Business Class Internet Connection for connection speed.
Last Saturday I asked Integra to modify our MX Record to point to the new IP address given to us by Comcast.

I changed the settings in my firewall to reflect the new IP address.
I tested incoming mail and it worked but did not make sure emails were reaching external recipients (my bad).
On Tuesday morning I was informed that external recipients were not getting emails.
I looked on the queue and noticed there were a bunch of emails stucked there.
I was informed by Integra that I should ask Comcast to create a PTR to, this was done on Tuesday at about 11am and the said it will take 24 for the DNS Server to populate.
Today, Wednesday 6:00pm and I still have messages getting stuck in the queque.
I did tests on and everything seems to be OK.
Besides messages getting stuck in the queue, one of my users is receiving the following message when sending messages to a particular recipient.
The following recipient (s) could not be reached: on 2/23/2011 5:01pm
You do not have permission to send to this recipient. For assistance, contact your system administrator.
< #5.7.1 smtp;550 5.7.1 Unable to relay for>

I have absolutely no more ideas on how to resolve this issue.
Your help will be greatly appreciated.

Who is Participating?

Improve company productivity with a Business Account.Sign Up

ernestopConnect With a Mentor Author Commented:

An old DNS entry from our previous provider in the virtual server properties.

Everything is working now!

Thanks Alan. I appreciate your input.
Alan HardistyCo-OwnerCommented:
Your configuration looks very RFC Compliant to me so there may be issues at the receiving end deliberately blocking you or expecting you to come in from your old IP not your new IP.  Some manually record your IP and if you stray from what they expect - they reject you.

As for the 5.7.1 error - that suggests a similar problem - the receiving server doesn't like you and you may need to contact them and get unblocked.
ernestopAuthor Commented:
Alan, thanks for your prompt response!

My Server name is zinnserv01 and I am using a SonicWALL Email Security device, its name zinnserv03. Don't know why it is coming up on this report.
Before the change everything was working fine.
I am calling SonicWALL as we have support agreement with them. Will keep you posted.

Here is the report from

smtp:     smtp    
220 zinnserv03.zinncorp.local ESMTP SonicWALL (

 OK - resolves to
 Warning - Reverse DNS does not match SMTP Banner
 0 seconds - Good on Connection time
 Not an open relay.
 0.320 seconds - Good on Transaction time

Session Transcript:
250 zinnserv03.zinncorp.local [48 ms]
250 2.1.0 OK [48 ms]
550 5.7.1 Unable to relay for <> [48 ms]
221 2.0.0 Bye [48 ms]
reverse lookup smtp diag port scan blacklist

Reported by on Wednesday, February 23, 2011 at 5:35:21 PM (GMT-6)  (History)     mx    

Pref Hostname IP Address TTL  
10 24 hrs SMTP Test Blacklist Check
20 24 hrs SMTP Test Blacklist Check
dns lookup ns lookup mx lookup whois lookup

Reported by on Wednesday, February 23, 2011 at 5:34:52 PM (GMT-6)

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

ernestopAuthor Commented:
Spoke with SonicWALL support.
zinnserv03 is a server that is running the email security software. It scans incoming mail before passsing it to the email server zinnserv01.

The line that concerns me from the mxtoolbox report is:
Warning - Reverse DNS does not match SMTP Banner
Don't know how to fix that.
Any suggestions?
thanks again in advance for all your input.
Alan HardistyCo-OwnerCommented:
Okay - the Reverse DNS does not match SMTP Banner can be resolved by changing the FQDN on your server.  (I missed that - Sorry).

Open Up Exchange System Manager and expand Protocols> SMTP> Right-Click on SMTP Virtual Server and choose Properties.

On the Delivery Tab> Advanced Button, change the FQDN fom zinnserv03.zinncorp.local to

The rest of your configuration looks fine.
ernestopAuthor Commented:

The FQDN has been there all along. That was one of the first things I double checked as per a post on the

So, that looks good. PrintScreen of FQDN
Was on the phone with Integra last night and they said everything looks good on their end (I have only talke to them and Comcast like 10 times!!!)
ernestopAuthor Commented:
One more clarification piece:

zinnserv03 is a server running SonnicWALL mail security software.

Inbound email gets routed from my SonicWALL firewall to server "zinnserv03" where messages are scanned and then junked or sent to my SBS2003 Server "zinnserv01".

Inbound emails are reaching the Outlook clients. It is the outbound emails that are either queued up or rejected.

ernestopAuthor Commented:
Digged more into the properties of the virtual server.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.