Red Hat DIRECTORY SERVER 8.1 - 11-01-2010 Instrukcja Użytkownika Pobierz pdf (Strona 65)

email defines the recipient address(es) to match. Multiple email addresses

are separated by spaces. The matching is done on substrings, with curly

brackets ({}) defining substring boundaries:

• {user@domain} matches exactly and only user@domain

• user@domain} matches anything that ends with user@domain

• {user@domain matches anything that starts with user@domain

• user@domain matches anything containing user@domain

keyId is the list of key IDs to use for the recipient. The key ID is specified in

the 8-byte format (e.g. 0x1234ABCD) or in the 16-byte format (e.g.

0x1234567890ABCDEF). Multiple keys are separated by spaces. If a dot (.) is

the only value in the field, Enigmail does not use a specific key ID and finds the

correct key using the email address. Any further rule for this recipient will be

ignored.

sign specifies message signing, encrypt specifies message encryption, and

pgpMime specifies PGP/MIME use. All these attributes must have one of the

following values:

• 0 – Disables the action even if it was enabled in the Message

Composition window. This is equivalent to the Never option in the GUI.

• 1 – Uses the setting specified in the Message Composition window. This

is equivalent to the Yes, if selected in Message Composition option in the

GUI.

• 2 – Enables the action even if it was not enabled in the Message

Composition window. This is equivalent to the Always option in the GUI.

When a message is sent to multiple recipients, and multiple rules are applied,

the value 0 overrides the value 2: if one of the rules disables the action, the

action will not be applied for the message, regardless of any other rule with

value 2.

1 2 ... 60 61 62 63 64 65 66 67 68 69 70 ... 105 106

Brak uwag

Red Hat DIRECTORY SERVER 8.1 - 11-01-2010 Instrukcja Użytkownika Strona 65