Please enable JavaScript to view this site.

This submenu is called up from the submenu ENCRYPTION POLICY.

 

anchor link Section Settings

 

Parameters

Description

anchor link State


anchor link CheckBoxInactive Inactive

By default, this option is inactive.

By activating the option, the rule remains inactive. This allows, for example, for a rule to be prepared for later use.

anchor link Policyname

Individual name of the rule that is assigned when the rule is created.

anchor link Policy Domains DropDown

The Managed Domains which are available for the rule and which can be selected as the source are listed here. Multiple selections are possible by clicking with the "CTRL" key pressed.

Generally, only Managed Domainswhich have not been assigned to a rule yet are available. In client-capable systems, only those Managed Domains which are also assigned to the client from which this menu was opened are visible.

anchor link Policy flag

If, by means of Custom commands, a flag() is set, for example by an LDAP query using ldap_compare(), this can also be used as a restricting criterion for triggering this policy here.

anchor link Encryption mode DropDown

The desired type of encryption is specified in the selection menu of this option:

 

anchor link Do not encrypt

Suppresses encryption (see Mail Processing Ruleset generator General settings Do not touch mails with the following text in subject:).

anchor link S/MIME-only

Enforces the user-related
S/MIME encryption..

Note:

Since Domain encryption is generally used, if available, it is enforced by the setup alone.

anchor link OpenPGP-only

Enforces the user-related
OpenPGP encryption..

anchor link GINA-only

Enforces the GINA encryption (see Mail Processing Ruleset generator Encryption Outgoing e-mails Always use GINA technology for mails with the following text in subject:).

is only displayed with an active HIN Connector licence.


anchor link HIN Global only

Enforces encryption by "HIN Secure Mail GLOBAL" (see also HIN Connector).

anchor link Emulate HIN MGW

By selecting this option, for the domains selected under Policy Domains Managed Domains, the behaviour of a HIN Mail Gateway (see also HIN Connector) can be enforced.

No SEPPmail Secure E-Mail Gateway functions like S/MIME (X.509))-, OpenPGP- and GINA Webmail encryption are then available.

anchor link Emulate HIN MGW, with Outlook flag

By selecting this option, for the domains selected under Policy Domains Managed Domains, the behaviour of a HIN Mail Gateway (see also HIN Connector) via the Outlook flag "confidential" (see also Microsoft Outlook Confidentiality) can be enforced.

 


anchor link Incamail

Uses Incamail (see also Mail Processing Ruleset generator Advanced options Use Incamail instead of local GINA interface) instead of GINA, unless a qualitatively better procedure (see Encryption Hierarchy) is available.

anchor link Any

Default setting.

Enforces encryption according to the Encryption Hierarchy (see Mail Processing Ruleset generator Encryption Outgoing e-mails Always encrypt mails with the following text in subject:).

anchor link S/MIME options

Allows setting the encryption algorithms and signature hash procedures to be used for S/MIME

 

anchor link CheckBoxInactive S/MIME sign outgoing mails

By default, this option is inactive.

Enabling this option enforces S/MIME signing of outgoing emails.

anchor link CheckBoxInactive Use opaque signature

By default, this option is inactive.

see Mail Processing Ruleset generator Signing Outgoing e-mails Use opaque signature

anchor link CheckBoxInactive Use triple wrapping

(new in 12.1)

By default, this option is inactive.

see Mail Processing Ruleset generator Signing Outgoing e-mails Use triple wrapping

anchor link CheckBoxInactive Use default digest for S/MIME signing: DropDown

see Mail Processing Ruleset generator Signing Outgoing e-mails Use default digest for S/MIME signing:


anchor link SHA-1

anchor link SHA-256

anchor link SHA-512

anchor link CheckBoxInactive Prefer RSA-PSS for S/MIME signatures

see Mail Processing Ruleset generator Signing Outgoing e-mails Prefer RSA-PSS for S/MIME signatures


anchor link CheckBoxInactive Prefer RSA-OAEP for S/MIME encryption

see Mail Processing Ruleset generator Encryption Outgoing e-mails Prefer RSA-OAEP for S/MIME encryption

anchor link CheckBoxInactive Use default cipher for S/MIME encryption DropDown

see Mail Processing Ruleset generator Encryption Outgoing e-mails Use default cipher for S/MIME encryption


anchor link Triple DES

anchor link AES-128

anchor link AES-192

anchor link AES-256

anchor link OpenPGP options

Allows you to set the encryption methods to be used for OpenPGP.


