sendmail, 4th Edition

hesiod

MIT network user authentication services V8.7 and later

The hesiod type of database map uses the Hesiod system, a network information system developed as Project Athena. Support of hesiod database maps is available only if you declare HESIOD when compiling sendmail. (See HESIOD on page 115 for a fuller description of the Hesiod system.)

A hesiod database map is declared like this:

Kname hesiod HesiodNameType

The HesiodNameType must be one that is known at your site, such as passwd or service. An unknown HesiodNameType will yield this error when sendmail begins to run:

cannot initialize Hesiod map (hesiod error number)

One example of a lookup might look like this:

Kuid2name hesiod uid
R$-      $: $(uid2name $1 $)

Here, we declare the network database map uid2name using the Hesiod type uid, which converts user-id numbers into login names. If the conversion was successful, we use the login name returned; otherwise, we use the original workspace.

Quite a few database-map switches are available with this type. They are all listed in Table 23-14.

Table 23-14. The hesiod database-map type K command switches

Switch	§	Description
-A	-A on page 886	Append values for duplicate keys.
-a	-a on page 887	Append tag on successful match.
-D	-D on page 887	Don’t use this database map if DeliveryMode=defer.
-f	-f on page 887	Don’t fold keys to lowercase.
-m	-m on page 888	Suppress replacement on match.
-N	-N on page 889	Append a null byte to all keys.
-O	-O on page 889	Never add a null ...