4 * The contents of this file are subject to the terms of the
5 * Common Development and Distribution License, Version 1.0 only
6 * (the "License"). You may not use this file except in compliance
9 * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
10 * or http://www.opensolaris.org/os/licensing.
11 * See the License for the specific language governing permissions
12 * and limitations under the License.
14 * When distributing Covered Code, include this CDDL HEADER in each
15 * file and include the License file at usr/src/OPENSOLARIS.LICENSE.
16 * If applicable, add the following below this CDDL HEADER, with the
17 * fields enclosed by brackets "[]" replaced with your own identifying
18 * information: Portions Copyright [yyyy] [name of copyright owner]
22 /* Copyright (c) 1984, 1986, 1987, 1988, 1989 AT&T */
23 /* All Rights Reserved */
27 * University Copyright- Copyright (c) 1982, 1986, 1988
28 * The Regents of the University of California
31 * University Acknowledgment- Portions of this document are derived from
32 * software developed by the University of California, Berkeley, and its
36 #pragma ident "%Z%%M% %I% %E% SMI"
39 * mailx -- a modified version of a University of California at Berkeley
42 * This file contains the definitions of data structures used in
43 * configuring the network behavior of Mail when replying.
47 * The following constants are used when you are running 4.1a bsd or
48 * later on a local network. The name thus found is inserted
49 * into the host table slot whose name was originally EMPTY.
51 #define EMPTY "** empty **"
55 * The following data structure is the host table. You must have
56 * an entry here for your own machine, plus any special stuff you
57 * expect the mailer to know about. Not all hosts need be here, however:
58 * mailx can dope out stuff about hosts on the fly by looking
59 * at addresses. The machines needed here are:
60 * 1) The local machine
61 * 2) Any machines on the path to a network gateway
62 * 3) Any machines with nicknames that you want to have considered
64 * The machine id letters can be anything you like and are not seen
65 * externally. Be sure not to use characters with the 0200 bit set --
66 * these have special meanings.
75 * Network type codes. Basically, there is one for each different
76 * network, if the network can be discerned by the separator character,
77 * such as @ for the arpa net. The purpose of these codes is to
78 * coalesce cases where more than one character means the same thing,
79 * such as % and @ for the arpanet. Also, the host table uses a
80 * bit map of these codes to show what it is connected to.
81 * BN -- connected to Bell Net.
82 * AN -- connected to ARPA net, SN -- connected to Schmidt net.
84 #define AN 1 /* Connected to ARPA net */
85 #define BN 2 /* Connected to BTL net */
86 #define SN 4 /* Connected to Schmidt net */
89 * Data structure for table mapping network characters to network types.
92 char nt_char
; /* Actual character separator */
93 int nt_bcode
; /* Type bit code */
97 * Codes for the "kind" of a network. IMPLICIT means that if there are
98 * physically several machines on the path, one does not list them in the
99 * address. The arpa net is like this. EXPLICIT means you list them,
101 * By the way, this distinction means we lose if anyone actually uses the
102 * arpa net subhost convention: name@subhost@arpahost
108 * Table for mapping a network code to its type -- IMPLICIT routing or
112 int nk_type
; /* Its bit code */
113 int nk_kind
; /* Whether explicit or implicit */
117 * The following table gives the order of preference of the various
118 * networks. Thus, if we have a choice of how to get somewhere, we
119 * take the preferred route.
127 * External declarations for above defined tables.
129 extern struct netmach netmach
[];
130 extern struct ntypetab ntypetab
[];
131 extern struct nkindtab nkindtab
[];
132 extern struct netorder netorder
[];
133 extern char *metanet
;