Commit | Line | Data |
---|---|---|
7ace9d88 | 1 | |
7ace9d88 | 2 | |
4a51b074 | 3 | NEW SENDMAIL CONFIGURATION FILES |
7ace9d88 | 4 | |
4a51b074 | 5 | Eric Allman <eric@CS.Berkeley.EDU> |
7ace9d88 | 6 | |
eb802161 | 7 | @(#)README 8.33 (Berkeley) %G% |
7ace9d88 | 8 | |
7ace9d88 | 9 | |
4a51b074 | 10 | This document describes the sendmail configuration files being used |
f22970ed EA |
11 | at Berkeley. These use features in the new (R8) sendmail; they will |
12 | not work on other versions. | |
4a51b074 EA |
13 | |
14 | These configuration files are probably not as general as previous | |
6fb312a3 | 15 | versions, and don't handle as many of the weird cases automagically. |
4a51b074 EA |
16 | I was able to simplify by them for two reasons. First, the network |
17 | has become more consistent -- for example, at this point, everyone | |
18 | on the internet is supposed to be running a name server, so hacks to | |
19 | handle NIC-registered hosts can go away. Second, I assumed that a | |
20 | subdomain would be running SMTP internally -- UUCP is presumed to be | |
21 | a long-haul protocol. I realize that this is not universal, but it | |
22 | does describe the vast majority of sites with which I am familiar, | |
23 | including those outside the US. | |
24 | ||
6fb312a3 EA |
25 | Of course, the downside of this is that if you do live in a weird |
26 | world, things are going to get weirder for you. I'm sorry about that, | |
4a51b074 EA |
27 | but at the time we at Berkeley had a problem, and it seemed like the |
28 | right thing to do. | |
29 | ||
fd82c288 EA |
30 | This package requires a post-V7 version of m4; if you are running the |
31 | 4.2bsd, SysV.2, or 7th Edition version, I suggest finding a friend with | |
32 | a newer version. You can m4-expand on their system, then run locally. | |
a7e36c1b EA |
33 | SunOS's /usr/5bin/m4 or BSD-Net/2's m4 both work. GNU m4 version 1.1 |
34 | also works. Unfortunately, I'm told that the M4 on BSDI 1.0 doesn't | |
35 | work -- you'll have to use a Net/2 or GNU version. | |
7ace9d88 | 36 | |
a33031f5 | 37 | IF YOU DON'T HAVE A BERKELEY MAKE, don't despair! Just run |
445bdec1 EA |
38 | "m4 foo.mc > foo.cf" -- that should be all you need. There is also |
39 | a fairly crude (but functional) Makefile.dist that works on the | |
40 | old version of make. | |
a33031f5 EA |
41 | |
42 | To get started, you may want to look at tcpproto.mc (for TCP-only | |
f51c9ac8 EA |
43 | sites), uucpproto.mc (for UUCP-only sites), and clientproto.mc (for |
44 | clusters of clients using a single mail host). Others are versions | |
a33031f5 EA |
45 | that we use at Berkeley, although not all are in current use. For |
46 | example, ucbarpa has gone away, but I've left ucbarpa.mc in because | |
47 | it demonstrates some interesting techniques. | |
48 | ||
4a51b074 EA |
49 | I'm not pretending that this README describes everything that these |
50 | configuration files can do; clever people can probably tweak them | |
51 | to great effect. But it should get you started. | |
52 | ||
1b5c2cc9 EA |
53 | ******************************************************************* |
54 | *** BE SURE YOU CUSTOMIZE THESE FILES! They have some *** | |
55 | *** Berkeley-specific assumptions built in, such as the name *** | |
56 | *** of our UUCP-relay. You'll want to create your own domain *** | |
57 | *** description, and use that in place of domain/Berkeley.m4. *** | |
58 | ******************************************************************* | |
59 | ||
bee9d799 | 60 | |
4a51b074 EA |
61 | +--------------------------+ |
62 | | INTRODUCTION AND EXAMPLE | | |
63 | +--------------------------+ | |
64 | ||
65 | Configuration files are contained in the subdirectory "cf", with a | |
66 | suffix ".mc". They must be run through "m4" to produce a ".cf" file. | |
67 | ||
7ace9d88 EA |
68 | Let's examine a typical .mc file (cf/cs-exposed.mc): |
69 | ||
70 | divert(-1) | |
71 | # | |
72 | # Copyright (c) 1983 Eric P. Allman | |
73 | # Copyright (c) 1988 The Regents of the University of California. | |
74 | # All rights reserved. | |
75 | # | |
76 | # Redistribution and use in source and binary forms are permitted | |
77 | # provided that the above copyright notice and this paragraph are | |
78 | # duplicated in all such forms and that any documentation, | |
79 | # advertising materials, and other materials related to such | |
80 | # distribution and use acknowledge that the software was developed | |
81 | # by the University of California, Berkeley. The name of the | |
82 | # University may not be used to endorse or promote products derived | |
83 | # from this software without specific prior written permission. | |
84 | # THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR | |
85 | # IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED | |
86 | # WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. | |
87 | # | |
88 | ||
4a51b074 | 89 | The divert(-1) will delete the crud in the resulting output file. |
fd82c288 | 90 | The copyright notice is what your lawyers require. Our lawyers require |
4a51b074 EA |
91 | the one that I've included in my files. A copyleft is a copyright by |
92 | another name. | |
93 | ||
94 | The next line MUST be | |
7ace9d88 EA |
95 | |
96 | include(`../m4/cf.m4') | |
97 | ||
4a51b074 EA |
98 | This will pull in the M4 macros you will need to make sense of |
99 | everything else. As the saying goes, don't think about it, just | |
100 | do it. If you don't do it, don't bother reading the rest of this | |
101 | file. | |
7ace9d88 | 102 | |
8897fcb1 | 103 | VERSIONID(`<SCCS or RCS version id>') |
7ace9d88 EA |
104 | |
105 | VERSIONID is a macro that stuffs the version information into the | |
106 | resulting file. We use SCCS; you could use RCS, something else, or | |
4a51b074 EA |
107 | omit it completely. This is not the same as the version id included |
108 | in SMTP greeting messages -- this is defined in m4/version.m4. | |
7ace9d88 | 109 | |
9df1b56b | 110 | DOMAIN(cs.exposed) |
7ace9d88 EA |
111 | |
112 | This example exposes the host inside of the CS subdomain -- that is, | |
113 | it doesn't try to hide the name of the workstation to the outside | |
114 | world. Changing this to DOMAIN(cs.hidden) would have made outgoing | |
115 | messages refer to "<username>@CS.Berkeley.EDU" instead of using the | |
5dd53c38 | 116 | local hostname. Internally this is effected by using |
4a51b074 | 117 | "MASQUERADE_AS(CS.Berkeley.EDU)". |
7ace9d88 | 118 | |
9df1b56b | 119 | MAILER(smtp) |
7ace9d88 | 120 | |
c573210d EA |
121 | These describe the mailers used at the default CS site site. The |
122 | local mailer is always included automatically. | |
7ace9d88 | 123 | |
bee9d799 | 124 | |
4a51b074 EA |
125 | +--------+ |
126 | | OSTYPE | | |
127 | +--------+ | |
128 | ||
7ace9d88 EA |
129 | Note that cf/cs-exposed.mc omits an OSTYPE macro -- this assumes |
130 | default Computer Science Division environment. There are several | |
fd82c288 EA |
131 | explicit environments available: bsd4.3, bsd4.4, hpux, irix, osf1, |
132 | riscos4.5, sunos3.5, sunos4.1, and ultrix4.1. These change things | |
133 | like the location of the alias file and queue directory. Some of | |
134 | these files are identical to one another. | |
4a51b074 EA |
135 | |
136 | Operating system definitions are easy to write. They may define | |
137 | the following variables (everything defaults, so an ostype file | |
138 | may be empty). | |
139 | ||
140 | ALIAS_FILE [/etc/aliases] The location of the text version | |
00d0b5bf | 141 | of the alias file(s). It can be a comma-separated |
7b97409d EA |
142 | list of names (but be sure you quote values with |
143 | comments in them -- for example, use | |
144 | define(`ALIAS_FILE', `a,b') | |
145 | to get "a" and "b" both listed as alias files; | |
146 | otherwise the define() primitive only sees "a"). | |
4a51b074 EA |
147 | HELP_FILE [/usr/lib/sendmail.hf] The name of the file |
148 | containing information printed in response to | |
149 | the SMTP HELP command. | |
4a51b074 EA |
150 | QUEUE_DIR [/var/spool/mqueue] The directory containing |
151 | queue files. | |
152 | STATUS_FILE [/etc/sendmail.st] The file containing status | |
153 | information. | |
bee9d799 | 154 | LOCAL_MAILER_PATH [/bin/mail] The program used to deliver local mail. |
2e9b6f6e EA |
155 | LOCAL_MAILER_FLAGS [rmn] The flags used by the local mailer. The |
156 | flags lsDFM are always included. | |
d8b2ad36 EA |
157 | LOCAL_MAILER_ARGS [mail -d $u] The arguments passed to deliver local |
158 | mail. | |
bee9d799 | 159 | LOCAL_SHELL_PATH [/bin/sh] The shell used to deliver piped email. |
1c61e291 EA |
160 | LOCAL_SHELL_FLAGS [eu] The flags used by the shell mailer. The |
161 | flags lsDFM are always included. | |
162 | LOCAL_SHELL_ARGS [sh -c $u] The arguments passed to deliver "prog" | |
163 | mail. | |
bee9d799 EA |
164 | USENET_MAILER_PATH [/usr/lib/news/inews] The name of the program |
165 | used to submit news. | |
166 | USENET_MAILER_FLAGS [rlsDFMmn] The mailer flags for the usenet mailer. | |
167 | USENET_MAILER_ARGS [-m -h -n] The command line arguments for the | |
168 | usenet mailer. | |
4e444ec8 EA |
169 | USENET_MAILER_MAX [100000] The maximum size of messages that will |
170 | be accepted by the usenet mailer. | |
5dd53c38 EA |
171 | SMTP_MAILER_FLAGS [undefined] Flags added to SMTP mailer. Default |
172 | flags are `mDFMUX' (and `a' for esmtp mailer). | |
4e444ec8 EA |
173 | SMTP_MAILER_MAX [undefined] The maximum size of messages that will |
174 | be transported using the smtp or esmtp mailers. | |
5dd53c38 EA |
175 | UUCP_MAILER_FLAGS [undefined] Flags added to UUCP mailer. Default |
176 | flags are `DFMhuU' (and `m' for suucp mailer, minus | |
177 | `U' for uucp-dom mailer). | |
d8b2ad36 EA |
178 | UUCP_MAILER_ARGS [uux - -r -z -a$f -gC $h!rmail ($u)] The arguments |
179 | passed to the UUCP mailer. | |
1c61e291 EA |
180 | UUCP_MAX_SIZE [100000] The maximum size message accepted for |
181 | transmission by the UUCP mailers. | |
4e444ec8 EA |
182 | FAX_MAILER_PATH [/usr/local/lib/fax/mailfax] The program used to |
183 | submit FAX messages. | |
184 | FAX_MAILER_MAX [100000] The maximum size message accepted for | |
185 | transmission by FAX. | |
4a51b074 | 186 | |
4a51b074 EA |
187 | +---------+ |
188 | | DOMAINS | | |
189 | +---------+ | |
190 | ||
191 | You will probably want to collect domain-dependent defines into one | |
192 | file, referenced by the DOMAIN macro. For example, our Berkeley | |
193 | domain file includes definitions for several internal distinguished | |
194 | hosts: | |
195 | ||
196 | UUCP_RELAY The host that will forward UUCP-addressed email. | |
197 | If not defined, all UUCP sites must be directly | |
bb3c21c3 | 198 | connected. |
4a51b074 EA |
199 | BITNET_RELAY The host that will forward BITNET-addressed email. |
200 | If not defined, the .BITNET pseudo-domain won't work. | |
4a51b074 EA |
201 | LOCAL_RELAY The site that will handle unqualified names -- that |
202 | is, names with out an @domain extension. If not set, | |
203 | they are assumed to belong on this machine. This | |
204 | allows you to have a central site to store a | |
205 | company- or department-wide alias database. This | |
206 | only works at small sites, and there are better | |
bb3c21c3 EA |
207 | methods. |
208 | ||
209 | Each of these can be either ``mailer:hostname'' (in which case the | |
210 | mailer is the internal mailer name, such as ``suucp'' and the hostname | |
211 | is the name of the host as appropriate for that mailer) or just a | |
212 | ``hostname'', in which case a default mailer type (usually ``relay'', | |
2e9b6f6e EA |
213 | a variant on SMTP) is used. WARNING: if you have a wildcard MX |
214 | record matching your domain, you probably want to define these to | |
215 | have a trailing dot so that you won't get the mail diverted back | |
216 | to yourself. | |
4a51b074 EA |
217 | |
218 | The domain file can also be used to define a domain name, if needed | |
6f02ae2f EA |
219 | (using "DD<domain>") and set certain site-wide features. If all hosts |
220 | at your site masquerade behind one email name, you could also use | |
221 | MASQUERADE_AS here. | |
4a51b074 | 222 | |
dec2b686 EA |
223 | You do not have to define a domain -- in particular, if you are a |
224 | single machine sitting off somewhere, it is probably more work than | |
225 | it's worth. This is just a mechanism for combining "domain dependent | |
226 | knowledge" into one place. | |
227 | ||
4a51b074 EA |
228 | +---------+ |
229 | | MAILERS | | |
230 | +---------+ | |
7ace9d88 EA |
231 | |
232 | There are fewer mailers supported in this version than the previous | |
233 | version, owing mostly to a simpler world. | |
234 | ||
235 | local The local and prog mailers. You will almost always | |
236 | need these; the only exception is if you relay ALL | |
fd82c288 EA |
237 | your mail to another site. This mailer is included |
238 | automatically. | |
7ace9d88 EA |
239 | |
240 | smtp The Simple Mail Transport Protocol mailer. This does | |
241 | not hide hosts behind a gateway or another other | |
242 | such hack; it assumes a world where everyone is | |
d8b2ad36 EA |
243 | running the name server. This file actually defines |
244 | three mailers: "smtp" for regular (old-style) SMTP to | |
245 | other servers, "esmtp" for extended SMTP to other | |
246 | servers, and "relay" for transmission to our | |
247 | RELAY_HOST or MAILER_HUB. | |
7ace9d88 EA |
248 | |
249 | uucp The Unix-to-Unix Copy Program mailer. Actually, this | |
41187805 EA |
250 | defines two mailers, "uucp-old" (a.k.a. "uucp") and |
251 | "uucp-new" (a.k.a. "suucp"). The latter is for when you | |
252 | know that the UUCP mailer at the other end can handle | |
253 | multiple recipients in one transfer. If the smtp mailer | |
254 | is also included in your configuration, two other mailers | |
255 | ("uucp-dom" and "uucp-uudom") are also defined. When you | |
256 | include the uucp mailer, sendmail looks for all names in | |
2a20bc94 EA |
257 | the $=U class and sends them to the uucp-old mailer; all |
258 | names in the $=Y class are sent to uucp-new; and all | |
259 | names in the $=Z class are sent to uucp-uudom. Note that | |
4a51b074 EA |
260 | this is a function of what version of rmail runs on |
261 | the receiving end, and hence may be out of your control. | |
2a20bc94 EA |
262 | See the section below describing UUCP mailers in more |
263 | detail. | |
4a51b074 | 264 | |
bee9d799 EA |
265 | usenet Usenet (network news) delivery. If this is specified, |
266 | an extra rule is added to ruleset 0 that forwards all | |
267 | local email for users named ``group.usenet'' to the | |
268 | ``inews'' program. Note that this works for all groups, | |
269 | and may be considered a security problem. | |
270 | ||
63013ec3 EA |
271 | fax Facsimile transmission. This is experimental and based |
272 | on Sam Leffler's FlexFAX software. For more information, | |
273 | see below. | |
274 | ||
418602bc EA |
275 | pop Post Office Protocol. |
276 | ||
bee9d799 | 277 | |
4a51b074 EA |
278 | +----------+ |
279 | | FEATURES | | |
280 | +----------+ | |
281 | ||
282 | Special features can be requested using the "FEATURE" macro. For | |
283 | example, the .mc line: | |
284 | ||
285 | FEATURE(use_cw_file) | |
286 | ||
287 | tells sendmail that you want to have it read an /etc/sendmail.cw | |
3ad658d7 EA |
288 | file to get values for class $=w. The FEATURE may contain a single |
289 | optional parameter -- for example: | |
290 | ||
291 | FEATURE(mailertable, dbm /usr/lib/mailertable) | |
292 | ||
293 | Available features are: | |
4a51b074 EA |
294 | |
295 | use_cw_file Read the file /etc/sendmail.cw file to get alternate | |
296 | names for this host. This might be used if you were | |
297 | on a host that MXed for a dynamic set of other | |
298 | hosts. If the set is static, just including the line | |
299 | "Cw<name1> <name2> ..." is probably superior. | |
dec2b686 EA |
300 | The actual filename can be overridden by redefining |
301 | confCW_FILE. | |
f51c9ac8 | 302 | |
bee9d799 EA |
303 | redirect Reject all mail addressed to "address.REDIRECT" with |
304 | a ``551 User not local; please try <address>'' message. | |
305 | If this is set, you can alias people who have left | |
306 | to their new address with ".REDIRECT" appended. | |
f51c9ac8 | 307 | |
a33031f5 | 308 | nouucp Don't do anything special with UUCP addresses at all. |
f51c9ac8 | 309 | |
928fba03 EA |
310 | nocanonify Don't pass addresses to $[ ... $] for canonification. |
311 | This would generally only be used by sites that only | |
312 | act as mail gateways or which have user agents that do | |
bb3c21c3 EA |
313 | full canonification themselves. You may also want to |
314 | use "define(`confBIND_OPTS',`-DNSRCH -DEFNAMES')" to | |
315 | turn off the usual resolver options that do a similar | |
316 | thing. | |
f51c9ac8 | 317 | |
da99e870 EA |
318 | notsticky By default, email sent to "user@local.host" are marked |
319 | as "sticky" -- that is, the local addresses aren't | |
320 | matched against UDB and don't go through ruleset 5. | |
321 | This features disables this treatment. It would | |
322 | normally be used on network gateway machines. | |
f51c9ac8 | 323 | |
3ad658d7 EA |
324 | mailertable Include a "mailer table" which can be used to override |
325 | routing for particular domains. The argument of the | |
326 | FEATURE may be the key definition. If none is specified, | |
327 | the definition used is: | |
6e8cccfc | 328 | hash -o /etc/mailertable |
d8b2ad36 EA |
329 | Keys in this database are fully qualified domain names |
330 | or partial domains preceded by a dot -- for example, | |
331 | "vangogh.CS.Berkeley.EDU" or ".CS.Berkeley.EDU". | |
332 | Values must be of the form: | |
3ad658d7 | 333 | mailer:domain |
d8b2ad36 EA |
334 | where "mailer" is the internal mailer name, and "domain" |
335 | is where to send the message. These maps are not | |
336 | reflected into the message header. | |
f51c9ac8 | 337 | |
d8b2ad36 | 338 | domaintable Include a "domain table" which can be used to provide |
e92659a8 EA |
339 | domain name mapping. Use of this should really be |
340 | limited to your own domains. It may be useful if you | |
341 | change names (e.g., your company changes names from | |
342 | oldname.com to newname.com). The argument of the | |
343 | FEATURE may be the key definition. If none is specified, | |
344 | the definition used is: | |
6e8cccfc | 345 | hash -o /etc/domaintable |
e92659a8 EA |
346 | The key in this table is the domain name; the value is |
347 | the new (fully qualified) domain. Anything in the | |
d8b2ad36 EA |
348 | domaintable is reflected into headers; that is, this |
349 | is done in ruleset 3. | |
f51c9ac8 | 350 | |
d1593b1a EA |
351 | bitdomain Look up bitnet hosts in a table to try to turn them into |
352 | internet addresses. The table can be built using the | |
2e9b6f6e | 353 | bitdomain program contributed by John Gardiner Myers. |
d1593b1a EA |
354 | The argument of the FEATURE may be the key definition; if |
355 | none is specified, the definition used is: | |
6e8cccfc | 356 | hash -o /etc/bitdomain.db |
d1593b1a EA |
357 | Keys are the bitnet hostname; values are the corresponding |
358 | internet hostname. | |
f51c9ac8 | 359 | |
4f1c78c0 EA |
360 | uucpdomain Similar feature for UUCP hosts. The default map definition |
361 | is: | |
6e8cccfc | 362 | hash -o /etc/uudomain.db |
4f1c78c0 EA |
363 | At the moment there is no automagic tool to build this |
364 | database. | |
f51c9ac8 | 365 | |
c62d746c EA |
366 | always_add_domain |
367 | Include the local host domain even on locally delivered | |
368 | mail. Normally it is not added unless it is already | |
369 | present. | |
f51c9ac8 | 370 | |
d8b2ad36 EA |
371 | allmasquerade If masquerading is enabled (using MASQUERADE_AS), this |
372 | feature will cause recipient addresses to also masquerade | |
373 | as being from the masquerade host. Normally they get | |
374 | the local hostname. Although this may be right for | |
375 | ordinary users, it can break local aliases. For example, | |
376 | if you send to "localalias", the originating sendmail will | |
377 | find that alias and send to all members, but send the | |
378 | message with "To: localalias@masqueradehost". Since that | |
379 | alias likely does not exist, replies will fail. Use this | |
380 | feature ONLY if you can guarantee that the ENTIRE | |
381 | namespace on your masquerade host supersets all the | |
382 | local entries. | |
f51c9ac8 | 383 | |
2e9b6f6e EA |
384 | nodns We aren't running DNS at our site (for example, |
385 | we are UUCP-only connected). It's hard to consider | |
386 | this a "feature", but hey, it had to go somewhere. | |
4a51b074 | 387 | |
f51c9ac8 EA |
388 | nullclient This is a special case -- it creates a stripped down |
389 | configuration file containing nothing but support for | |
de0c51e7 EA |
390 | forwarding all mail to a central hub via a local |
391 | SMTP-based network. The argument is the name of that | |
392 | hub. | |
393 | ||
394 | The only other feature that should be used in conjunction | |
395 | with this one is "nocanonify" (this causes addresses to | |
396 | be sent unqualified via the SMTP connection; normally | |
397 | they are qualifed with the masquerade name, which | |
398 | defaults to the name of the hub machine). No mailers | |
399 | should be defined. No aliasing or forwarding is done. | |
f51c9ac8 | 400 | |
bee9d799 | 401 | |
4a51b074 EA |
402 | +-------+ |
403 | | HACKS | | |
404 | +-------+ | |
405 | ||
406 | Some things just can't be called features. To make this clear, | |
fd82c288 | 407 | they go in the hack subdirectory and are referenced using the HACK |
4a51b074 EA |
408 | macro. These will tend to be site-dependent. The release |
409 | includes the Berkeley-dependent "cssubdomain" hack (that makes | |
410 | sendmail accept local names in either Berkeley.EDU or CS.Berkeley.EDU; | |
411 | this is intended as a short-term aid while we move hosts into | |
412 | subdomains. | |
413 | ||
bee9d799 | 414 | |
4a51b074 EA |
415 | +--------------------+ |
416 | | SITE CONFIGURATION | | |
417 | +--------------------+ | |
418 | ||
419 | Complex sites will need more local configuration information, such as | |
420 | lists of UUCP hosts they speak with directly. This can get a bit more | |
421 | tricky. For an example of a "complex" site, see cf/ucbvax.mc. | |
422 | ||
c833924a EA |
423 | If your host is known by several different names, you need to augment |
424 | the $=w class. This is a list of names by which you are known, and | |
425 | anything sent to an address using a host name in this list will be | |
426 | treated as local mail. You can do this in two ways: either create | |
427 | the file /etc/sendmail.cw containing a list of your aliases (one per | |
428 | line), and use ``FEATURE(use_cw_file)'' in the .mc file, or add the | |
429 | line: | |
430 | ||
431 | Cw alias.host.name | |
432 | ||
433 | at the end of that file. See the ``vangogh.mc'' file for an example. | |
434 | Be sure you use the fully-qualified name of the host, rather than a | |
435 | short name. | |
436 | ||
4a51b074 EA |
437 | The SITECONFIG macro allows you to indirectly reference site-dependent |
438 | configuration information stored in the siteconfig subdirectory. For | |
439 | example, the line | |
440 | ||
441 | SITECONFIG(uucp.ucbvax, ucbvax, U) | |
442 | ||
443 | reads the file uucp.ucbvax for local connection information. The | |
444 | second parameter is the local name (in this case just "ucbvax" since | |
c833924a EA |
445 | it is locally connected, and hence a UUCP hostname). The third |
446 | parameter is the name of both a macro to store the local name (in | |
447 | this case, $U) and the name of the class (e.g., $=U) in which to store | |
448 | the host information read from the file. Another SITECONFIG line reads | |
4a51b074 EA |
449 | |
450 | SITECONFIG(uucp.ucbarpa, ucbarpa.Berkeley.EDU, W) | |
451 | ||
452 | This says that the file uucp.ucbarpa contains the list of UUCP sites | |
453 | connected to ucbarpa.Berkeley.EDU. The $=W class will be used to | |
c833924a EA |
454 | store this list, and $W is defined to be ucbarpa.Berkeley.EDU, that |
455 | is, the name of the relay to which the hosts listed in uucp.ucbarpa | |
456 | are connected. [The machine ucbarpa is gone now, but I've left | |
4a51b074 EA |
457 | this out-of-date configuration file around to demonstrate how you |
458 | might do this.] | |
459 | ||
c833924a EA |
460 | Note that the case of SITECONFIG with a third parameter of ``U'' is |
461 | special; the second parameter is assumed to be the UUCP name of the | |
462 | local site, rather than the name of a remote site, and the UUCP name | |
463 | is entered into $=w (the list of local hostnames) as $U.UUCP. | |
464 | ||
4a51b074 EA |
465 | The siteconfig file (e.g., siteconfig/uucp.ucbvax.m4) contains nothing |
466 | more than a sequence of SITE macros describing connectivity. For | |
467 | example: | |
468 | ||
469 | SITE(cnmat) | |
470 | SITE(sgi olympus) | |
471 | ||
472 | The second example demonstrates that you can use two names on the | |
473 | same line; these are usually aliases for the same host (or are at | |
474 | least in the same company). | |
475 | ||
bee9d799 | 476 | |
2a20bc94 EA |
477 | +--------------------+ |
478 | | USING UUCP MAILERS | | |
479 | +--------------------+ | |
480 | ||
481 | It's hard to get UUCP mailers right because of the extremely ad hoc | |
482 | nature of UUCP addressing. These config files are really designed | |
483 | for domain-based addressing, even for UUCP sites. | |
484 | ||
485 | There are four UUCP mailers available. The choice of which one to | |
486 | use is partly a matter of local preferences and what is running at | |
487 | the other end of your UUCP connection. Unlike good protocols that | |
488 | define what will go over the wire, UUCP uses the policy that you | |
489 | should do what is right for the other end; if they change, you have | |
490 | to change. This makes it hard to do the right thing, and discourages | |
491 | people from updating their software. In general, if you can avoid | |
492 | UUCP, please do. | |
493 | ||
494 | The major choice is whether to go for a domainized scheme or a | |
495 | non-domainized scheme. This depends entirely on what the other | |
496 | end will recognize. If at all possible, you should encourage the | |
497 | other end to go to a domain-based system -- non-domainized addresses | |
498 | don't work entirely properly. | |
499 | ||
500 | The four mailers are: | |
501 | ||
502 | uucp-old (obsolete name: "uucp") | |
503 | This is the oldest, the worst (but the closest to UUCP) way of | |
504 | sending messages accros UUCP connections. It does bangify | |
505 | everything and prepends $U (your UUCP name) to the sender's | |
506 | address (which can already be a bang path itself). It can | |
507 | only send to one address at a time, so it spends a lot of | |
508 | time copying duplicates of messages. Avoid this if at all | |
509 | possible. | |
510 | ||
511 | uucp-new (obsolete name: "suucp") | |
512 | The same as above, except that it assumes that in one rmail | |
513 | command you can specify several recipients. It still has a | |
514 | lot of other problems. | |
515 | ||
516 | uucp-dom | |
517 | This UUCP mailer keeps everything as domain addresses. | |
41187805 EA |
518 | Basically, it uses the SMTP mailer rewriting rules. This mailer |
519 | is only included if MAILER(smtp) is also specified. | |
2a20bc94 EA |
520 | |
521 | Unfortunately, a lot of UUCP mailer transport agents require | |
522 | bangified addresses in the envelope, although you can use | |
523 | domain-based addresses in the message header. (The envelope | |
524 | shows up as the From_ line on UNIX mail.) So.... | |
525 | ||
526 | uucp-uudom | |
527 | This is a cross between uucp-new (for the envelope addresses) | |
528 | and uucp-dom (for the header addresses). It bangifies the | |
529 | envelope sender (From_ line in messages) without adding the | |
530 | local hostname, unless there is no host name on the address | |
531 | at all (e.g., "wolf") or the host component is a UUCP host name | |
532 | instead of a domain name ("somehost!wolf" instead of | |
41187805 EA |
533 | "some.dom.ain!wolf"). This is also included only if MAILER(smtp) |
534 | is also specified. | |
2a20bc94 EA |
535 | |
536 | Examples: | |
537 | ||
538 | We are on host grasp.insa-lyon.fr (UUCP host name "grasp"). The | |
539 | following summarizes the sender rewriting for various mailers. | |
540 | ||
541 | Mailer sender rewriting in the envelope | |
542 | ------ ------ ------------------------- | |
543 | uucp-{old,new} wolf grasp!wolf | |
544 | uucp-dom wolf wolf@grasp.insa-lyon.fr | |
545 | uucp-uudom wolf grasp.insa-lyon.fr!wolf | |
546 | ||
547 | uucp-{old,new} wolf@fr.net grasp!fr.net!wolf | |
548 | uucp-dom wolf@fr.net wolf@fr.net | |
549 | uucp-uudom wolf@fr.net fr.net!wolf | |
550 | ||
551 | uucp-{old,new} somehost!wolf grasp!somehost!wolf | |
552 | uucp-dom somehost!wolf somehost!wolf@grasp.insa-lyon.fr | |
553 | uucp-uudom somehost!wolf grasp.insa-lyon.fr!somehost!wolf | |
554 | ||
555 | If you are using one of the domainized UUCP mailers, you really want | |
556 | to convert all UUCP addresses to domain format -- otherwise, it will | |
557 | do it for you (and probably not the way you expected). For example, | |
558 | if you have the address foo!bar!baz (and you are not sending to foo), | |
559 | the heuristics will add the @uucp.relay.name or @local.host.name to | |
560 | this address. However, if you map foo to foo.host.name first, it | |
561 | will not add the local hostname. You can do this using the uucpdomain | |
562 | feature. | |
563 | ||
564 | ||
4a51b074 EA |
565 | +-------------------+ |
566 | | TWEAKING RULESETS | | |
567 | +-------------------+ | |
9df1b56b EA |
568 | |
569 | For more complex configurations, you can define special rules. | |
570 | The macro LOCAL_RULE_3 introduces rules that are used in canonicalizing | |
571 | the names. Any modifications made here are reflected in the header. | |
572 | ||
573 | A common use is to convert old UUCP addreses to SMTP addresses using | |
574 | the UUCPSMTP macro. For example: | |
575 | ||
576 | LOCAL_RULE_3 | |
577 | UUCPSMTP(decvax, decvax.dec.com) | |
578 | UUCPSMTP(research, research.att.com) | |
579 | ||
580 | will cause addresses of the form "decvax!user" and "research!user" | |
581 | to be converted to "user@decvax.dec.com" and "user@research.att.com" | |
582 | respectively. | |
583 | ||
6fb312a3 | 584 | This could also be used to look up hosts in a database map: |
4a51b074 EA |
585 | |
586 | LOCAL_RULE_3 | |
587 | R$* < @ $+ > $* $: $1 < @ $(hostmap $2 $) > $3 | |
588 | ||
589 | This map would be defined in the LOCAL_CONFIG portion, as shown below. | |
590 | ||
9df1b56b EA |
591 | Similarly, LOCAL_RULE_0 can be used to introduce new parsing rules. |
592 | For example, new rules are needed to parse hostnames that you accept | |
c573210d EA |
593 | via MX records. For example, you might have: |
594 | ||
595 | LOCAL_RULE_0 | |
2c56efa0 | 596 | R$+ <@ host.dom.ain.> $#uucp $@ cnmat $: $1 < @ host.dom.ain.> |
c573210d EA |
597 | |
598 | You would use this if you had installed an MX record for cnmat.Berkeley.EDU | |
599 | pointing at this host; this rule catches the message and forwards it on | |
600 | using UUCP. | |
9df1b56b | 601 | |
06630be3 EA |
602 | You can also tweak rulesets 1 and 2 using LOCAL_RULE_1 and LOCAL_RULE_2. |
603 | These rulesets are normally empty. | |
604 | ||
4a51b074 EA |
605 | A similar macro is LOCAL_CONFIG. This introduces lines added after the |
606 | boilerplate option setting but before rulesets, and can be used to | |
a151c868 | 607 | declare local database maps or whatever. For example: |
4a51b074 EA |
608 | |
609 | LOCAL_CONFIG | |
610 | Khostmap hash /etc/hostmap.db | |
611 | Kyplocal nis -m hosts.byname | |
4a51b074 | 612 | |
bee9d799 | 613 | |
4a51b074 EA |
614 | +---------------------------+ |
615 | | MASQUERADING AND RELAYING | | |
616 | +---------------------------+ | |
617 | ||
618 | You can have your host masquerade as another using | |
619 | ||
620 | MASQUERADE_AS(host.domain) | |
9df1b56b | 621 | |
6fb312a3 | 622 | This causes outgoing SMTP mail to be labeled as coming from the |
4a51b074 | 623 | indicated domain, rather than $j. One normally masquerades as one |
6fb312a3 | 624 | of one's own subdomains (for example, it's unlikely that I would |
4a51b074 EA |
625 | choose to masquerade as an MIT site). |
626 | ||
2e9b6f6e EA |
627 | The masquerade name is not normally canonified, so it is important |
628 | that it be your One True Name, that is, fully qualified and not a | |
629 | CNAME. | |
630 | ||
4a51b074 EA |
631 | there are always users that need to be "exposed" -- that is, their |
632 | internal site name should be displayed instead of the masquerade name. | |
633 | Root is an example. You can add users to this list using | |
634 | ||
635 | EXPOSED_USER(usernames) | |
636 | ||
637 | This adds users to class E; you could also use something like | |
638 | ||
639 | FE/etc/sendmail.cE | |
640 | ||
641 | You can also arrange to relay all unqualified names (that is, names | |
642 | without @host) to a relay host. For example, if you have a central | |
643 | email server, you might relay to that host so that users don't have | |
644 | to have .forward files or aliases. You can do this using | |
645 | ||
28b51619 | 646 | define(`LOCAL_RELAY', mailer:hostname) |
4a51b074 | 647 | |
28b51619 EA |
648 | The ``mailer:'' can be omitted, in which case the mailer defaults to |
649 | "smtp". There are some user names that you don't want relayed, perhaps | |
650 | because of local aliases. A common example is root, which may be | |
651 | locally aliased. You can add entries to this list using | |
4a51b074 EA |
652 | |
653 | LOCAL_USER(usernames) | |
654 | ||
655 | This adds users to class L; you could also use something like | |
656 | ||
657 | FL/etc/sendmail.cL | |
658 | ||
2e9b6f6e EA |
659 | If you want all incoming mail sent to a centralized hub, as for a |
660 | shared /var/spool/mail scheme, use | |
34e49bd3 | 661 | |
28b51619 | 662 | define(`MAIL_HUB', mailer:hostname) |
34e49bd3 | 663 | |
28b51619 | 664 | Again, ``mailer:'' defaults to "smtp". If you define both LOCAL_RELAY |
0ee1617f EA |
665 | and MAIL_HUB, unqualified names will be sent to the LOCAL_RELAY and |
666 | other local names will be sent to MAIL_HUB. Names in $=L will be | |
667 | delivered locally, so you MUST have aliases or .forward files for them. | |
668 | ||
669 | For example, if are on machine mastodon.CS.Berkeley.EDU, the following | |
28b51619 | 670 | combinations of settings will have the indicated effects: |
34e49bd3 EA |
671 | |
672 | email sent to.... eric eric@mastodon.CS.Berkeley.EDU | |
673 | ||
674 | LOCAL_RELAY set to mail.CS.Berkeley.EDU (delivered locally) | |
675 | mail.CS.Berkeley.EDU | |
676 | ||
677 | MAIL_HUB set to mammoth.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU | |
678 | mammoth.CS.Berkeley.EDU | |
679 | ||
680 | Both LOCAL_RELAY and mail.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU | |
681 | MAIL_HUB set as above | |
682 | ||
2e9b6f6e EA |
683 | If you want all outgoing mail to go to a central relay site, define |
684 | SMART_HOST as well. Briefly: | |
685 | ||
686 | LOCAL_RELAY applies to unqualifed names (e.g., "eric"). | |
687 | MAIL_HUB applies to names qualified with the name of the | |
688 | local host (e.g., "eric@mastodon.CS.Berkeley.EDU"). | |
689 | SMART_HOST applies to names qualified with other hosts. | |
690 | ||
691 | However, beware that other relays (e.g., UUCP_RELAY, BITNET_RELAY, and | |
692 | FAX_RELAY) take precedence over SMART_HOST, so if you really want | |
693 | absolutely everything to go to a single central site you will need to | |
694 | unset all the other relays -- or better yet, find or build a minimal | |
695 | config file that does this. | |
696 | ||
28b51619 EA |
697 | |
698 | +-------------------------------+ | |
699 | | NON-SMTP BASED CONFIGURATIONS | | |
700 | +-------------------------------+ | |
701 | ||
702 | These configuration files are designed primarily for use by SMTP-based | |
703 | sites. I don't pretend that they are well tuned for UUCP-only or | |
704 | UUCP-primarily nodes (the latter is defined as a small local net | |
705 | connected to the rest of the world via UUCP). However, there is one | |
706 | hook to handle some special cases. | |
707 | ||
708 | You can define a ``smart host'' that understands a richer address syntax | |
709 | using: | |
710 | ||
711 | define(`SMART_HOST', mailer:hostname) | |
712 | ||
bb3c21c3 | 713 | In this case, the ``mailer:'' defaults to "relay". Any messages that |
28b51619 EA |
714 | can't be handled using the usual UUCP rules are passed to this host. |
715 | ||
716 | If you are on a local SMTP-based net that connects to the outside | |
717 | world via UUCP, you can use LOCAL_NET_CONFIG to add appropriate rules. | |
718 | For example: | |
719 | ||
720 | define(`SMART_HOST', suucp:uunet) | |
721 | LOCAL_NET_CONFIG | |
d8b2ad36 | 722 | R$* < @ $* .$m. > $* $#smtp $@ $2.$m. $: $1 < @ $2.$m. > $3 |
28b51619 EA |
723 | |
724 | This will cause all names that end in your domain name ($m) via | |
725 | SMTP; anything else will be sent via suucp (smart UUCP) to uunet. | |
d8b2ad36 EA |
726 | If you have FEATURE(nocanonify), you may need to omit the dots after |
727 | the $m. If you are running a local DNS inside your domain which is | |
728 | not otherwise connected to the outside world, you probably want to | |
729 | use: | |
730 | ||
731 | define(`SMART_HOST', smtp:fire.wall.com) | |
732 | LOCAL_NET_CONFIG | |
733 | R$* < @ $* . > $* $#smtp $@ $2. $: $1 < @ $2. > $3 | |
734 | ||
735 | That is, send directly only to things you found in your DNS lookup; | |
736 | anything else goes through SMART_HOST. | |
28b51619 | 737 | |
2e9b6f6e EA |
738 | If you are not running DNS at all, it is important to use |
739 | FEATURE(nodns) to avoid having sendmail queue everything waiting | |
740 | for the name server to come up. | |
741 | ||
28b51619 | 742 | |
f7e8be31 EA |
743 | +-----------+ |
744 | | WHO AM I? | | |
745 | +-----------+ | |
746 | ||
747 | Normally, the $j macro is automatically defined to be your fully | |
748 | qualified domain name (FQDN). Sendmail does this by getting your | |
749 | host name using gethostname and then calling gethostbyname on the | |
750 | result. For example, in some environments gethostname returns | |
751 | only the root of the host name (such as "foo"); gethostbyname is | |
752 | supposed to return the FQDN ("foo.bar.com"). In some (fairly rare) | |
753 | cases, gethostbyname may fail to return the FQDN. In this case | |
754 | you MUST define confDOMAIN_NAME to be your fully qualified domain | |
755 | name. This is usually done using: | |
756 | ||
757 | Dmbar.com | |
758 | define(`confDOMAIN_NAME', `$w.$m')dnl | |
759 | ||
760 | ||
bb3c21c3 EA |
761 | +--------------------+ |
762 | | USING MAILERTABLES | | |
763 | +--------------------+ | |
764 | ||
765 | To use FEATURE(mailertable), you will have to create an external | |
766 | database containing the routing information for various domains. | |
767 | For example, a mailertable file in text format might be: | |
768 | ||
769 | .my.domain xnet:%1.my.domain | |
770 | uuhost1.my.domain suucp:uuhost1 | |
771 | .bitnet smtp:relay.bit.net | |
772 | ||
773 | This should normally be stored in /etc/mailertable. The actual | |
774 | database version of the mailertable is built using: | |
775 | ||
776 | makemap hash /etc/mailertable.db < /etc/mailertable | |
777 | ||
778 | The semantics are simple. Any LHS entry that does not begin with | |
779 | a dot matches the full host name indicated. LHS entries beginning | |
780 | with a dot match anything ending with that domain name -- that is, | |
781 | they can be thought of as having a leading "*" wildcard. Matching | |
782 | is done in order of most-to-least qualified -- for example, even | |
783 | though ".my.domain" is listed first in the above example, an entry | |
784 | of "uuhost1.my.domain" will match the second entry since it is | |
785 | more explicit. | |
786 | ||
787 | The RHS should always be a "mailer:host" pair. The mailer is the | |
788 | configuration name of a mailer (that is, an `M' line in the | |
789 | sendmail.cf file). The "host" will be the hostname passed to | |
790 | that mailer. In domain-based matches (that is, those with leading | |
791 | dots) the "%1" may be used to interpolate the wildcarded part of | |
792 | the host name. For example, the first line above sends everything | |
793 | addressed to "anything.my.domain" to that same host name, but using | |
794 | the (presumably experimental) xnet mailer. | |
795 | ||
796 | ||
2e9b6f6e EA |
797 | +--------------------------------+ |
798 | | USING USERDB TO MAP FULL NAMES | | |
799 | +--------------------------------+ | |
800 | ||
801 | The user database was not originally intended for mapping full names | |
802 | to login names (e.g., Eric.Allman => eric), but some people are using | |
803 | it that way. (I would recommend that you set up aliases for this | |
804 | purpose instead -- since you can specify multiple alias files, this | |
805 | is fairly easy.) The intent was to locate the default maildrop at | |
806 | a site, but allow you to override this by sending to a specific host. | |
807 | ||
808 | If you decide to set up the user database in this fashion, it is | |
809 | imperative that you also specify FEATURE(notsticky) -- otherwise, | |
810 | e-mail sent to Full.Name@local.host.name will be rejected. | |
811 | ||
f7e8be31 EA |
812 | To build the internal form of the user databae, use: |
813 | ||
814 | makemap btree /usr/data/base.db < /usr/data/base.txt | |
815 | ||
2e9b6f6e | 816 | |
f4d9c9f9 EA |
817 | +--------------------------------+ |
818 | | MISCELLANEOUS SPECIAL FEATURES | | |
819 | +--------------------------------+ | |
820 | ||
821 | DOTTED_USER(name) | |
822 | Sometimes it is convenient to merge configuration on a | |
823 | centralized mail machine, for example, to forward all | |
824 | root mail to a mail server. In this case it might be | |
825 | useful to be able to treat the root addresses as a class | |
826 | of addresses with subtle differences. You can do this | |
827 | using dotted users. For example, a client might include | |
828 | the alias: | |
829 | ||
830 | root: root.client1@server | |
831 | ||
832 | On the server, the mail configuration would include: | |
833 | ||
834 | DOTTED_USER(root) | |
835 | ||
836 | Aliases on the server that would match this address would | |
837 | be "root.client", "root.*", and "root", tried in that | |
838 | order. You can specify multiple addresses either by | |
839 | joining them in one DOTTTED_USER macro or by having | |
840 | multiple macros: | |
841 | ||
842 | DOTTED_USER(root) | |
843 | DOTTED_USER(postmaster mailer-daemon) | |
844 | ||
845 | defines three dotted users. | |
846 | ||
847 | ||
63013ec3 EA |
848 | +------------------+ |
849 | | FlexFAX SOFTWARE | | |
850 | +------------------+ | |
851 | ||
852 | Sam Leffler's FlexFAX software is still in beta test -- but he expects a | |
853 | public version out "later this week" [as of 3/1/93]. The following | |
854 | blurb is direct from Sam: | |
855 | ||
d1ad6cf3 | 856 | $Header: /usr/people/sam/fax/RCS/HOWTO,v 1.14 93/05/24 11:42:16 sam Exp $ |
63013ec3 EA |
857 | |
858 | How To Obtain This Software (in case all you get is this file) | |
d1ad6cf3 | 859 | -------------------------------------------------------------- |
63013ec3 | 860 | The source code is available for public ftp on |
d1ad6cf3 | 861 | sgi.com sgi/fax/v2.1.src.tar.Z |
63013ec3 EA |
862 | (192.48.153.1) |
863 | ||
864 | You can also obtain inst'able images for Silicon Graphics machines from | |
d1ad6cf3 | 865 | sgi.com sgi/fax/v2.1.inst.tar |
63013ec3 EA |
866 | (192.48.153.1) |
867 | ||
868 | For example, | |
869 | % ftp -n sgi.com | |
870 | .... | |
871 | ftp> user anonymous | |
872 | ... <type in password> | |
873 | ftp> cd sgi/fax | |
874 | ftp> binary | |
d1ad6cf3 EA |
875 | ftp> get v2.1.src.tar.Z |
876 | ||
877 | In general, the latest version of the 2.1 release of the software is | |
878 | always available as "v2.1.src.tar.Z" or "v2.1.inst.tar" in the ftp | |
879 | directory. This file is a link to the appropriate released version (so | |
880 | don't waste your time retrieving the linked file as well!) Any files of | |
881 | the form v2.1.*.patch are shell scripts that can be used to patch older | |
882 | versions of the source code. For example, the file v2.1.0.patch would | |
883 | contain patches to update v2.1.0.tar.Z. (Note to beta testers: this is | |
884 | different than the naming conventions used during beta testing.) Patch | |
885 | files only work to go between consecutive versions, so if you are | |
886 | multiple versions behind the latest release, you will need to apply | |
887 | each patch file between your current version and the latest. | |
888 | ||
889 | ||
890 | Obtaining the Software by Electronic Mail | |
891 | ----------------------------------------- | |
892 | Do not send me requests for the software; they will be ignored (without | |
893 | response). If you cannot use FTP at all, there is a service called | |
894 | "ftpmail" available from gatekeeper.dec.com: you can send e-mail to | |
895 | this machine and it will use FTP to retrieve files for you and send you | |
896 | the files back again via e-mail. To find out more about the ftpmail | |
63013ec3 EA |
897 | service, send a message to "ftpmail@gatekeeper.dec.com" whose body |
898 | consists of the single line "help". | |
899 | ||
d1ad6cf3 EA |
900 | |
901 | Obtaining the Software Within Silicon Graphics | |
902 | ---------------------------------------------- | |
63013ec3 | 903 | Internal to Silicon Graphics there are inst'able images on the host |
d1ad6cf3 | 904 | flake.asd in the directory /usr/dist. Thus you can do something like: |
63013ec3 | 905 | |
d1ad6cf3 | 906 | % inst -f flake.asd.sgi.com:/usr/dist/flexfax |
63013ec3 | 907 | |
d1ad6cf3 | 908 | to install the latest version of the software on your machine. |
63013ec3 | 909 | |
d1ad6cf3 EA |
910 | |
911 | What to do Once You've Retrieved Stuff | |
912 | -------------------------------------- | |
63013ec3 EA |
913 | The external distributions come in a compressed or uncompressed tar |
914 | file. To extract the source distribution: | |
915 | ||
d1ad6cf3 | 916 | % zcat v2.1.src.tar.Z | tar xf - |
63013ec3 EA |
917 | |
918 | (uncompress and extract individual files in current directory). To | |
919 | unpack and install the client portion of the inst'able distribution: | |
920 | ||
921 | % mkdir dist | |
d1ad6cf3 | 922 | % cd dist; tar xf ../v2.1.inst.tar; cd .. |
63013ec3 EA |
923 | % inst -f dist/flexfax |
924 | ... | |
925 | inst> go | |
926 | ||
927 | (Note, the dist subdirectory is because some versions of inst fail if | |
d1ad6cf3 EA |
928 | the files are in the current directory.) Server binaries are also |
929 | included in the inst'able images as flexfax.server.*. They are not | |
930 | installed by default, so to get them also you need to do: | |
63013ec3 EA |
931 | |
932 | % inst -f flexfax | |
933 | ... | |
934 | inst> install flexfax.server.* | |
935 | inst> go | |
936 | ||
d1ad6cf3 | 937 | The SGI binaries were built for Version 4.0.5H of the IRIX operating |
63013ec3 EA |
938 | system. They should work w/o problem on earlier versions of the |
939 | system, but I have not fully tested this. Also, note that to install a | |
940 | server on an SGI machine, you need to have installed the Display | |
941 | PostScript execution environment product (dps_eoe). Otherwise, the fax | |
942 | server will not be able to convert PostScript to facsimile for | |
943 | transmission. | |
944 | ||
d1ad6cf3 EA |
945 | If you are working from the source distribution, look at the file |
946 | README in the top of the source tree. If you are working from the inst | |
947 | images, the subsystem flexfax.man.readme contains the README file and | |
948 | other useful pieces of information--the installed files are placed in | |
949 | the directory /usr/local/doc/flexfax). Basically you will need to run | |
950 | the faxaddmodem script to setup and configure your fax modem. Consult | |
951 | the README file and the manual page for faxaddmodem for information. | |
63013ec3 | 952 | |
63013ec3 | 953 | |
d1ad6cf3 EA |
954 | FlexFAX Mail List |
955 | ----------------- | |
63013ec3 EA |
956 | A mailing list for users of this software is located on sgi.com. |
957 | If you want to join this mailing list or have a list-related request | |
958 | such as getting your name removed from it, send a request to | |
959 | ||
d1ad6cf3 EA |
960 | majordomo@whizzer.wpd.sgi.com |
961 | ||
962 | For example, to subscribe, send the line "subscribe flexfax" in | |
963 | the body of your message. The line "help" will return a list of | |
964 | the commands understood by the mailing list management software. | |
63013ec3 EA |
965 | |
966 | Submissions (including bug reports) should be directed to: | |
967 | ||
968 | flexfax@sgi.com | |
969 | ||
d1ad6cf3 EA |
970 | When corresponding about this software please always specify what |
971 | version you have, what system you're running on, and, if the problem is | |
972 | specific to your modem, identify the modem and firmware revision. | |
973 | ||
63013ec3 | 974 | |
a151c868 EA |
975 | +--------------------------------+ |
976 | | TWEAKING CONFIGURATION OPTIONS | | |
977 | +--------------------------------+ | |
978 | ||
979 | There are a large number of configuration options that don't normally | |
980 | need to be changed. However, if you feel you need to tweak them, you | |
981 | can define the following M4 variables. This list is shown in four | |
982 | columns: the name you define, the default value for that definition, | |
983 | the option or macro that is affected (either Ox for an option or Dx | |
984 | for a macro), and a brief description. Greater detail of the semantics | |
985 | can be found in the Installation and Operations Guide. | |
986 | ||
fb32c2a1 EA |
987 | Some options are likely to be deprecated in future versions -- that is, |
988 | the option is only included to provide back-compatibility. These are | |
989 | marked with "*". | |
990 | ||
a7e36c1b EA |
991 | Remember that these options are M4 variables, and hence may need to |
992 | be quoted. In particular, arguments with commas will usually have to | |
993 | be ``double quoted, like this phrase'' to avoid having the comma | |
994 | confuse things. This is common for alias file definitions and for | |
995 | the read timeout. | |
996 | ||
a151c868 | 997 | M4 Variable Name Default Mac/Opt Description |
a7e36c1b | 998 | ================ ======= ======= =========== |
a151c868 EA |
999 | confMAILER_NAME MAILER-DAEMON Dn The sender name used for |
1000 | internally generated | |
1001 | outgoing messages. | |
06630be3 EA |
1002 | confFROM_LINE From $g $d Dl The From_ line used when |
1003 | sending to files or programs. | |
a151c868 EA |
1004 | confFROM_HEADER $?x$x <$g>$|$g$. The format of an internally |
1005 | Dq generated From: address. | |
1006 | confOPERATORS .:%@!^/[] Do Address operator characters. | |
2e9b6f6e | 1007 | confSMTP_LOGIN_MSG $j Sendmail $v/$Z ready at $b |
a151c868 EA |
1008 | De The initial (spontaneous) |
1009 | SMTP greeting message. | |
f6232b5e | 1010 | confSEVEN_BIT_INPUT False O7 Force input to seven bits? |
eb802161 | 1011 | confEIGHT_BIT_HANDLING pass8 O8 8-bit data handling |
a151c868 EA |
1012 | confALIAS_WAIT 10 Oa Wait (in minutes) for alias |
1013 | file rebuild. | |
bee9d799 EA |
1014 | confMIN_FREE_BLOCKS 4 Ob Minimum number of free blocks |
1015 | on queue filesystem to accept | |
1016 | SMTP mail. | |
a151c868 EA |
1017 | confBLANK_SUB . OB Blank (space) substitution |
1018 | character. | |
e9cedcc1 EA |
1019 | confCON_EXPENSIVE False Oc Avoid connecting immediately |
1020 | to mailers marked expensive? | |
a151c868 EA |
1021 | confCHECKPOINT_INTERVAL 10 OC Checkpoint queue files |
1022 | every N recipients. | |
1023 | confDELIVERY_MODE background Od Default delivery mode. | |
1024 | confAUTO_REBUILD False OD Automatically rebuild | |
1025 | alias file if needed. | |
1026 | confERROR_MODE (undefined) Oe Error message mode. | |
1027 | confERROR_MESSAGE (undefined) OE Error message header/file. | |
1028 | confSAVE_FROM_LINES False Of Save extra leading | |
1029 | From_ lines. | |
1030 | confTEMP_FILE_MODE 0600 OF Temporary file mode. | |
1031 | confDEF_GROUP_ID 1 Og Default group id. | |
1032 | confMATCH_GECOS False OG Match GECOS field. | |
1033 | confMAX_HOP 17 Oh Maximum hop count. | |
fb32c2a1 | 1034 | confIGNORE_DOTS False Oi * Ignore dot as terminator |
a151c868 EA |
1035 | for incoming messages? |
1036 | confBIND_OPTS (empty) OI Default options for BIND. | |
fb32c2a1 | 1037 | confMIME_FORMAT_ERRORS True Oj * Send error messages as MIME- |
f6232b5e EA |
1038 | encapsulated messages per |
1039 | RFC 1344. | |
2e9b6f6e EA |
1040 | confFORWARD_PATH (undefined) OJ The colon-separated list of |
1041 | places to search for .forward | |
1042 | files. | |
a151c868 EA |
1043 | confMCI_CACHE_SIZE 2 Ok Size of open connection cache. |
1044 | confMCI_CACHE_TIMEOUT 5m OK Open connection cache timeout. | |
fb32c2a1 EA |
1045 | confUSE_ERRORS_TO False Ol * Use the Errors-To: header to |
1046 | deliver error messages. This | |
1047 | should not be necessary because | |
1048 | of general acceptance of the | |
1049 | envelope/header distinction. | |
a151c868 EA |
1050 | confLOG_LEVEL 9 OL Log level. |
1051 | confME_TOO False Om Include sender in group | |
1052 | expansions. | |
1053 | confCHECK_ALIASES True On Check RHS of aliases when | |
1054 | running newaliases. | |
fb32c2a1 | 1055 | confOLD_STYLE_HEADERS True Oo * Assume that headers without |
a151c868 | 1056 | special chars are old style. |
4c230f32 | 1057 | confDAEMON_OPTIONS (undefined) OO SMTP daemon options. |
88ce9b1c | 1058 | confPRIVACY_FLAGS authwarnings Op Privacy flags. |
a151c868 EA |
1059 | confCOPY_ERRORS_TO (undefined) OP Address for additional copies |
1060 | of all error messages. | |
1061 | confQUEUE_FACTOR (undefined) Oq Slope of queue-only function | |
33f90dbe | 1062 | confREAD_TIMEOUT (undefined) Or SMTP read timeouts. |
fb32c2a1 | 1063 | confSAFE_QUEUE True Os * Commit all messages to disk |
a151c868 | 1064 | before forking. |
88ce9b1c EA |
1065 | confMESSAGE_TIMEOUT 5d/4h OT Timeout for messages before |
1066 | sending error/warning message. | |
386fe59f | 1067 | confTIME_ZONE USE_SYSTEM Ot Time zone info -- can be |
a151c868 EA |
1068 | USE_SYSTEM to use the system's |
1069 | idea, USE_TZ to use the user's | |
1070 | TZ envariable, or something | |
1071 | else to force that value. | |
1072 | confDEF_USER_ID 1 Ou Default user id. | |
39ed20b0 | 1073 | confUSERDB_SPEC (undefined) OU User database specification. |
4c230f32 | 1074 | confFALLBACK_MX (undefined) OV Fallback MX host. |
5dd53c38 EA |
1075 | confTRY_NULL_MX_LIST False Ow If we are the best MX for a |
1076 | host and haven't made other | |
1077 | arrangements, try connecting | |
1078 | to the host directly; normally | |
1079 | this would be a config error. | |
a151c868 EA |
1080 | confQUEUE_LA 8 Ox Load average at which queue-only |
1081 | function kicks in. | |
1082 | confREFUSE_LA 12 OX Load average at which incoming | |
1083 | SMTP connections are refused. | |
a151c868 | 1084 | confWORK_RECIPIENT_FACTOR |
fb32c2a1 EA |
1085 | (undefined) Oy Cost of each recipient. |
1086 | confSEPARATE_PROC False OY Run all deliveries in a | |
1087 | separate process. | |
a151c868 EA |
1088 | confWORK_CLASS_FACTOR (undefined) Oz Priority multiplier for class. |
1089 | confWORK_TIME_FACTOR (undefined) OZ Cost of each delivery attempt. | |
dec2b686 EA |
1090 | confCW_FILE /etc/sendmail.cw Name of file used to get the |
1091 | Fw local additions to the $=w | |
1092 | class. | |
2e9b6f6e | 1093 | confSMTP_MAILER smtp - The mailer name used when |
cf36aa8d EA |
1094 | SMTP connectivity is required. |
1095 | Either "smtp" or "esmtp". | |
2c840221 EA |
1096 | confLOCAL_MAILER local - The mailer name used when |
1097 | local connectivity is required. | |
1098 | Almost always "local". | |
bb3c21c3 EA |
1099 | confRELAY_MAILER relay - The default mailer name used |
1100 | for relaying any mail (e.g., | |
1101 | to a BITNET_RELAY, a | |
1102 | SMART_HOST, or whatever). | |
1103 | This can reasonably be "suucp" | |
1104 | if you are on a UUCP-connected | |
1105 | site. | |
f7e8be31 | 1106 | confDOMAIN_NAME (undefined) Dj If defined, sets $j. |
a151c868 | 1107 | |
bee9d799 | 1108 | |
4a51b074 EA |
1109 | +-----------+ |
1110 | | HIERARCHY | | |
1111 | +-----------+ | |
7ace9d88 EA |
1112 | |
1113 | Within this directory are several subdirectories, to wit: | |
1114 | ||
1115 | m4 General support routines. These are typically | |
1116 | very important and should not be changed without | |
fd82c288 | 1117 | very careful consideration. |
7ace9d88 EA |
1118 | |
1119 | cf The configuration files themselves. They have | |
1120 | ".mc" suffixes, and must be run through m4 to | |
1121 | become complete. The resulting output should | |
1122 | have a ".cf" suffix. | |
1123 | ||
1124 | ostype Definitions describing a particular operating | |
1125 | system type. These should always be referenced | |
1126 | using the OSTYPE macro in the .mc file. Examples | |
1127 | include "bsd4.3", "bsd4.4", "sunos3.5", and | |
1128 | "sunos4.1". | |
1129 | ||
1130 | domain Definitions describing a particular domain, referenced | |
1131 | using the DOMAIN macro in the .mc file. These are | |
1132 | site dependent; for example, we contribute "cs.exposed.m4" | |
1133 | and "cs.hidden.m4" which both describe hosts in the | |
1134 | CS.Berkeley.EDU subdomain; the former displays the local | |
1135 | hostname (e.g., mammoth.CS.Berkeley.EDU), whereas the | |
1136 | latter does its best to hide the identity of the local | |
1137 | workstation inside the CS subdomain. | |
1138 | ||
1139 | mailer Descriptions of mailers. These are referenced using | |
1140 | the MAILER macro in the .mc file. | |
1141 | ||
1142 | sh Shell files used when building the .cf file from the | |
1143 | .mc file in the cf subdirectory. | |
1144 | ||
1145 | feature These hold special orthogonal features that you might | |
1146 | want to include. They should be referenced using | |
1147 | the FEATURE macro. | |
1148 | ||
1149 | hack Local hacks. These can be referenced using the HACK | |
1150 | macro. They shouldn't be of more than voyeuristic | |
1151 | interest outside the .Berkeley.EDU domain, but who knows? | |
6fb312a3 | 1152 | We've all got our own peccadillos. |
7ace9d88 | 1153 | |
9df1b56b EA |
1154 | siteconfig Site configuration -- e.g., tables of locally connected |
1155 | UUCP sites. | |
1156 | ||
7ace9d88 | 1157 | |
4a51b074 EA |
1158 | +------------------------+ |
1159 | | ADMINISTRATIVE DETAILS | | |
1160 | +------------------------+ | |
7ace9d88 EA |
1161 | |
1162 | The following sections detail usage of certain internal parts of the | |
1163 | sendmail.cf file. Read them carefully if you are trying to modify | |
1164 | the current model. If you find the above descriptions adequate, these | |
1165 | should be {boring, confusing, tedious, ridiculous} (pick one or more). | |
1166 | ||
1167 | RULESETS (* means built in to sendmail) | |
1168 | ||
1169 | 0 * Parsing | |
1170 | 1 * Sender rewriting | |
1171 | 2 * Recipient rewriting | |
1172 | 3 * Canonicalization | |
1173 | 4 * Post cleanup | |
f5baef19 | 1174 | 5 * Local address rewrite (after aliasing) |
b197efaa EA |
1175 | 1x mailer rules (sender qualification) |
1176 | 2x mailer rules (recipient qualification) | |
0409c6a2 EA |
1177 | 3x mailer rules (sender header qualification) |
1178 | 4x mailer rules (recipient header qualification) | |
1179 | 5x mailer subroutines (general) | |
1180 | 6x mailer subroutines (general) | |
1181 | 7x mailer subroutines (general) | |
1182 | 8x reserved | |
b197efaa | 1183 | 90 Mailertable host stripping |
f7ffd8e3 EA |
1184 | 96 Bottom half of Ruleset 3 (ruleset 6 in old sendmail) |
1185 | 97 Hook for recursive ruleset 0 call (ruleset 7 in old sendmail) | |
5dd53c38 | 1186 | 98 Local part of ruleset 0 (ruleset 8 in old sendmail) |
7ace9d88 EA |
1187 | |
1188 | ||
1189 | MAILERS | |
1190 | ||
1191 | 0 local, prog local and program mailers | |
2a20bc94 EA |
1192 | 1 [e]smtp, relay SMTP channel |
1193 | 2 uucp-* UNIX-to-UNIX Copy Program | |
bee9d799 | 1194 | 3 netnews Network News delivery |
63013ec3 | 1195 | 4 fax Sam Leffler's FlexFAX software |
7ace9d88 EA |
1196 | |
1197 | ||
1198 | MACROS | |
1199 | ||
1200 | A | |
1201 | B Bitnet Relay | |
72a40e6d | 1202 | C |
f5baef19 | 1203 | D The local domain -- usually not needed |
7ace9d88 | 1204 | E |
63013ec3 | 1205 | F FAX Relay |
7ace9d88 | 1206 | G |
34e49bd3 | 1207 | H mail Hub (for mail clusters) |
7ace9d88 EA |
1208 | I |
1209 | J | |
1210 | K | |
1211 | L | |
1212 | M Masquerade (who I claim to be) | |
1213 | N | |
1214 | O | |
1215 | P | |
1216 | Q | |
1217 | R Relay (for unqualified names) | |
28b51619 | 1218 | S Smart Host |
7ace9d88 | 1219 | T |
c573210d EA |
1220 | U my UUCP name (if I have a UUCP connection) |
1221 | V UUCP Relay (class V hosts) | |
7ace9d88 EA |
1222 | W UUCP Relay (class W hosts) |
1223 | X UUCP Relay (class X hosts) | |
c573210d | 1224 | Y UUCP Relay (all other hosts) |
7ace9d88 EA |
1225 | Z Version number |
1226 | ||
1227 | ||
1228 | CLASSES | |
1229 | ||
1230 | A | |
1231 | B | |
1232 | C | |
f4d9c9f9 | 1233 | D "dotted" users |
4a51b074 | 1234 | E addresses that should not seem to come from $M |
f5baef19 | 1235 | F hosts we forward for |
7ace9d88 EA |
1236 | G |
1237 | H | |
1238 | I | |
1239 | J | |
1240 | K | |
1241 | L addresses that should not be forwarded to $R | |
1242 | M | |
1243 | N | |
1244 | O operators that indicate network operations (cannot be in local names) | |
91626fee | 1245 | P top level pseudo-domains: BITNET, FAX, UUCP, etc. |
7ace9d88 EA |
1246 | Q |
1247 | R | |
1248 | S | |
1249 | T | |
1250 | U locally connected UUCP hosts | |
c573210d EA |
1251 | V UUCP hosts connected to relay $V |
1252 | W UUCP hosts connected to relay $W | |
1253 | X UUCP hosts connected to relay $X | |
1254 | Y locally connected smart UUCP hosts | |
2e9b6f6e | 1255 | Z locally connected domain-ized UUCP hosts |
f5baef19 | 1256 | . the class containing only a dot |
7ace9d88 EA |
1257 | |
1258 | ||
1259 | M4 DIVERSIONS | |
1260 | ||
28b51619 EA |
1261 | 1 Local host detection and resolution |
1262 | 2 Local Ruleset 3 additions | |
1263 | 3 Local Ruleset 0 additions | |
9df1b56b | 1264 | 4 UUCP Ruleset 0 additions |
c573210d | 1265 | 5 locally interpreted names (overrides $R) |
f5baef19 | 1266 | 6 local configuration (at top of file) |
7ace9d88 | 1267 | 7 mailer definitions |
32f9e686 | 1268 | 8 |
06630be3 | 1269 | 9 special local rulesets (1 and 2) |