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