Risorse per professionisti IT > Home page del forum > Forefront Security for Exchange Server > Should I disable the builtin Exchange antispam functions after intsalling FSE 2010?
Formula una domandaFormula una domanda
 

Con rispostaShould I disable the builtin Exchange antispam functions after intsalling FSE 2010?

  • lunedì 23 novembre 2009 10.49Trond Hindenes Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    Hi,
    We have a Exchange 2007 (SP1) system, and before installing FSE 2010 we just used the builtin exchange antispam functions (installed on the hub servers, as we don't use edge servers). My question is: After installing FSE2010 on our hub servers, should I disable the Exchange antispam functions? I can't seem to find any info on how to configure this...

Risposte

Tutte le risposte

  • martedì 24 novembre 2009 5.08Nick Gu - MSFTMSFT, ModeratoreMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    Hi,

     

    Thank you for the post.

     

    As far as I know, Spam filtering can be disabled by clicking the Disable Antispam Filtering button in the Antispam – Configure pane of the Forefront Protection 2010 for Exchange Server Administrator Console. For more information, please refer to the following link.

     

    http://technet.microsoft.com/en-us/library/dd639368.aspx

     

    Regards,


    Nick Gu - MSFT
    •  
  • martedì 24 novembre 2009 8.10Trond Hindenes Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    Hi,
    Not exactly what I meant,

    What I wonder is: After ForeFront is installed, I basically have two sets of antispam agents, the builtin exchange ones, and the ForeFront ones. I need to know if it's considered a best practice to turn off the builtin ones and leave antispam "washing" up to ForeFront, or if i need to leave the excahnge builtin ones enabled also?
  • martedì 24 novembre 2009 17.48Tal Holt Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    I have the same questions. This guy is a master at saying nothing. 

    Simple question.  Does the built in antispam filtering enabled through Install-antispamagents.ps1 on Hub transport role need to be enabled or disabled with the install of Forefront Security for Exchange.

    As of right now I have been unable to install forefront 2010 on my Hub Transport Servers due to errors in the Forefront Installation process.  There is a problem with the FSE agent registering with Exchange Transport.

    I hope someone here starts looking into this stuff without just unthinkingly making useless statements.
  • giovedì 26 novembre 2009 5.52Nick Gu - MSFTMSFT, ModeratoreMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Con risposta

    Hi,

     

    Thank you for the update.

     

    After installing Forefront during the setup we disable the Exchange’s Content Filter.  The rest of Exchange filters will stay in the state it was before Forefront setup.  Please do not re-enable Exchange content filter.  Also, after installing Forefront you will now manage Exchange filters via Forefront UI.  Please read the whitepapers we have for the product, here are the links:

     

    Forefront Protection 2010 For Exchange Server Antispam

    Forefront Protection 2010 for Exchange Server

    Forefront Protection 2010 for Exchange Server Scan Actions And Sequence

    Monitoring Forefront Protection 2010 for Exchange Server

     

    Regards,


    Nick Gu - MSFT
  • lunedì 7 dicembre 2009 14.14atcnf2008 Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    Thank Nick, 

    I have  read all these  docs  you have listed  here.    I have  disabled Content Filtering on Edge Server and  use  FPE 2010 antispam and  I saw  mails  are rejected  messages like "Message rejected due to content restrictions" in FSE log,  here  I have   more questions, please  give us specific answers.
    #1:  Regarding  Antispam updates on Exchange Build-in engine,   I have looked its update since RC1 and nothing changed since  Sep 2009,  is it  supposed  to be so or do I miss something here?    the Event Log shows  Exchange does check antispam updates  every 30 Mintes, like  "Information 12/7/2009 8:16:00 AM MSExchange Anti-spam Update 1005 Update Service ",  just  nothing is installed.  On  contrast, Exchange 2007 built-in engine updates its spam definition  copule of times  a  day, please tell me why this  antispam update never happens...
     
            [PS] C:\Windows\system32>get-antispamupdates


    UpdateMode                  : Automatic
    LatestContentFilterVersion  : 3.3.4604.600
    SpamSignatureUpdatesEnabled : True
    LatestSpamSignatureVersion  : 3.3.4604.600
    IPReputationUpdatesEnabled  : True
    LatestIPReputationVersion   : 3.3.4604.001
    MicrosoftUpdate             : Configured

     

    [PS] C:\Windows\system32>


    #2: Are these  functions  duplicated or  different?  the Build-in spam engine has  Sender ID/Sender Filter/Recipient Filtering/IP allow list/IP block list, FSE2010 have almost the same things, do we need keep both of them?  SenderIP reputation is only listed on  Build-in engine side but if we  get NO updates for Exchange 2010, is it still useful?

    Please  be more specific  for  your answers, I do appreciate your help.  Thank you