Difference between revisions of "Policy Manager"
| Line 4: | Line 4: | ||
The active policy can be viewed at any given time, but once the policy manager is unlocked, or opened in editing mode, the GWAVA system will no longer automatically manage the policy. This means that every time an additional interface is added to the system manual manipulation of policies is required. The simplest way to deal with the Policy Manager is to allow the Policy Manager to be automatically managed by the system. | The active policy can be viewed at any given time, but once the policy manager is unlocked, or opened in editing mode, the GWAVA system will no longer automatically manage the policy. This means that every time an additional interface is added to the system manual manipulation of policies is required. The simplest way to deal with the Policy Manager is to allow the Policy Manager to be automatically managed by the system. | ||
| + | |||
| + | Viewing policies in readonly mode displays all the pertinent information in a grayed-out text. Selecting the different parts of the existing policy tree will display the policy active on each section. Every automatically created and configured policy contains identifying notes, and will be tied to the interface that it was created with. All gray text and settings are locked and cannot be modified. Every automatically created and configured policy contains identifying notes, and will be tied to the interface that it was created with. | ||
Revision as of 21:11, 5 March 2014
GWAVA introduces the ‘policy’ to the GWAVA interface. Polices are utilized mainly for multi-tenant systems; systems with multiple domains, interfaces, or both. GWAVA and the Policy Manager disassociate domain settings from the interface, allowing multiple managed domains under the same interface, or vice versa. If, for example, multiple domains are hosted on a large system with load balanced SMTP servers, the policy manager can implement several different scanning profiles through a single or multiple SMTP interfaces all controlled by the same GWAVA server. A policy may also be used to manage several completely separate domains hosted on the same SMTP server, through the same SMTP scanning interface, with different criteria for each domain.
By Default, the Policy Manager automatically creates and manages policies for interfaces. Unlocking the Policy Manager permanently disables automatic management. If the GWAVA system is setup to only utilize a single domain and interface, or the different domains managed are to have the same scanning policy, then the Policy Manager should be left to manage the policy automatically. Policies are required for scanning to be completed, as they are the framework for all mail flow and dictate what mail ‘qualifies’ for scanning.
The active policy can be viewed at any given time, but once the policy manager is unlocked, or opened in editing mode, the GWAVA system will no longer automatically manage the policy. This means that every time an additional interface is added to the system manual manipulation of policies is required. The simplest way to deal with the Policy Manager is to allow the Policy Manager to be automatically managed by the system.
Viewing policies in readonly mode displays all the pertinent information in a grayed-out text. Selecting the different parts of the existing policy tree will display the policy active on each section. Every automatically created and configured policy contains identifying notes, and will be tied to the interface that it was created with. All gray text and settings are locked and cannot be modified. Every automatically created and configured policy contains identifying notes, and will be tied to the interface that it was created with.
