Spam Protection of Email - Exchange 2010 - SBS 2011

Hi All.

We have recently moved our company over to SBS 2011 Standard (great product) however under our security TAB there is an entry - Spam Protection for e-mail - Critical.

We HAD (we no longer have it) - Microsoft Forefront as our Email Spam Protection program - and was removed in preference for Symantec Mail Security for Microsoft Exchange.

(Briefly - we trialled MS Forefront to see what it was like but already had the Symantec suite paid for - so when the MS forefront trial ended we removed it and then installed Symantec Mail.)

The problem did not exist when we had MS Forefront as we changed the 'E12AntiSpam.xml' file to refect the change to - '$(Get-TransportAgent "FSE Content Filter Agent").Enabled' - however since removing MS Forefront the problem has returned.

I HAVE changed the 'E12AntiSpam.xml' file back to its original code and restarted the server but to no avail.

Am I right in thinking that somehow we need to tell Exchange 2010 that Symantec Mail Security is looking after the spam as we did for MS Forefront - or am i missing something more fundamental here?

I have enabled anti-spam on the Exchange server and is showing in the Exchange management console - 'Organisation Configuration - Hub Transport - Ant-Spam' - content filtering IS enabled.

Can anyone please throw any light onto this issue please.

Thank you
Andy Keen - Mersey-IT
Who is Participating?
AndyKeenConnect With a Mentor Author Commented:
Hi All.

Thank you for your help - in the end I decided to try and bottom this issue myself and did so.

The resolution in the end was not that difficult - just needed some logical detective work.

For this reason I have attached the solution as a PDF document.

I hope it help those who have this same issue.
Unfortunately you were not wised up to not installing the Forefront trial in the first place.
Most M$ MVP's advise against it because it's a pain to remove and causes issues just like this.
And to top it off ,Forefront is no longer being sold.

Wish I could be of more help.
Removing forefront is a right pain...

Try deleting/renaming the FSE.xml file from C:\Program Files\Windows Small Business Server\Data\SHExtensions. I know that worked on 2008 but havent tried it on 2011.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

AndyKeenAuthor Commented:
Hi totallytonto.

Thank you for the help - I will try that shortly and update you.
AndyKeenAuthor Commented:
Other solutions provided did not resolve the problem - so I decided to look into it further myself and resolved the issue.

As a result I included the resolution as a PDF document.
AndyKeen - That worked, been fighting for a few weeks now.  THANK YOU!
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.