Submission of Suspicious Files Disabled ???

Discussion in 'ESET NOD32 Antivirus' started by MarcR, Aug 18, 2009.

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

    MarcR Registered Member

    Joined:
    Nov 3, 2006
    Posts:
    60
    I tried to send a false positive file in my quarantine and I received the following error from NOD32:

    The submission of suspicious files is currently disabled. It has been added to the queue.

    What does this mean and why is it happening?
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    I have no clue why it's happening, but if you want to submit a potential FP follow these instructions. Also let us know more details about the file, such as the file name and the threat which is reported.
     
  3. MarcR

    MarcR Registered Member

    Joined:
    Nov 3, 2006
    Posts:
    60
    Thanks, Yes, I used that method and I got a reply from Eset. File was infected due to a infected compiler the publisher used. I downloaded a new version of the program and it's clean now.

    Anyway, I sent an email to Eset about this message:

    The submission of suspicious files is currently disabled. It has been added to the queue.


    Anyone else have any info on this?
     
  4. MarcR

    MarcR Registered Member

    Joined:
    Nov 3, 2006
    Posts:
    60
    Last edited by a moderator: Aug 18, 2009
  5. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    I had this problem when threatsense.net was unchecked in advanced setup. You definitely want to go there, if you have not checked allready. In addition, that is where the queue is and the settings to be able to send the file immediately, depending on what the parameters are set at.
     
  6. MarcR

    MarcR Registered Member

    Joined:
    Nov 3, 2006
    Posts:
    60
    Yes, I have threatsense turned off - that explains it.

    I just email the files when the need arises.

    Thanks.
     
  7. MarcR

    MarcR Registered Member

    Joined:
    Nov 3, 2006
    Posts:
    60
    One final comment from Eset on the subject:

    ~Private communication removed per the Terms Of Service.~
     
    Last edited by a moderator: Aug 18, 2009
  8. MarcR

    MarcR Registered Member

    Joined:
    Nov 3, 2006
    Posts:
    60
    I have found that this error can be caused by the eset servers being down for maintenance. In addition, I have learned that Eset prefers the email method for submitting false positives as discussed earlier in this thread.
     
Thread Status:
Not open for further replies.