The protection scope refers to the objects that the component scans during its operation. The protection scopes of different components have different properties. The properties of the protection scope of Mail Anti-Virus include the settings of Mail Anti-Virus integration into mail clients, and the type of email messages and the email protocols whose traffic is scanned by Mail Anti-Virus. By default, Mail Anti-Virus scans both incoming and outgoing messages and traffic via the POP3, SMTP, IMAP, and NNTP protocols, and is integrated into the Microsoft Office Outlook application. The Mail Anti-Virus extension is embedded in the Microsoft Office Outlook mail client during installation of Kaspersky Security.
To create the protection scope of Mail Anti-Virus in Kaspersky Security Center:
Open Kaspersky Security Center Administration Console.
In the Managed devices folder of the console tree, open the folder with the name of the administration group to which the relevant protected virtual machines belong.
In the workspace, select the Policies tab.
Select a Light Agent for Windows policy in the list of policies and open the Properties: <Policy name> by double-clicking.
In the policy properties window, select the Mail Anti-Virus section in the list on the left.
In the right part of the window, in the Security level section, click the Settings button.
In the Mail Anti-Virus window that opens, on the General tab, in the Protection scope section, do one of the following:
If you want Mail Anti-Virus to scan all incoming and outgoing messages on the protected virtual machine, select the Incoming and outgoing messages option.
If you want Mail Anti-Virus to scan only incoming messages on the protected virtual machine, select the Incoming messages only option.
If you choose to scan incoming messages only, you are advised to perform a one-time scan of all outgoing messages because there is a chance that the protected virtual machine has email worms that use email to spread. This helps to avoid unmonitored mass emailing of infected messages from the protected virtual machine.
In the Connectivity section, do the following:
If you want Mail Anti-Virus to scan messages that are transmitted via the POP3, SMTP, NNTP and IMAP protocols before they arrive on the protected virtual machine, select the POP3 / SMTP / NNTP / IMAP traffic check box.
If you do not want Mail Anti-Virus to scan messages that are transmitted via the POP3, SMTP, NNTP and IMAP protocols before they arrive on the protected virtual machine, clear the POP3 / SMTP / NNTP / IMAP traffic check box. In this case, messages are scanned by the Mail Anti-Virus extension that is embedded into the Microsoft Office Outlook mail client after they arrive on the protected virtual machine.
If you want to open access to Mail Anti-Virus settings from Microsoft Office Outlook and enable scanning of messages that are transmitted via the POP3, SMTP, NNTP, and IMAP protocols after they arrive on the protected virtual machine by using an extension that is embedded into Microsoft Office Outlook, select the Additional: Microsoft Office Outlook extension check box.
If you want to close access to Mail Anti-Virus settings from Microsoft Office Outlook and disable scanning of messages that are transmitted via the POP3, SMTP, NNTP, and IMAP protocols after they arrive on the protected virtual machine by using an extension that is embedded into Microsoft Office Outlook, clear the Additional: Microsoft Office Outlook extension check box.
If you use a mail client other than Microsoft Office Outlook, messages that are transmitted via the POP3, SMTP, NNTP and IMAP protocols are not scanned by Mail Anti-Virus when the POP3 / SMTP / NNTP / IMAP traffic check box is cleared.
Click OK in the Mail Anti-Virus window.
Click the Apply button.
To create the protection scope of Mail Anti-Virus in the local interface:
In the left part of the window, in the Anti-Virus protection section, select Mail Anti-Virus.
In the right part of the window, the Mail Anti-Virus component’s settings are displayed.
If the settings in the local interface are not available, this means that the values of settings defined by the policy are used for all protected virtual machines of the administration group.