Jump to content

filips

ESET Staff
  • Content Count

    139
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by filips

  1. 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
  2. filips

    eset mail security

    Hi, you can create transport rules to block messages by subject or by message body, but you have to specify the blocked words manually
  3. 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.
  4. 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
  5. Hi, We managed to reproduce the issue - the problem is that Database scan task scheduled in policy is not created correctly. A workaround exists: When you create a scheduled Database scan task in ESMC, click edit and go through the wizard again. When you click finish the task should be saved correctly. The issue will be fixed in configuration module for ESMC
  6. Hi davidenco, thank you for your suggestion. We added this improvement to our backlog.
  7. Please ignore that sentence, of course you don't need Hyper-V
  8. There seems to be a problem when the database scan is scheduled in ESMC policy - we will investigate it I didn't know you were using ESMC - to schedule a scan from ESMC, you can use Client tasks/Server scan (https://help.eset.com/esmc_admin/70/en-US/dashboard.html?client_task_server_scan.html). But you have to enable sending of scan targets to ESMC first: https://help.eset.com/emsx/7.0/en-US/idh_config_era_targets.html This is the most up to date option and it gives you the ability to select mailboxes/public folders just like in EMSX.
  9. Hi davidenco, you can try enabling Diagnostic logging (Menu->Setup->Tools) for a minute and run the Database scan. Then check "Events" log to get more information.
  10. This issue should be fixed in ESET Mail Security for Microsoft Exchange Server version 7.0.10020.0
  11. I updated the answer - there was a problem with encoding of some characters...
  12. Hi davidenco, The error in logs is caused by an exception while parsing "Received:" headers. We will address the issue in next hotfix of EMSX. Could you PM me a procdump file(s) capturing the exception? It would help us to track it down: procdump -ma -e 1 -f "nullreferenceexception" edgetransport.exe
×