Exchange Exclusions

Discussion in 'Other ESET Home Products' started by thenoble06, Sep 20, 2007.

Thread Status:
Not open for further replies.
  1. thenoble06

    thenoble06 Registered Member

    Joined:
    Aug 15, 2006
    Posts:
    25
    As a user of XMON - I am interested to learn if I had to set up exclusions for XMON/AMON etc on our Exchange server - or whether NOD32 is Exchange aware enough to set the exclusions up automatically?
     
  2. YeOldeStonecat

    YeOldeStonecat Registered Member

    Joined:
    Apr 25, 2005
    Posts:
    2,345
    Location:
    Along the Shorelines somewhere in New England
    You need to manually set them in AMON exclusions.
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    AMON in NOD32 for Exchange already has the required file extensions excluded.
     
  4. thenoble06

    thenoble06 Registered Member

    Joined:
    Aug 15, 2006
    Posts:
    25
    Marcos - I was under that impression as well. But AMON yesterday detected a J/Loop trojan in the Mailroot directory (blahblah.eml file). I thought this directory should not be scanned (according to Microsoft in one of there TechNet articles).
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Do you have XMON 2.71 installed? If so, could you check the extension list if eml extension is there?
     
  6. thenoble06

    thenoble06 Registered Member

    Joined:
    Aug 15, 2006
    Posts:
    25
    We run 2.7 of NOD32, I'm not sure what the exact version of XMON is (how do I find out?)

    And as for the extensions that are scanned by XMON - the tick box for Scan All Files is ticked under the extensions tab.

    In AMON - the .eml extension is on the inlcuded list of extensions to be scanned.
     
Thread Status:
Not open for further replies.