Red Hat DIRECTORY SERVER 8.1 - 11-01-2010 Manual de usuario descargar pdf (Pagina 64)

The rules are processed sequentially in the order displayed in the rules editor.

If a rule contains an OpenPGP key, the rule is applied, but the address that

triggered the match will not be rechecked in any following rules.

In order to minimize the number of rules you have to create, you should set

carefully your OpenPGP global and account settings.

How Enigmail chooses the recipient keys for an encrypted message is

controlled by the settings in OpenPGP → Preferences → Key Selection. By

default, Enigmail first checks per-recipient rules, then the user IDs in your public

keyring.

You can disable on-the-fly the lookup of per-recipient rules for a message you're

composing by checking the option OpenPGP → Ignore Per-Recipient Rules in

the Message Composition window.

You can enable the option OpenPGP → Preferences → Sending → Always

confirm before sending in order to check the status for signing, encryption, and

PGP/MIME before a message is sent.

Per-recipient rules are stored in a file called pgprules.xml located in your

profile directory. If you backup/restore your profile manually, you should make

sure to include this file.

8.6.4. XML format of per-recipient rules

This Section details the format of pgprules.xml, which is a XML file

generated by Enigmail and containing the per-recipient rules. This is intended

as a technical reference for developers only; normal users should never edit the

XML file manually, and can skip this Section.

The pgprules.xml file has the following structure:

<pgpRule email='{[email protected]}' keyId='0x1234ABCD'

sign='1' encrypt='1' pgpMime='1'/>

<pgpRule email='{bob@ {user@domain' keyId='0xCDEF6789'

sign='2' encrypt='1' pgpMime='0'/>

<pgpRule email='{[email protected]} '

keyId='0x11111111 0x22222222 0x33333333' sign='2'

encrypt='2' pgpMime='0'/>

...

</pgpRuleList>

Each <pgpRule .../> line is a per-recipient rule stating how Enigmail should

enable or disable encryption, signing and PGP/MIME and which key to use.

The file is processed sequentially; if a rule contains a key ID attribute with some

value, the rule is applied, but the address that matched will not be rechecked in

any following rule. The attributes are defined as follows.

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

Sin comentarios

Red Hat DIRECTORY SERVER 8.1 - 11-01-2010 Manual de usuario Pagina 64