Jump to content

filips

ESET Staff
  • Posts

    160
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by filips

  1. Hi,

    You can enable quarantine web interface to allow users manage their quarantined emails. (http://help.eset.com/emsx/6.5/en-US/index.html?idh_xmon_quarantine_web.htm)

    You can also add "Send mail quarantine reports" task in tools/scheduler, which will send reports to selected users periodically. (http://help.eset.com/emsx/6.5/en-US/index.html?idh_scheduler_task_qreports.htm)

     

  2. 1)      Please, install ESHP 6.5.15006.0, which should resolve these errors seen in the logs: „ERROR 'SHARED_MEM_ERROR', object: SharePoint Agent: Reading updated memory size of stream failed.“

    2)     BTW: You need to run the SHPIO under the same account as provided to our product. The SHPIO10 error looks like one reported when executing incorrect version (i.e. incompatible with the .NET used by the SharePoint). Did you run it from command line? Did it write anything to command line before/after the crash? Try executing SHPIO07 or 13 instead. Did it help?

    If there are still problems, please, open a support ticket and provide logs collected with ESET Log Collector.

     

  3. Hi wolflord,

    You can use mail transport rules to achieve this, e.g.:

    Conditions:
    Internal message - False
    Recipient validation result - is - Contains invalid recipients
    Recipient validation result - is not - Contains valid recipients

    Actions:
    Log to events/Drop/Reject


    I suggest to do some testing with "Log to events" or "Reject message" action for some time and check logs if the rule works correctly.

    NOTE: Drop message action has one disadvantage - if a sender makes a typo in the email address, even a valid mail will be dropped (e.g. john.doe@mydomain.com vs. jonh.doe@mydomain.com)

     

  4. Hi,

    this is probably a known issue of 4.5 - when VSAPI evaluates rules, it may use two values of sender - email address and display name. In that case the NOT operator does not work as expected.

    try something like this:
    NOT email@address.com AND NOT "display name"

    (both display name and email address used by VSAPI can be seen in log after enabling diagnostic logging)

  5. Hi jadorwin,

    this error means that automatic exclusions for IIS were not generated because our current server products do not recognize IIS 10. This will be fixed soon.

    You can add these exclusions manually to Advanced setup/Computer/Exclusions:

    The default values are:
    "c:\inetpub\logs\logfiles\*\*.log", "c:\inetpub\temp\IIS Temporary Compressed Files\*.*"
    (more info here: https://blogs.technet.microsoft.com/raymond_ris/2014/01/16/windows-antivirus-exclusion-recommendations-servers-clients-and-role-specific/)

    If you don't want to see the error in logs, you can disable Microsoft Internet Information Services under Advanced setup/Computer/Automatic exclusions

  6. Hi CraigB,

    setting "Write scan results to message headers" can only be enabled/disabled, you cannot choose any subset of messages (e.g. incomming). If these headers are causing you problems then you will have to disable them completely.

    If you still want to keep the scan results in headers, then you could create some custom rules. Something like this:

    Conditions:
    Internal message: False
    Antispam scan result: Spam

    Actions:
    Add header field: "X-MY-AS-HEADER: SPAM"
    Evaluate other rules

×
×
  • Create New...