Spam Filter/Restricting SMTP Traffic

We use a third party spam filter called Postini.  All of our inbound and outbound traffic goes through this company's servers.  Our MX record points to them, they filter and send the mail to us.  In their setup instructions, it states that I need to lock down my e-mail relay to restrict inbound SMTP traffic to ONLY their server's IP addresses.

I am very familiar on how to set the relay restrictions in Server 2003 with Exchange 2003 but now we are using Server 2008 Standard with Microsoft Exchange 2010 installed.

I can't find anyone who knows how to do that in Exchange 2010 with a Hub Transport.
qualityipAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

shauncroucherCommented:
It is in the receive connector.

Exchange Management Console --> Server config --> Hub transport --> Receive connector.

Select the one for inbound mail and go to network and then remote IP ranges, set to only those ranges specified.

Shaun
shauncroucherCommented:
See here for background info: http://technet.microsoft.com/en-us/library/aa996395.aspx

If it the remote network settings section.

Shaun
qualityipAuthor Commented:
Okay, perfect. I had it configured properly but we keep receiving tons of 400 errors.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

shauncroucherCommented:
400 is a transient failure. What do you mean that you are receiving 400 errors? Do you mean when sending outbound mail or are you seeing these in the queues on exchange?

Shaun
qualityipAuthor Commented:
The issue was resolved. The error was occuring because we had an old alias domain configured in Postini. The e-mail to that domain was accepted into our network as it was coming from Postinibut Exchange 2010 was not configured to accept e-mail from the domain. The 400 errors were a result of the bounceback messages after our Exchange server declined to relay the e-mail.
shauncroucherCommented:
It's odd that 400 errors were generated, was there any description with the error? Usually not able to relay is a 5xx (usually 5.1.7)

Shaun
qualityipAuthor Commented:
We originally noticed undeliverable 400-error messages in our outgoing message logs in Postini:

2010/05/10 05:47:18      
IP: ---
IPOrg:100149868      
User:0      
Org:100149868      
Recipients:team@m1.constructiondeal.com      
Header:754      
Size:14743      
Disposition:f      Subject:Undeliverable: New Job: Carport Construction in Hudson
Capture.JPG
shauncroucherCommented:
Glad you got it fixed,

Shaun

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.