![]() |
|
#1
|
|||
|
|||
|
If you allow the disabling of email client protection on the setup page, the NOD32 icon should not turn orange. Many of us use webmail and don't need client based protection. IMO, this is a design flaw that is carried over from previous versions.
|
|
#2
|
|||
|
|||
|
What happens if you try to uncheck all the 'Integrate into <mail client>' in the advanced setup tree "'Web and email' -> 'Email client protection' -> 'Email client integration'"?
|
|
#3
|
|||
|
|||
|
I can disable email client protection by unchecking POP3 protocol checking. That is not the problem. The problem is offering the user the ability to disable email client protection from the setup screen and then telling them there is a problem with NOD32 when they do it. That is ridiculous.
|
|
#4
|
|||
|
|||
|
I'll inquire the developers and marketers as to why the status isn't same as in v4, ie. "%ProductName% requires your attention" like it was in v4. Other than that, the behavior is ok and pretty much same as in any previous version.
If you don't use POP3 disabling email protection will not make any difference in terms of resource usage. |
|
#5
|
|||
|
|||
|
Quote:
Essentially, this is what Eset is doing when a user chooses not to have email client checking on the setup screen and receives an error message when he does. |
|
#6
|
|||
|
|||
|
As a suggestion, if the user wants to disable email client protection from the setup screen, instead of turning the icon orange with a warning message, present the user with a popup, "Are you sure you want to disable email client protection?"
|
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|