spam on eXchange 2003
I know,... i know... we're in the process of migrating to exchange 2010.
for now.... how do I BLOCK all fake senders?? How can I fix this?
Who is Participating?
Experts Exchange Solution brought to you by
"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.
Experts Exchange Solution brought to you by
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 trialIt'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
From novice to tech pro — start learning today.
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - Word 2016 Part … 134 lessons
-
Microsoft ApplicationsCertification: IC3 GS4 Internet Core Competency Global Standard 4… 135 lessons
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - Outlook 2016 Par… 211 lessons
Experts Exchange Solution brought to you by
INTERNET --> Barracuda --> Exchange
Cloud --> Public IP --> Private IP
The Barracuda should be told to send mail to the exchange server. Nothing else should be able to reach it.
(Disclaimer - I've never worked with a Barracuda appliance, but most spam systems have a configuration to tell it where to send the mail for a given domain.
You could also adjust your firewall so that ONLY the IP of the barracuda can communicate with the Exchange SMTP server over port 25).
(Honestly, I haven't used Exchange 2003 in YEARS... it's 12 years old - you know, you know - this is one of the problems taking so long to update your network (and Exchange 2010? I like it... but if you were to move to eXchange it should be 2013 - you're shooting yourself in the foot as you'll need to do it again sooner than later).