Email "tag" line: How to get rid of?

Discussion in 'NOD32 version 2 Forum' started by mingus, Oct 13, 2003.

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

    mingus Registered Member

    Joined:
    May 21, 2003
    Posts:
    20
    I'm trying out Nod32 again. Still have a few issues and have not figured out how to get rid of the email tag line:

    __________ NOD32 1.533 (20031011) Information __________

    This message was checked by NOD32 Antivirus System.
    http://www.nod32.com
     
  2. minacross

    minacross Registered Member

    Joined:
    May 12, 2002
    Posts:
    657
    Go to IMON >> Setup >> Append notification to emails
    then choose what is proper for you :)
     
  3. minacross

    minacross Registered Member

    Joined:
    May 12, 2002
    Posts:
    657
    check this snapshot ;)
     

    Attached Files:

  4. Dan Perez

    Dan Perez Retired Moderator

    Joined:
    May 18, 2003
    Posts:
    1,495
    Location:
    Sunny San Diego
    Actually, I believe the tagline that can be disabled in the IMON settings specifies that it is NODs IMON that added it. This one looks like the one added by EMON which cannot be disabled. I've tried uninstalling , removing all reg entries (that clearly pertain to NOD) and the NOD folder tree and then reinstalling and deselecting having EMON alter clean emails but it does no good. A couple of queries here regading this didn't turn up anything then but hopefully someone will have some input now on this.

    It's kind of annoying since it alters digitally signed emails so that, depending on the form of authentication, the email's author can't be verified.
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Hi mingus,

    in case you use EMON for checking incoming email and wish to disable appending certifiaction messages, please contact the NOD32 technical support at support@nod32.com to obtain the appropriate registry files that, after being imported to the registry, will disable that feature.

    This bug will be fixed in the following program component update.
     
Thread Status:
Not open for further replies.