1 2 3 NEW SENDMAIL CONFIGURATION FILES 4 5 Eric Allman <eric@CS.Berkeley.EDU> 6 7 @(#)README 8.35 (Berkeley) 10/16/94 8 9 10This document describes the sendmail configuration files being used 11at Berkeley. These use features in the new (R8) sendmail; they will 12not work on other versions. 13 14These configuration files are probably not as general as previous 15versions, and don't handle as many of the weird cases automagically. 16I was able to simplify by them for two reasons. First, the network 17has become more consistent -- for example, at this point, everyone 18on the internet is supposed to be running a name server, so hacks to 19handle NIC-registered hosts can go away. Second, I assumed that a 20subdomain would be running SMTP internally -- UUCP is presumed to be 21a long-haul protocol. I realize that this is not universal, but it 22does describe the vast majority of sites with which I am familiar, 23including those outside the US. 24 25Of course, the downside of this is that if you do live in a weird 26world, things are going to get weirder for you. I'm sorry about that, 27but at the time we at Berkeley had a problem, and it seemed like the 28right thing to do. 29 30This package requires a post-V7 version of m4; if you are running the 314.2bsd, SysV.2, or 7th Edition version, I suggest finding a friend with 32a newer version. You can m4-expand on their system, then run locally. 33SunOS's /usr/5bin/m4 or BSD-Net/2's m4 both work. GNU m4 version 1.1 34also works. Unfortunately, I'm told that the M4 on BSDI 1.0 doesn't 35work -- you'll have to use a Net/2 or GNU version. 36 37IF YOU DON'T HAVE A BERKELEY MAKE, don't despair! Just run 38"m4 foo.mc > foo.cf" -- that should be all you need. There is also 39a fairly crude (but functional) Makefile.dist that works on the 40old version of make. 41 42To get started, you may want to look at tcpproto.mc (for TCP-only 43sites), uucpproto.mc (for UUCP-only sites), and clientproto.mc (for 44clusters of clients using a single mail host). Others are versions 45that we use at Berkeley, although not all are in current use. For 46example, ucbarpa has gone away, but I've left ucbarpa.mc in because 47it demonstrates some interesting techniques. 48 49I'm not pretending that this README describes everything that these 50configuration files can do; clever people can probably tweak them 51to great effect. But it should get you started. 52 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 60 61+--------------------------+ 62| INTRODUCTION AND EXAMPLE | 63+--------------------------+ 64 65Configuration files are contained in the subdirectory "cf", with a 66suffix ".mc". They must be run through "m4" to produce a ".cf" file. 67 68Let'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 89The divert(-1) will delete the crud in the resulting output file. 90The copyright notice is what your lawyers require. Our lawyers require 91the one that I've included in my files. A copyleft is a copyright by 92another name. 93 94The next line MUST be 95 96 include(`../m4/cf.m4') 97 98This will pull in the M4 macros you will need to make sense of 99everything else. As the saying goes, don't think about it, just 100do it. If you don't do it, don't bother reading the rest of this 101file. 102 103 VERSIONID(`<SCCS or RCS version id>') 104 105VERSIONID is a macro that stuffs the version information into the 106resulting file. We use SCCS; you could use RCS, something else, or 107omit it completely. This is not the same as the version id included 108in SMTP greeting messages -- this is defined in m4/version.m4. 109 110 DOMAIN(cs.exposed) 111 112This example exposes the host inside of the CS subdomain -- that is, 113it doesn't try to hide the name of the workstation to the outside 114world. Changing this to DOMAIN(cs.hidden) would have made outgoing 115messages refer to "<username>@CS.Berkeley.EDU" instead of using the 116local hostname. Internally this is effected by using 117"MASQUERADE_AS(CS.Berkeley.EDU)". 118 119 MAILER(smtp) 120 121These describe the mailers used at the default CS site site. The 122local mailer is always included automatically. 123 124 125+--------+ 126| OSTYPE | 127+--------+ 128 129Note that cf/cs-exposed.mc omits an OSTYPE macro -- this assumes 130default Computer Science Division environment. There are several 131explicit environments available: bsd4.3, bsd4.4, hpux, irix, osf1, 132riscos4.5, sunos3.5, sunos4.1, and ultrix4.1. These change things 133like the location of the alias file and queue directory. Some of 134these files are identical to one another. 135 136Operating system definitions are easy to write. They may define 137the following variables (everything defaults, so an ostype file 138may be empty). 139 140ALIAS_FILE [/etc/aliases] The location of the text version 141 of the alias file(s). It can be a comma-separated 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"). 147HELP_FILE [/usr/lib/sendmail.hf] The name of the file 148 containing information printed in response to 149 the SMTP HELP command. 150QUEUE_DIR [/var/spool/mqueue] The directory containing 151 queue files. 152STATUS_FILE [/etc/sendmail.st] The file containing status 153 information. 154LOCAL_MAILER_PATH [/bin/mail] The program used to deliver local mail. 155LOCAL_MAILER_FLAGS [rmn] The flags used by the local mailer. The 156 flags lsDFM are always included. 157LOCAL_MAILER_ARGS [mail -d $u] The arguments passed to deliver local 158 mail. 159LOCAL_SHELL_PATH [/bin/sh] The shell used to deliver piped email. 160LOCAL_SHELL_FLAGS [eu] The flags used by the shell mailer. The 161 flags lsDFM are always included. 162LOCAL_SHELL_ARGS [sh -c $u] The arguments passed to deliver "prog" 163 mail. 164USENET_MAILER_PATH [/usr/lib/news/inews] The name of the program 165 used to submit news. 166USENET_MAILER_FLAGS [rlsDFMmn] The mailer flags for the usenet mailer. 167USENET_MAILER_ARGS [-m -h -n] The command line arguments for the 168 usenet mailer. 169USENET_MAILER_MAX [100000] The maximum size of messages that will 170 be accepted by the usenet mailer. 171SMTP_MAILER_FLAGS [undefined] Flags added to SMTP mailer. Default 172 flags are `mDFMUX' (and `a' for esmtp mailer). 173SMTP_MAILER_MAX [undefined] The maximum size of messages that will 174 be transported using the smtp or esmtp mailers. 175UUCP_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). 178UUCP_MAILER_ARGS [uux - -r -z -a$f -gC $h!rmail ($u)] The arguments 179 passed to the UUCP mailer. 180UUCP_MAX_SIZE [100000] The maximum size message accepted for 181 transmission by the UUCP mailers. 182FAX_MAILER_PATH [/usr/local/lib/fax/mailfax] The program used to 183 submit FAX messages. 184FAX_MAILER_MAX [100000] The maximum size message accepted for 185 transmission by FAX. 186 187+---------+ 188| DOMAINS | 189+---------+ 190 191You will probably want to collect domain-dependent defines into one 192file, referenced by the DOMAIN macro. For example, our Berkeley 193domain file includes definitions for several internal distinguished 194hosts: 195 196UUCP_RELAY The host that will forward UUCP-addressed email. 197 If not defined, all UUCP sites must be directly 198 connected. 199BITNET_RELAY The host that will forward BITNET-addressed email. 200 If not defined, the .BITNET pseudo-domain won't work. 201LOCAL_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 207 methods. 208 209Each of these can be either ``mailer:hostname'' (in which case the 210mailer is the internal mailer name, such as ``suucp'' and the hostname 211is the name of the host as appropriate for that mailer) or just a 212``hostname'', in which case a default mailer type (usually ``relay'', 213a variant on SMTP) is used. WARNING: if you have a wildcard MX 214record matching your domain, you probably want to define these to 215have a trailing dot so that you won't get the mail diverted back 216to yourself. 217 218The domain file can also be used to define a domain name, if needed 219(using "DD<domain>") and set certain site-wide features. If all hosts 220at your site masquerade behind one email name, you could also use 221MASQUERADE_AS here. 222 223You do not have to define a domain -- in particular, if you are a 224single machine sitting off somewhere, it is probably more work than 225it's worth. This is just a mechanism for combining "domain dependent 226knowledge" into one place. 227 228+---------+ 229| MAILERS | 230+---------+ 231 232There are fewer mailers supported in this version than the previous 233version, owing mostly to a simpler world. 234 235local The local and prog mailers. You will almost always 236 need these; the only exception is if you relay ALL 237 your mail to another site. This mailer is included 238 automatically. 239 240smtp 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 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. 248 249uucp The Unix-to-Unix Copy Program mailer. Actually, this 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 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 260 this is a function of what version of rmail runs on 261 the receiving end, and hence may be out of your control. 262 See the section below describing UUCP mailers in more 263 detail. 264 265usenet 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 271fax Facsimile transmission. This is experimental and based 272 on Sam Leffler's FlexFAX software. For more information, 273 see below. 274 275pop Post Office Protocol. 276 277 278+----------+ 279| FEATURES | 280+----------+ 281 282Special features can be requested using the "FEATURE" macro. For 283example, the .mc line: 284 285 FEATURE(use_cw_file) 286 287tells sendmail that you want to have it read an /etc/sendmail.cw 288file to get values for class $=w. The FEATURE may contain a single 289optional parameter -- for example: 290 291 FEATURE(mailertable, dbm /usr/lib/mailertable) 292 293Available features are: 294 295use_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. 300 The actual filename can be overridden by redefining 301 confCW_FILE. 302 303redirect 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. 307 308nouucp Don't do anything special with UUCP addresses at all. 309 310nocanonify 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 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. 317 318notsticky 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. 323 324mailertable 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: 328 hash -o /etc/mailertable 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: 333 mailer:domain 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. 337 338domaintable Include a "domain table" which can be used to provide 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: 345 hash -o /etc/domaintable 346 The key in this table is the domain name; the value is 347 the new (fully qualified) domain. Anything in the 348 domaintable is reflected into headers; that is, this 349 is done in ruleset 3. 350 351bitdomain Look up bitnet hosts in a table to try to turn them into 352 internet addresses. The table can be built using the 353 bitdomain program contributed by John Gardiner Myers. 354 The argument of the FEATURE may be the key definition; if 355 none is specified, the definition used is: 356 hash -o /etc/bitdomain.db 357 Keys are the bitnet hostname; values are the corresponding 358 internet hostname. 359 360uucpdomain Similar feature for UUCP hosts. The default map definition 361 is: 362 hash -o /etc/uudomain.db 363 At the moment there is no automagic tool to build this 364 database. 365 366always_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. 370 371allmasquerade 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. 383 384nodns 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. 387 388nullclient This is a special case -- it creates a stripped down 389 configuration file containing nothing but support for 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. 400 401 402+-------+ 403| HACKS | 404+-------+ 405 406Some things just can't be called features. To make this clear, 407they go in the hack subdirectory and are referenced using the HACK 408macro. These will tend to be site-dependent. The release 409includes the Berkeley-dependent "cssubdomain" hack (that makes 410sendmail accept local names in either Berkeley.EDU or CS.Berkeley.EDU; 411this is intended as a short-term aid while we move hosts into 412subdomains. 413 414 415+--------------------+ 416| SITE CONFIGURATION | 417+--------------------+ 418 419Complex sites will need more local configuration information, such as 420lists of UUCP hosts they speak with directly. This can get a bit more 421tricky. For an example of a "complex" site, see cf/ucbvax.mc. 422 423If your host is known by several different names, you need to augment 424the $=w class. This is a list of names by which you are known, and 425anything sent to an address using a host name in this list will be 426treated as local mail. You can do this in two ways: either create 427the file /etc/sendmail.cw containing a list of your aliases (one per 428line), and use ``FEATURE(use_cw_file)'' in the .mc file, or add the 429line: 430 431 Cw alias.host.name 432 433at the end of that file. See the ``vangogh.mc'' file for an example. 434Be sure you use the fully-qualified name of the host, rather than a 435short name. 436 437The SITECONFIG macro allows you to indirectly reference site-dependent 438configuration information stored in the siteconfig subdirectory. For 439example, the line 440 441 SITECONFIG(uucp.ucbvax, ucbvax, U) 442 443reads the file uucp.ucbvax for local connection information. The 444second parameter is the local name (in this case just "ucbvax" since 445it is locally connected, and hence a UUCP hostname). The third 446parameter is the name of both a macro to store the local name (in 447this case, $U) and the name of the class (e.g., $=U) in which to store 448the host information read from the file. Another SITECONFIG line reads 449 450 SITECONFIG(uucp.ucbarpa, ucbarpa.Berkeley.EDU, W) 451 452This says that the file uucp.ucbarpa contains the list of UUCP sites 453connected to ucbarpa.Berkeley.EDU. The $=W class will be used to 454store this list, and $W is defined to be ucbarpa.Berkeley.EDU, that 455is, the name of the relay to which the hosts listed in uucp.ucbarpa 456are connected. [The machine ucbarpa is gone now, but I've left 457this out-of-date configuration file around to demonstrate how you 458might do this.] 459 460Note that the case of SITECONFIG with a third parameter of ``U'' is 461special; the second parameter is assumed to be the UUCP name of the 462local site, rather than the name of a remote site, and the UUCP name 463is entered into $=w (the list of local hostnames) as $U.UUCP. 464 465The siteconfig file (e.g., siteconfig/uucp.ucbvax.m4) contains nothing 466more than a sequence of SITE macros describing connectivity. For 467example: 468 469 SITE(cnmat) 470 SITE(sgi olympus) 471 472The second example demonstrates that you can use two names on the 473same line; these are usually aliases for the same host (or are at 474least in the same company). 475 476 477+--------------------+ 478| USING UUCP MAILERS | 479+--------------------+ 480 481It's hard to get UUCP mailers right because of the extremely ad hoc 482nature of UUCP addressing. These config files are really designed 483for domain-based addressing, even for UUCP sites. 484 485There are four UUCP mailers available. The choice of which one to 486use is partly a matter of local preferences and what is running at 487the other end of your UUCP connection. Unlike good protocols that 488define what will go over the wire, UUCP uses the policy that you 489should do what is right for the other end; if they change, you have 490to change. This makes it hard to do the right thing, and discourages 491people from updating their software. In general, if you can avoid 492UUCP, please do. 493 494The major choice is whether to go for a domainized scheme or a 495non-domainized scheme. This depends entirely on what the other 496end will recognize. If at all possible, you should encourage the 497other end to go to a domain-based system -- non-domainized addresses 498don't work entirely properly. 499 500The 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. 518 Basically, it uses the SMTP mailer rewriting rules. This mailer 519 is only included if MAILER(smtp) is also specified. 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 533 "some.dom.ain!wolf"). This is also included only if MAILER(smtp) 534 is also specified. 535 536Examples: 537 538We are on host grasp.insa-lyon.fr (UUCP host name "grasp"). The 539following summarizes the sender rewriting for various mailers. 540 541Mailer sender rewriting in the envelope 542------ ------ ------------------------- 543uucp-{old,new} wolf grasp!wolf 544uucp-dom wolf wolf@grasp.insa-lyon.fr 545uucp-uudom wolf grasp.insa-lyon.fr!wolf 546 547uucp-{old,new} wolf@fr.net grasp!fr.net!wolf 548uucp-dom wolf@fr.net wolf@fr.net 549uucp-uudom wolf@fr.net fr.net!wolf 550 551uucp-{old,new} somehost!wolf grasp!somehost!wolf 552uucp-dom somehost!wolf somehost!wolf@grasp.insa-lyon.fr 553uucp-uudom somehost!wolf grasp.insa-lyon.fr!somehost!wolf 554 555If you are using one of the domainized UUCP mailers, you really want 556to convert all UUCP addresses to domain format -- otherwise, it will 557do it for you (and probably not the way you expected). For example, 558if you have the address foo!bar!baz (and you are not sending to foo), 559the heuristics will add the @uucp.relay.name or @local.host.name to 560this address. However, if you map foo to foo.host.name first, it 561will not add the local hostname. You can do this using the uucpdomain 562feature. 563 564 565+-------------------+ 566| TWEAKING RULESETS | 567+-------------------+ 568 569For more complex configurations, you can define special rules. 570The macro LOCAL_RULE_3 introduces rules that are used in canonicalizing 571the names. Any modifications made here are reflected in the header. 572 573A common use is to convert old UUCP addreses to SMTP addresses using 574the UUCPSMTP macro. For example: 575 576 LOCAL_RULE_3 577 UUCPSMTP(decvax, decvax.dec.com) 578 UUCPSMTP(research, research.att.com) 579 580will cause addresses of the form "decvax!user" and "research!user" 581to be converted to "user@decvax.dec.com" and "user@research.att.com" 582respectively. 583 584This could also be used to look up hosts in a database map: 585 586 LOCAL_RULE_3 587 R$* < @ $+ > $* $: $1 < @ $(hostmap $2 $) > $3 588 589This map would be defined in the LOCAL_CONFIG portion, as shown below. 590 591Similarly, LOCAL_RULE_0 can be used to introduce new parsing rules. 592For example, new rules are needed to parse hostnames that you accept 593via MX records. For example, you might have: 594 595 LOCAL_RULE_0 596 R$+ <@ host.dom.ain.> $#uucp $@ cnmat $: $1 < @ host.dom.ain.> 597 598You would use this if you had installed an MX record for cnmat.Berkeley.EDU 599pointing at this host; this rule catches the message and forwards it on 600using UUCP. 601 602You can also tweak rulesets 1 and 2 using LOCAL_RULE_1 and LOCAL_RULE_2. 603These rulesets are normally empty. 604 605A similar macro is LOCAL_CONFIG. This introduces lines added after the 606boilerplate option setting but before rulesets, and can be used to 607declare local database maps or whatever. For example: 608 609 LOCAL_CONFIG 610 Khostmap hash /etc/hostmap.db 611 Kyplocal nis -m hosts.byname 612 613 614+---------------------------+ 615| MASQUERADING AND RELAYING | 616+---------------------------+ 617 618You can have your host masquerade as another using 619 620 MASQUERADE_AS(host.domain) 621 622This causes outgoing SMTP mail to be labeled as coming from the 623indicated domain, rather than $j. One normally masquerades as one 624of one's own subdomains (for example, it's unlikely that I would 625choose to masquerade as an MIT site). 626 627The masquerade name is not normally canonified, so it is important 628that it be your One True Name, that is, fully qualified and not a 629CNAME. 630 631there are always users that need to be "exposed" -- that is, their 632internal site name should be displayed instead of the masquerade name. 633Root is an example. You can add users to this list using 634 635 EXPOSED_USER(usernames) 636 637This adds users to class E; you could also use something like 638 639 FE/etc/sendmail.cE 640 641You can also arrange to relay all unqualified names (that is, names 642without @host) to a relay host. For example, if you have a central 643email server, you might relay to that host so that users don't have 644to have .forward files or aliases. You can do this using 645 646 define(`LOCAL_RELAY', mailer:hostname) 647 648The ``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 650because of local aliases. A common example is root, which may be 651locally aliased. You can add entries to this list using 652 653 LOCAL_USER(usernames) 654 655This adds users to class L; you could also use something like 656 657 FL/etc/sendmail.cL 658 659If you want all incoming mail sent to a centralized hub, as for a 660shared /var/spool/mail scheme, use 661 662 define(`MAIL_HUB', mailer:hostname) 663 664Again, ``mailer:'' defaults to "smtp". If you define both LOCAL_RELAY 665and MAIL_HUB, unqualified names will be sent to the LOCAL_RELAY and 666other local names will be sent to MAIL_HUB. Names in $=L will be 667delivered locally, so you MUST have aliases or .forward files for them. 668 669For example, if are on machine mastodon.CS.Berkeley.EDU, the following 670combinations of settings will have the indicated effects: 671 672email sent to.... eric eric@mastodon.CS.Berkeley.EDU 673 674LOCAL_RELAY set to mail.CS.Berkeley.EDU (delivered locally) 675mail.CS.Berkeley.EDU 676 677MAIL_HUB set to mammoth.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU 678mammoth.CS.Berkeley.EDU 679 680Both LOCAL_RELAY and mail.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU 681MAIL_HUB set as above 682 683If you want all outgoing mail to go to a central relay site, define 684SMART_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 691However, beware that other relays (e.g., UUCP_RELAY, BITNET_RELAY, and 692FAX_RELAY) take precedence over SMART_HOST, so if you really want 693absolutely everything to go to a single central site you will need to 694unset all the other relays -- or better yet, find or build a minimal 695config file that does this. 696 697 698+-------------------------------+ 699| NON-SMTP BASED CONFIGURATIONS | 700+-------------------------------+ 701 702These configuration files are designed primarily for use by SMTP-based 703sites. I don't pretend that they are well tuned for UUCP-only or 704UUCP-primarily nodes (the latter is defined as a small local net 705connected to the rest of the world via UUCP). However, there is one 706hook to handle some special cases. 707 708You can define a ``smart host'' that understands a richer address syntax 709using: 710 711 define(`SMART_HOST', mailer:hostname) 712 713In this case, the ``mailer:'' defaults to "relay". Any messages that 714can't be handled using the usual UUCP rules are passed to this host. 715 716If you are on a local SMTP-based net that connects to the outside 717world via UUCP, you can use LOCAL_NET_CONFIG to add appropriate rules. 718For example: 719 720 define(`SMART_HOST', suucp:uunet) 721 LOCAL_NET_CONFIG 722 R$* < @ $* .$m. > $* $#smtp $@ $2.$m. $: $1 < @ $2.$m. > $3 723 724This will cause all names that end in your domain name ($m) via 725SMTP; anything else will be sent via suucp (smart UUCP) to uunet. 726If you have FEATURE(nocanonify), you may need to omit the dots after 727the $m. If you are running a local DNS inside your domain which is 728not otherwise connected to the outside world, you probably want to 729use: 730 731 define(`SMART_HOST', smtp:fire.wall.com) 732 LOCAL_NET_CONFIG 733 R$* < @ $* . > $* $#smtp $@ $2. $: $1 < @ $2. > $3 734 735That is, send directly only to things you found in your DNS lookup; 736anything else goes through SMART_HOST. 737 738If you are not running DNS at all, it is important to use 739FEATURE(nodns) to avoid having sendmail queue everything waiting 740for the name server to come up. 741 742 743+-----------+ 744| WHO AM I? | 745+-----------+ 746 747Normally, the $j macro is automatically defined to be your fully 748qualified domain name (FQDN). Sendmail does this by getting your 749host name using gethostname and then calling gethostbyname on the 750result. For example, in some environments gethostname returns 751only the root of the host name (such as "foo"); gethostbyname is 752supposed to return the FQDN ("foo.bar.com"). In some (fairly rare) 753cases, gethostbyname may fail to return the FQDN. In this case 754you MUST define confDOMAIN_NAME to be your fully qualified domain 755name. This is usually done using: 756 757 Dmbar.com 758 define(`confDOMAIN_NAME', `$w.$m')dnl 759 760 761+--------------------+ 762| USING MAILERTABLES | 763+--------------------+ 764 765To use FEATURE(mailertable), you will have to create an external 766database containing the routing information for various domains. 767For 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 773This should normally be stored in /etc/mailertable. The actual 774database version of the mailertable is built using: 775 776 makemap hash /etc/mailertable.db < /etc/mailertable 777 778The semantics are simple. Any LHS entry that does not begin with 779a dot matches the full host name indicated. LHS entries beginning 780with a dot match anything ending with that domain name -- that is, 781they can be thought of as having a leading "*" wildcard. Matching 782is done in order of most-to-least qualified -- for example, even 783though ".my.domain" is listed first in the above example, an entry 784of "uuhost1.my.domain" will match the second entry since it is 785more explicit. 786 787The RHS should always be a "mailer:host" pair. The mailer is the 788configuration name of a mailer (that is, an `M' line in the 789sendmail.cf file). The "host" will be the hostname passed to 790that mailer. In domain-based matches (that is, those with leading 791dots) the "%1" may be used to interpolate the wildcarded part of 792the host name. For example, the first line above sends everything 793addressed to "anything.my.domain" to that same host name, but using 794the (presumably experimental) xnet mailer. 795 796 797+--------------------------------+ 798| USING USERDB TO MAP FULL NAMES | 799+--------------------------------+ 800 801The user database was not originally intended for mapping full names 802to login names (e.g., Eric.Allman => eric), but some people are using 803it that way. (I would recommend that you set up aliases for this 804purpose instead -- since you can specify multiple alias files, this 805is fairly easy.) The intent was to locate the default maildrop at 806a site, but allow you to override this by sending to a specific host. 807 808If you decide to set up the user database in this fashion, it is 809imperative that you also specify FEATURE(notsticky) -- otherwise, 810e-mail sent to Full.Name@local.host.name will be rejected. 811 812To build the internal form of the user databae, use: 813 814 makemap btree /usr/data/base.db < /usr/data/base.txt 815 816 817+--------------------------------+ 818| MISCELLANEOUS SPECIAL FEATURES | 819+--------------------------------+ 820 821DOTTED_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 848+------------------+ 849| FlexFAX SOFTWARE | 850+------------------+ 851 852Sam Leffler's FlexFAX software is still in beta test -- but he expects a 853public version out "later this week" [as of 3/1/93]. The following 854blurb is direct from Sam: 855 856 $Header: /usr/people/sam/fax/RCS/HOWTO,v 1.14 93/05/24 11:42:16 sam Exp $ 857 858 How To Obtain This Software (in case all you get is this file) 859 -------------------------------------------------------------- 860 The source code is available for public ftp on 861 sgi.com sgi/fax/v2.1.src.tar.Z 862 (192.48.153.1) 863 864 You can also obtain inst'able images for Silicon Graphics machines from 865 sgi.com sgi/fax/v2.1.inst.tar 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 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 897 service, send a message to "ftpmail@gatekeeper.dec.com" whose body 898 consists of the single line "help". 899 900 901 Obtaining the Software Within Silicon Graphics 902 ---------------------------------------------- 903 Internal to Silicon Graphics there are inst'able images on the host 904 flake.asd in the directory /usr/dist. Thus you can do something like: 905 906 % inst -f flake.asd.sgi.com:/usr/dist/flexfax 907 908 to install the latest version of the software on your machine. 909 910 911 What to do Once You've Retrieved Stuff 912 -------------------------------------- 913 The external distributions come in a compressed or uncompressed tar 914 file. To extract the source distribution: 915 916 % zcat v2.1.src.tar.Z | tar xf - 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 922 % cd dist; tar xf ../v2.1.inst.tar; cd .. 923 % inst -f dist/flexfax 924 ... 925 inst> go 926 927 (Note, the dist subdirectory is because some versions of inst fail if 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: 931 932 % inst -f flexfax 933 ... 934 inst> install flexfax.server.* 935 inst> go 936 937 The SGI binaries were built for Version 4.0.5H of the IRIX operating 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 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. 952 953 954 FlexFAX Mail List 955 ----------------- 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 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. 965 966 Submissions (including bug reports) should be directed to: 967 968 flexfax@sgi.com 969 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 974 975+--------------------------------+ 976| TWEAKING CONFIGURATION OPTIONS | 977+--------------------------------+ 978 979There are a large number of configuration options that don't normally 980need to be changed. However, if you feel you need to tweak them, you 981can define the following M4 variables. This list is shown in four 982columns: the name you define, the default value for that definition, 983the option or macro that is affected (either Ox for an option or Dx 984for a macro), and a brief description. Greater detail of the semantics 985can be found in the Installation and Operations Guide. 986 987Some options are likely to be deprecated in future versions -- that is, 988the option is only included to provide back-compatibility. These are 989marked with "*". 990 991Remember that these options are M4 variables, and hence may need to 992be quoted. In particular, arguments with commas will usually have to 993be ``double quoted, like this phrase'' to avoid having the comma 994confuse things. This is common for alias file definitions and for 995the read timeout. 996 997M4 Variable Name Default Mac/Opt Description 998================ ======= ======= =========== 999confMAILER_NAME MAILER-DAEMON Dn The sender name used for 1000 internally generated 1001 outgoing messages. 1002confFROM_LINE From $g $d Dl The From_ line used when 1003 sending to files or programs. 1004confFROM_HEADER $?x$x <$g>$|$g$. The format of an internally 1005 Dq generated From: address. 1006confOPERATORS .:%@!^/[] Do Address operator characters. 1007confSMTP_LOGIN_MSG $j Sendmail $v/$Z ready at $b 1008 De The initial (spontaneous) 1009 SMTP greeting message. 1010confRECEIVED_HEADER $?sfrom $s $.$?_($?s$|from $.$_) $.by $j ($v/$Z)$?r with $r$. id $i$?u for $u$.; $b 1011 HReceived 1012 The format of the Received: 1013 header in messages passed 1014 through this host. It is 1015 unwise to try to change this. 1016confSEVEN_BIT_INPUT False O7 Force input to seven bits? 1017confEIGHT_BIT_HANDLING pass8 O8 8-bit data handling 1018confALIAS_WAIT 10 Oa Wait (in minutes) for alias 1019 file rebuild. 1020confMIN_FREE_BLOCKS 4 Ob Minimum number of free blocks 1021 on queue filesystem to accept 1022 SMTP mail. 1023confBLANK_SUB . OB Blank (space) substitution 1024 character. 1025confCON_EXPENSIVE False Oc Avoid connecting immediately 1026 to mailers marked expensive? 1027confCHECKPOINT_INTERVAL 10 OC Checkpoint queue files 1028 every N recipients. 1029confDELIVERY_MODE background Od Default delivery mode. 1030confAUTO_REBUILD False OD Automatically rebuild 1031 alias file if needed. 1032confERROR_MODE (undefined) Oe Error message mode. 1033confERROR_MESSAGE (undefined) OE Error message header/file. 1034confSAVE_FROM_LINES False Of Save extra leading 1035 From_ lines. 1036confTEMP_FILE_MODE 0600 OF Temporary file mode. 1037confDEF_GROUP_ID 1 Og Default group id. 1038confMATCH_GECOS False OG Match GECOS field. 1039confMAX_HOP 17 Oh Maximum hop count. 1040confIGNORE_DOTS False Oi * Ignore dot as terminator 1041 for incoming messages? 1042confBIND_OPTS (empty) OI Default options for BIND. 1043confMIME_FORMAT_ERRORS True Oj * Send error messages as MIME- 1044 encapsulated messages per 1045 RFC 1344. 1046confFORWARD_PATH (undefined) OJ The colon-separated list of 1047 places to search for .forward 1048 files. 1049confMCI_CACHE_SIZE 2 Ok Size of open connection cache. 1050confMCI_CACHE_TIMEOUT 5m OK Open connection cache timeout. 1051confUSE_ERRORS_TO False Ol * Use the Errors-To: header to 1052 deliver error messages. This 1053 should not be necessary because 1054 of general acceptance of the 1055 envelope/header distinction. 1056confLOG_LEVEL 9 OL Log level. 1057confME_TOO False Om Include sender in group 1058 expansions. 1059confCHECK_ALIASES True On Check RHS of aliases when 1060 running newaliases. 1061confOLD_STYLE_HEADERS True Oo * Assume that headers without 1062 special chars are old style. 1063confDAEMON_OPTIONS (undefined) OO SMTP daemon options. 1064confPRIVACY_FLAGS authwarnings Op Privacy flags. 1065confCOPY_ERRORS_TO (undefined) OP Address for additional copies 1066 of all error messages. 1067confQUEUE_FACTOR (undefined) Oq Slope of queue-only function 1068confREAD_TIMEOUT (undefined) Or SMTP read timeouts. 1069confDONT_PRUNE_ROUTES False OR Don't prune down route-addr 1070 syntax addresses to the 1071 minimum possible. 1072confSAFE_QUEUE True Os * Commit all messages to disk 1073 before forking. 1074confMESSAGE_TIMEOUT 5d/4h OT Timeout for messages before 1075 sending error/warning message. 1076confTIME_ZONE USE_SYSTEM Ot Time zone info -- can be 1077 USE_SYSTEM to use the system's 1078 idea, USE_TZ to use the user's 1079 TZ envariable, or something 1080 else to force that value. 1081confDEF_USER_ID 1 Ou Default user id. 1082confUSERDB_SPEC (undefined) OU User database specification. 1083confFALLBACK_MX (undefined) OV Fallback MX host. 1084confTRY_NULL_MX_LIST False Ow If we are the best MX for a 1085 host and haven't made other 1086 arrangements, try connecting 1087 to the host directly; normally 1088 this would be a config error. 1089confQUEUE_LA 8 Ox Load average at which queue-only 1090 function kicks in. 1091confREFUSE_LA 12 OX Load average at which incoming 1092 SMTP connections are refused. 1093confWORK_RECIPIENT_FACTOR 1094 (undefined) Oy Cost of each recipient. 1095confSEPARATE_PROC False OY Run all deliveries in a 1096 separate process. 1097confWORK_CLASS_FACTOR (undefined) Oz Priority multiplier for class. 1098confWORK_TIME_FACTOR (undefined) OZ Cost of each delivery attempt. 1099confCW_FILE /etc/sendmail.cw Name of file used to get the 1100 Fw local additions to the $=w 1101 class. 1102confSMTP_MAILER smtp - The mailer name used when 1103 SMTP connectivity is required. 1104 Either "smtp" or "esmtp". 1105confLOCAL_MAILER local - The mailer name used when 1106 local connectivity is required. 1107 Almost always "local". 1108confRELAY_MAILER relay - The default mailer name used 1109 for relaying any mail (e.g., 1110 to a BITNET_RELAY, a 1111 SMART_HOST, or whatever). 1112 This can reasonably be "suucp" 1113 if you are on a UUCP-connected 1114 site. 1115confDOMAIN_NAME (undefined) Dj If defined, sets $j. 1116 1117 1118+-----------+ 1119| HIERARCHY | 1120+-----------+ 1121 1122Within this directory are several subdirectories, to wit: 1123 1124m4 General support routines. These are typically 1125 very important and should not be changed without 1126 very careful consideration. 1127 1128cf The configuration files themselves. They have 1129 ".mc" suffixes, and must be run through m4 to 1130 become complete. The resulting output should 1131 have a ".cf" suffix. 1132 1133ostype Definitions describing a particular operating 1134 system type. These should always be referenced 1135 using the OSTYPE macro in the .mc file. Examples 1136 include "bsd4.3", "bsd4.4", "sunos3.5", and 1137 "sunos4.1". 1138 1139domain Definitions describing a particular domain, referenced 1140 using the DOMAIN macro in the .mc file. These are 1141 site dependent; for example, we contribute "cs.exposed.m4" 1142 and "cs.hidden.m4" which both describe hosts in the 1143 CS.Berkeley.EDU subdomain; the former displays the local 1144 hostname (e.g., mammoth.CS.Berkeley.EDU), whereas the 1145 latter does its best to hide the identity of the local 1146 workstation inside the CS subdomain. 1147 1148mailer Descriptions of mailers. These are referenced using 1149 the MAILER macro in the .mc file. 1150 1151sh Shell files used when building the .cf file from the 1152 .mc file in the cf subdirectory. 1153 1154feature These hold special orthogonal features that you might 1155 want to include. They should be referenced using 1156 the FEATURE macro. 1157 1158hack Local hacks. These can be referenced using the HACK 1159 macro. They shouldn't be of more than voyeuristic 1160 interest outside the .Berkeley.EDU domain, but who knows? 1161 We've all got our own peccadillos. 1162 1163siteconfig Site configuration -- e.g., tables of locally connected 1164 UUCP sites. 1165 1166 1167+------------------------+ 1168| ADMINISTRATIVE DETAILS | 1169+------------------------+ 1170 1171The following sections detail usage of certain internal parts of the 1172sendmail.cf file. Read them carefully if you are trying to modify 1173the current model. If you find the above descriptions adequate, these 1174should be {boring, confusing, tedious, ridiculous} (pick one or more). 1175 1176RULESETS (* means built in to sendmail) 1177 1178 0 * Parsing 1179 1 * Sender rewriting 1180 2 * Recipient rewriting 1181 3 * Canonicalization 1182 4 * Post cleanup 1183 5 * Local address rewrite (after aliasing) 1184 1x mailer rules (sender qualification) 1185 2x mailer rules (recipient qualification) 1186 3x mailer rules (sender header qualification) 1187 4x mailer rules (recipient header qualification) 1188 5x mailer subroutines (general) 1189 6x mailer subroutines (general) 1190 7x mailer subroutines (general) 1191 8x reserved 1192 90 Mailertable host stripping 1193 96 Bottom half of Ruleset 3 (ruleset 6 in old sendmail) 1194 97 Hook for recursive ruleset 0 call (ruleset 7 in old sendmail) 1195 98 Local part of ruleset 0 (ruleset 8 in old sendmail) 1196 1197 1198MAILERS 1199 1200 0 local, prog local and program mailers 1201 1 [e]smtp, relay SMTP channel 1202 2 uucp-* UNIX-to-UNIX Copy Program 1203 3 netnews Network News delivery 1204 4 fax Sam Leffler's FlexFAX software 1205 1206 1207MACROS 1208 1209 A 1210 B Bitnet Relay 1211 C 1212 D The local domain -- usually not needed 1213 E 1214 F FAX Relay 1215 G 1216 H mail Hub (for mail clusters) 1217 I 1218 J 1219 K 1220 L 1221 M Masquerade (who I claim to be) 1222 N 1223 O 1224 P 1225 Q 1226 R Relay (for unqualified names) 1227 S Smart Host 1228 T 1229 U my UUCP name (if I have a UUCP connection) 1230 V UUCP Relay (class V hosts) 1231 W UUCP Relay (class W hosts) 1232 X UUCP Relay (class X hosts) 1233 Y UUCP Relay (all other hosts) 1234 Z Version number 1235 1236 1237CLASSES 1238 1239 A 1240 B 1241 C 1242 D "dotted" users 1243 E addresses that should not seem to come from $M 1244 F hosts we forward for 1245 G 1246 H 1247 I 1248 J 1249 K 1250 L addresses that should not be forwarded to $R 1251 M 1252 N 1253 O operators that indicate network operations (cannot be in local names) 1254 P top level pseudo-domains: BITNET, FAX, UUCP, etc. 1255 Q 1256 R 1257 S 1258 T 1259 U locally connected UUCP hosts 1260 V UUCP hosts connected to relay $V 1261 W UUCP hosts connected to relay $W 1262 X UUCP hosts connected to relay $X 1263 Y locally connected smart UUCP hosts 1264 Z locally connected domain-ized UUCP hosts 1265 . the class containing only a dot 1266 1267 1268M4 DIVERSIONS 1269 1270 1 Local host detection and resolution 1271 2 Local Ruleset 3 additions 1272 3 Local Ruleset 0 additions 1273 4 UUCP Ruleset 0 additions 1274 5 locally interpreted names (overrides $R) 1275 6 local configuration (at top of file) 1276 7 mailer definitions 1277 8 1278 9 special local rulesets (1 and 2) 1279