anchor link CheckBoxInactive OpenPGP sign outgoing mails when sender has a secret key

By default, this option is inactive.

see Mail Processing Ruleset generator Signing Outgoing e-mails OpenPGP sign outgoing mails when encrypting with OpenPGP and sender has a secret key

anchor link CheckBoxInactive Use OpenPGP method for user encryption DropDown

see Mail Processing Ruleset generator Encryption Outgoing e-mails OpenPGP method for recipient encryption


anchor link PGP/MIME

anchor link Inline PGP

anchor link CheckBoxInactive Use OpenPGP method for domain encryption DropDown

see Mail Processing Ruleset generator Encryption Outgoing e-mails OpenPGP method for domain encryption


anchor link PGP/MIME

anchor link Inline PGP

anchor link GINA options

Only relevant if, under Encryption mode "GINA-only" or "Any" has been selected.

 

anchor link DropDown [GINA Domain selection]

Selection of the GINA Domainto be used in this rule.

 

empty

anchor link Note:

In client-capable systems, care must be taken to ensure that this GINA Domain is assigned to the same client (Customers) as this policy.


is only displayed with an active HIN Connector licence.

anchor link Miscellaneous options


 

anchor link CheckBoxInactive Use HIN Secure Mail GLOBAL instead of local GINA interface

By default, this option is inactive.

see Mail Processing Ruleset generator Advanced Options Use HIN Secure Mail GLOBAL instead of local GINA interface

 

anchor link Bounce behaviour

By default, bounce_policy is selected.

Determines how to handle an email if the execution of the rule fails.

 

 

anchor link [Email template selection] DropDown

By default, the selection is "bounce_policy".

Selection of a special template previously created via Mail System Edit mail templates.... This can be used to indicate to the sender that the sending of their email has failed due to this special rule/policy.

anchor link CheckBoxInactive Allow default mail processing instead of bouncing if encryption was not immediately successful

By default, this option is inactive.

This option is used to decide whether an email for which this rule/policy could not be executed should first run through the global ruleset (see Ruleset generator).

 

empty

anchor link Note:

This option has no influence on the bounce due to missing user permissions (User not authenticated) or a missing key pair (No secret key available). This prevents the encryption/signing which is to be enforced from not being executed, if applicable.

If the automatic creation of Users (see Mail Processing Ruleset generator User creation) is activated, a new user is created for the implementation of the rule as needed.

anchor link Disclaimer

Individual disclaimer settings for this rule.

 

anchor link [Disclaimer template selection] DropDown

Option of selecting a disclaimer from LIST DISCLAIMER.

If no selection is made, or "[default]" is selected, the disclaimer specified in the Managed Domains of the sender will be used.

With the selection "-NONE-", the insertion of a disclaimer is suppressed.

anchor link Customer

(only in client-capable systems)

Client for which the policy has been created.

 

empty

anchor link Note:

A policy is always bound to an email domain (Managed Domains). The list of selectable domains (Policy Domains) depends on the client (Customers).

 

anchor link [Client selection] DropDown

Enables the allocation of the rule to a client.

 

empty

anchor link Note:

Rules are already allocated to the corresponding clients when they are opened from the source menu.

Usually, any changes are to be avoided since a subsequent allocation can lead to a loss of the client separation and to the erroneous processing of emails.

.

anchor link Senders

Here, under New Domain/ Mailaddress, email addresses or email domains and/or wildcard domains can be inserted as string in the form john.doe@mycompany.tld, mycompany.tld or .mycompany.tld. The rule will then apply exclusively to these entries.

Optionally, in the field Comment: a custom comment can be added for each entry.

After entering an address, another input field is displayed by clicking on Add entry.

Any entries in this field must be a subset of the Managed Domains selected under Policy Domains.

anchor link Recipients


 

Click on Save to save the rule. Cancel cancels the process without saving. If an already existing rule is opened by clicking on its name, a Delete button is also displayed via which this already existing rule can be deleted.

 

empty

anchor link Attention:

After the creation of policies, the ruleset must be generated again after saving the individual policies by means of Save (Mail Processing SMTP ruleset Generate ruleset).

This is also displayed in the status bar:

The ruleset was modified. Please generate a new ruleset to activate it.

  

Keyboard Navigation

F7 for caret browsing
Hold ALT and press letter

This Info: ALT+q
Topic Header: ALT+t
Topic Body: ALT+b
Contents: ALT+c
Search: ALT+s
Exit Menu/Up: ESC