Jump to content

filips

ESET Staff
  • Posts

    160
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by filips

  1. Hi raimund,

    Attachment type rules are evaluated on all files in archives - zipped document with macro will be caught by the rule (unless it's password protected).

    Rules support only comparing of static strings so it is not possible to compare From: and Return-Path: headers. Not a perfect solution, but something like this should do the job:

    From Header - display name contains one of [@customer1.com, @customer2.com]
    Message headers do not match regular expression "\nReply-To: .*(@customer1.com|customer2.com)"

  2. Hi yardstudio,

    Releasing of spam from mail quarantine should work even if you don't report the false positive. The message is resent using replay directory and antispam is not evaluated again.

    If the email was marked as spam again, it means that it was routed through SMTP agent and tested for spam again - this is not the usual case. Do you have more Exchange servers in your environment? If yes can you describe routing of mail?
    Information about delivery of the message can be seen in "Received" headers (in the detail dialog) of the message that returned to quarantine. Please post the "Received" headers.

    BTW, which version of EMSX do you use?

  3. Of course you can create separate mailbox, but it's not necessary. EMSX skips scanning of emails going to the address set as quarantined mailbox in advanced setup. It should be enough to give the shared mailbox 2 addresses, e.g. info@ and quarantine@. Then set @quarantine as quarantine mailbox in advanced setup (so only emails going to @quarantine are skipped).

  4. Quote

    EMSX 4.5 will have no new Antispam Signatures as of 1. april right?

    The antispam engine will be disabled competely. We are already releasing new Mailserver module that disables the antispam engine to prevent more serious errors that could occur after April 1st.

    We prepared a KB article with details, you can find it at https://support.eset.com/kb7118/

    Quote

    Only Anti Malware right?

    Yes, anti-malware will work correctly

  5. Hi davidenco,

    "Approved Domain to IP List" and the "Ignored Domain to IP List" are used only by antispam engine

    To whitelist some IP addresses, modify the rule - create a condition "Sender's IP address is not any" and specify list of allowed IP addresses

    15 hours ago, davidenco said:

    This is affecting rules configured not just for emails coming in but also those being scanned on-demand within the database.

    Only on-demand database scan rules can affect emails while scanning with on-demand database scan, transport rules are used only when scanning by transport agent

  6. Hi,

    as marcos noted this error is logged when automatic exclusions for Microsoft SQL server are enabled. Automatic exclusions for Microsoft SQL server are using ADO API to read information from "sys.master_files" table to get list of files to exclude from scanning. The ADO API obviously loads a DLL that is not signed.

    As a workaround, automatic exclusions for Microsoft SQL server can be disabled.

  7. Hi,

    You can create a transport rule with conditions:
    From header - address contains one of {list of your domains}
    Sender's IP address is not one of {list of your IP addresses}


    If you wish to limit this rule to the finance department, then add a condition:
    Recipient's organizational units and select corresponding OUs

    and actions:
    Log to events
    Reject message/Drop message/Quarantine message

    • I'm trying to see the advantages of installing ESET using the extension...

    When deploying infrastructure using Resource Manager templates, you can reference extensions to be deployed to a VM as part of the whole process.

    If you want to install to one machine, manual install may be easier.

    Extension management interface is not very fancy, e.g. when the extension needs to reboot after upgrade/uninstall, there is no way to indicate that. It will either wait or force reboot – what can be a surprising action for admin.

     

    • Also the Azure Advisor says that there is no Endpoint Protection on the VM (said before upgraded to v7)..

    Detection of Endpoint protection is unrelated to whether the product was installed as extension or not. Currently, MS does not recognize ESET as Endpoint protection. Don't know why, we are trying to reach them.

     

    • Now v7 is here and there is no way (that I can see) to use the Azure interface to upgrade Eset file security on the VM.

    Upgrade: Extension management system does not do major version upgrades. No way to do that automatically.

    Install: Currently, clean install of v7 can be done only via PowerShell, because we need to update the portal UI to reference new major version (it references v6 now). We are working on this with MS right now, but as it is handled via emails, it takes time.

  8. Hi Dean,

    We will add import/export options to lists in rules (just like in antispam filtering lists) - these options will be available after ERA configuration module update.

    In the meantime - what is your use case?
    It's also possible to export the configuration directly in product - this will give you an XML file. This file can be modified - e.g. you can remove everything except rules, modify the list and then import the rules on other machine etc.

    It looks like you are trying to do some antispam filtering - if you have problems with antispam detection rate, you can submit samples to ESET (https://support.eset.com/kb141/#spam) or contact customer care

×
×
  • Create New...