Jump to content

Marcos

Administrators
  • Posts

    36,228
  • Joined

  • Last visited

  • Days Won

    1,441

Posts posted by Marcos

  1. You can report email messages incorrectly evaluated by the ESET Antispam as spam according to the instructions at https://support.eset.com/en/kb141. You can also attach the email in the eml or msg format here if you would like me to check it out. Attachments are available to ESET staff only.

    Submit spam or spam false positives
    Submit emails in .eml or .msg format

    For ESET to process your submission, it must be included as an attachment in .eml or .msg format. Email sent in a different format cannot be processed.

    In Microsoft Outlook, drag an email to your desktop to export it as a .msg file. If you use a web-based email client, consult their help resources for instructions to export your mail.

    • Email incorrectly marked as spam: If you received an email message classified as spam by your ESET product, and you do not recognize it as spam, send an email to nospam@eset.com with the original message as an attachment in .eml or .msg format.
    • Undetected spam: If you received an email message that you classify as spam, but your ESET product did not classify it as spam, send an email to spam@eset.com with the original message as an attachment in .eml or .msg format.
    If you are using ESET Cloud Office Security, use dedicated email addresses nospam_ecos@eset.com and spam_ecos@eset.com to report false positive (FP) / false negative (FN) detections for spam. For detailed instructions, see ECOS Online Help.
  2. I've found a similar support ticket where developers concluded that:

    Provided logs show that the customer incorrectly tried to use software install task to upgrade Agent first. That is not possible as it will cause Agent service to be stopped by the installer. Agent will then properly shutdown and stop any ongoing installations including its own upgrade.

    Agent must be only upgraded through Upgrade infrastructure task and its output is logged into 'ra-upgrade-agent_*.log' file that is first placed at 'C:\Windows\Temp\' and then moved into Agent logs directory.

    Could you please confirm that agent upgrade via an ESET PROTECT component upgrade task is failing?

  3. 10 hours ago, QuickSilverST250 said:

    I have some apk files i want to check but to exceeds the limit so will email a wetransfer link for them

    Is it detected by other vendors or it exhibited suspicious behavior when you installed the application? It is not that an arbitrary file can be submitted and it will be analyzed by humans. We need to know what makes the file suspicious to you. Moreover, if only a link is submitted the file cannot be pre-processed automatically for analysts.

×
×
  • Create New...