NOD32 still insists on creating Signatures

Discussion in 'NOD32 version 2 Forum' started by ir0nx, Feb 27, 2007.

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

    ir0nx Registered Member

    Joined:
    Feb 27, 2007
    Posts:
    2
    Hello guys,

    I have the following problem:
    When I fetch mails with outlook express, NOD32 still insists on creating
    mail-footers with the message that the mail had been scanned by NOD32.
    I have switched both options in NOD32 EMON to just add check information if the EMail is infected because I dont want anny additional info if the email was not infected.
    Is there any option I have been missing for this issue ?
    My Version of NOD32: 2083 (registered)
    Screenshot is attached.

    Thanks for your help,

    Best regards,

    ir0nx
     

    Attached Files:

  2. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,722
    Location:
    Texas
    Did you check your settings in the Imon module?
     
  3. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,148
    Location:
    Denmark
    You need to turn it off in IMON too.
     
  4. ASpace

    ASpace Guest

    The screenshot is not in English but it seems it is from EMON .

    Outlook Express is not handled by EMON . EMON takes care of MS Office Outlook . You should check IMON's settings

    Please , open Control Center -> IMON -> Setup (in your language).
    "Check email confirmations" - change it to Infected mails only or to No notifications
     

    Attached Files:

  5. ir0nx

    ir0nx Registered Member

    Joined:
    Feb 27, 2007
    Posts:
    2
    Thank you very much, that did solve the problem.
    Was my bad I did think, EMON was responsible for the mail issues.

    That was FAASSST :))

    Best regards,

    ir0nx
     
  6. uc-icq

    uc-icq Registered Member

    Joined:
    Oct 28, 2006
    Posts:
    129
    Glad to see you problem solved. :thumb: I also had the same question before, thinking it would be good for ESET to move this to EMON settings in its future release
     
Thread Status:
Not open for further replies.