Sonicwall - Spam Filter - Exchange Interaction

Dang it!  IPs are mixed up... here's the right setup.

Sonicwall              :::               Barracuda                 :::              Exchange Server
x.x.x.253                                 x.x.x.200                                     x.x.x.210

Definitely a few moving parts.
Did e-mail, both in and out, work with the Exchange server through the firewall PRIOR to you "rerouting" the incoming mail?
If not, I would take the Barracuda out of the equation until you have the basics diagnosed/fixed.
If it DID work before the rerouting, I would look at how the Exchange server, filter and firewall "point" SMTP traffic to make sure it all matches up. Since Exchange "thinks" it is sending, I wonder if the traffic is being "black holed" by the filter or the firewall.
 - Tom

If SMTP worked prior to the reroute, I would look at the firewall first.
On my larger networks, I DISABLE outbound SMTP unless it originates from authorized servers (in case someone is able to somehow install malware that attempts to spam). On a SonicWALL, I normally devine an Address Object, "Internal Mail Servers", and only allow outbound traffic from that object.
However, if you did something similar, but the object is just a single host instead of a group, then the firewall would drop the SMTP traffic unless you also redefined the host object as being the Barracuda.
 - Tom

@Tom: This question was spawned from the question below after I helped him setup the sonicwall.  Just helping complete the picture.

https://www.experts-exchange.com/questions/26279484/Sonicwall-Setup-for-Exchange-2010.html

Thanks all and digi for hanging in.  More info.  This is a new domain that has never rcvd or sent email externally or internally.  The hope was that I could somehow get things verified working before unleashing the www on the exchange server.  Here is a thought.  The external new domain is being forwarded to the current working domain that is hosting pop mbxs.  I worry that this new domain is visible to the LAN dns and is complicating my efforts.  Thoughts are to point the new domain mail traffic into the public ip and not forward it to the existing domain thereby isolating it from the current www that hosts the pop mail.  The idea is to eliminate the pop mbxs once the new domain is functioning properly.  Late here in California.  Will pick up tomorrow morn.   Thanks again to all interested parties.  Stay tuned.

For those following this thread :::

I have removed the spam filter in an effort to minimize parametric difficulties; a.k.a., too many cooks in the kitchen.  I am going to make sure the exchange server is working with the new domain first before adding the spam filter back into the equation.  I have pointed the new domain to the WAN static IP and have dropped all the email config's from the Sonicwall.  I am going to recreate the email services using the Sonicwall Public Service Wizard pointing it at the exchange server for now.

MOD :::  Appreciate the open Q until resolved.  Maybe it will be beneficial to have the result eventually.  Should be in a couple days.  Thanks.

fingers crossed...i'm sure you'll get it.  stepping back is usually the best first step to resolution.

Sounds like a plan.
With a clean and tested setup on the SonicWALL, it is pretty easy to tweak the Address Objects to redirect to the Barracuda.  I've done it a few times and it was fairly easy.
I would like the Q left open pending your progress too.
Good Luck,
 
Tom

OK folks...the next installment is here.  I have managed to use the Sonicwall wizard to setup the public service for Exchange.  I have had the new domain pointed at the WAN IP for several days now.  I can telnet to the IP and get a response from the server on port 25.  I get ESMTP MAIL Service ready...  

I am testing send receive traffic from the new domain as I write this but wanted to post something in light of the EE prompt to continue the question.  More very soon.

great...thanks for the update!

Reference Thread:  https://www.experts-exchange.com/questions/25065088/Exchange-Receive-Connector.html

This person had the same type of problem so I followed all the screen shots that lead to the successful outcome BUT..there is always a but...  I get this response from the domain when sending mail from the outside to the new domain:

SMTP error from remote mail server after RCPT TO:<recipient@domain.org>:
    host mail.domain.org [x.x.x.196]: 550 5.7.1 Unable to relay

This, by the way, was the response I got tfrom the Barracuda Spam Firewal when it tried to verify installation by sending a message to Barracuda.  I may have mentioned that earlier.

From this great little test website from MS ::: https://www.testexchangeconnectivity.com

Result :::

Testing Inbound SMTP Mail flow for domain voviedo@woodwardpark.org
  Failed to test inbound SMTP mail flow.
   Test Steps
   Attempting to retrieve DNS MX records for domain woodwardpark.org
  One or more MX records were successfully retrieved from DNS.
   Additional Details
  MX Records Host mail.woodwardpark.org, Preference 0
 
 
 Testing Mail Exchanger mail.woodwardpark.org.
  One or more SMTP tests failed for this Mail Exchanger.
   Test Steps
   Attempting to resolve the host name mail.woodwardpark.org in DNS.
  Host successfully resolved
   Additional Details
  IP(s) returned: 99.3.111.196    :::  THIS IS CORRECT - jdfuller
 
 Testing TCP Port 25 on host mail.woodwardpark.org to ensure it is listening and open.
  The port was opened successfully.
   Additional Details
  Banner Received: 220 WPBCDC01.WPBC.local Microsoft ESMTP MAIL Service ready at Tue, 29 Jun 2010 16:21:59 -0700   ::: THIS IS ALSO RECEIVED VIA TELNET - jdfuller
 
 Attempting to send test email message to voviedo@woodwardpark.org using MX mail.woodwardpark.org.
  Delivery of the test message failed.
   Additional Details
  Server returned status code 550 - Mailbox unavailable. The server response was: 5.7.1 Unable to relay
Exception details:
Message: Mailbox unavailable. The server response was: 5.7.1 Unable to relay    :::  The mailbox SMTP Email address is correct and is on the users Exchange Account profile tab - jdfuller
Type: System.Net.Mail.SmtpFailedRecipientException
Stack trace:
at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()
 
Does this help anyone?
 
 
 
 

FIXED!!!  I found there was NO "Accepted Domains" other than the .local in the Exchange Managemenet Console/Org. Config./Hub Transport.  Why doesn't the install make one!  The default domain was given at the time of install.  I didn't think of this at all.  I only found it by picking at one tab at a time and validating its settings by reason.

Once the new domain was added as an Accepted Domain, BINGO!! the  receive started working for all recipients.

PROBLEM:  I still can't send!  I created a Send Connector to IP range 0.0.0.0-255.255.255.255.  This did not seem to help.  Do I need it?

BTW :::  The client shows the mail is Sent and it is in the Sent folder but no bounce and no inidcation that it went out.

digi ::: Did you see the comment I made above yours?  I made one but I admit the IP address range I put was 0.0.0.0-255.255.255.255 and don't include subdom's.  I am changing it now and test.  Hang one...

yeah...i saw that...thought the IP was wrong...fingers crossed.

digi ::: You got it.  I guess 0.0.0.0-255.255.255.255 isn't a valid IP range?  What gives?  That changed and the one I found about the "Accepted Domains" did the trick.  Thanks for hanging in there with me to figure this out.  I wish there were more points to award you.   Tom got me started an the right track while I was fumbling with the Barracuda so I have to give there, too.

I'll be on the Send/Receive Error next ater I put the Barracuda back on line.  I guessing they'll be more points to award in those two areas.  Keep an eye on my Author name.  I seem to ask more than I answer but maybe that will change in time.  You guys rock.

Goes to show, team work - works!  Thanks.  Best money ever spent.

no problem...i think my wife wishes i'd never heard of it!!

Glad we could help and thanks for the points!  I'll keep my eye for your next question...

Ditto!  :o)