1 2 3 NEW SENDMAIL CONFIGURATION FILES 4 5 Eric Allman <eric@CS.Berkeley.EDU> 6 7 @(#)README 6.12 (Berkeley) 03/06/93 8 9 10This document describes the sendmail configuration files being used 11at Berkeley. These use features in the new (R6) sendmail, and although 12there is an ``OLDSENDMAIL'' mode, they haven't really been tested on 13old versions of sendmail and cannot be expected to work well. 14 15These configuration files are probably not as general as previous 16versions, and don't handle as many of the wierd cases automagically. 17I was able to simplify by them for two reasons. First, the network 18has become more consistent -- for example, at this point, everyone 19on the internet is supposed to be running a name server, so hacks to 20handle NIC-registered hosts can go away. Second, I assumed that a 21subdomain would be running SMTP internally -- UUCP is presumed to be 22a long-haul protocol. I realize that this is not universal, but it 23does describe the vast majority of sites with which I am familiar, 24including those outside the US. 25 26Of course, the downside of this is that if you do live in a wierd 27world, things are going to get wierder for you. I'm sorry about that, 28but at the time we at Berkeley had a problem, and it seemed like the 29right thing to do. 30 31This package requires a post-V7 version of m4; if you are running the 324.2bsd, SysV.2, or 7th Edition version, I suggest finding a friend with 33a newer version. You can m4-expand on their system, then run locally. 34SunOS's /usr/5bin/m4 or BSD-Net/2's m4 both work. GNU m4 (which is a 35language unto itself) also works, but I don't intend to work so hard 36to keep this up in the future. [Note to GNU folks: the construct 37"define(`FOO')" should work without my having to add a null value.] 38 39IF YOU DON'T HAVE A BERKELEY MAKE, don't despair! Just run 40"m4 foo.mc > foo.cf" -- that should be all you need. 41 42To get started, you may want to look at tcpproto.mc (for TCP-only 43sites) and uucpproto.m4 (for UUCP-only sites). Others are versions 44that we use at Berkeley, although not all are in current use. For 45example, ucbarpa has gone away, but I've left ucbarpa.mc in because 46it demonstrates some interesting techniques. 47 48I'm not pretending that this README describes everything that these 49configuration files can do; clever people can probably tweak them 50to great effect. But it should get you started. 51 52 53+--------------------------+ 54| INTRODUCTION AND EXAMPLE | 55+--------------------------+ 56 57Configuration files are contained in the subdirectory "cf", with a 58suffix ".mc". They must be run through "m4" to produce a ".cf" file. 59 60Let's examine a typical .mc file (cf/cs-exposed.mc): 61 62 divert(-1) 63 # 64 # Copyright (c) 1983 Eric P. Allman 65 # Copyright (c) 1988 The Regents of the University of California. 66 # All rights reserved. 67 # 68 # Redistribution and use in source and binary forms are permitted 69 # provided that the above copyright notice and this paragraph are 70 # duplicated in all such forms and that any documentation, 71 # advertising materials, and other materials related to such 72 # distribution and use acknowledge that the software was developed 73 # by the University of California, Berkeley. The name of the 74 # University may not be used to endorse or promote products derived 75 # from this software without specific prior written permission. 76 # THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR 77 # IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED 78 # WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. 79 # 80 81The divert(-1) will delete the crud in the resulting output file. 82The copyright notice is what your lawyers require. Our lawyers require 83the one that I've included in my files. A copyleft is a copyright by 84another name. 85 86The next line MUST be 87 88 include(`../m4/cf.m4') 89 90This will pull in the M4 macros you will need to make sense of 91everything else. As the saying goes, don't think about it, just 92do it. If you don't do it, don't bother reading the rest of this 93file. 94 95 VERSIONID(`<SCCS or RCS version id>') 96 97VERSIONID is a macro that stuffs the version information into the 98resulting file. We use SCCS; you could use RCS, something else, or 99omit it completely. This is not the same as the version id included 100in SMTP greeting messages -- this is defined in m4/version.m4. 101 102 DOMAIN(cs.exposed) 103 104This example exposes the host inside of the CS subdomain -- that is, 105it doesn't try to hide the name of the workstation to the outside 106world. Changing this to DOMAIN(cs.hidden) would have made outgoing 107messages refer to "<username>@CS.Berkeley.EDU" instead of using the 108local hostname. Internaly this is effected by using 109"MASQUERADE_AS(CS.Berkeley.EDU)". 110 111 MAILER(smtp) 112 113These describe the mailers used at the default CS site site. The 114local mailer is always included automatically. 115 116 117+--------+ 118| OSTYPE | 119+--------+ 120 121Note that cf/cs-exposed.mc omits an OSTYPE macro -- this assumes 122default Computer Science Division environment. There are several 123explicit environments available: bsd4.3, bsd4.4, hpux, irix, osf1, 124riscos4.5, sunos3.5, sunos4.1, and ultrix4.1. These change things 125like the location of the alias file and queue directory. Some of 126these files are identical to one another. 127 128Operating system definitions are easy to write. They may define 129the following variables (everything defaults, so an ostype file 130may be empty). 131 132ALIAS_FILE [/etc/aliases] The location of the text version 133 of the alias file. 134HELP_FILE [/usr/lib/sendmail.hf] The name of the file 135 containing information printed in response to 136 the SMTP HELP command. 137QUEUE_DIR [/var/spool/mqueue] The directory containing 138 queue files. 139STATUS_FILE [/etc/sendmail.st] The file containing status 140 information. 141LOCAL_MAILER_PATH [/bin/mail] The program used to deliver local mail. 142LOCAL_MAILER_FLAGS [rn] The flags used by the local mailer. The 143 flags lsDFMm are always included. 144LOCAL_SHELL_PATH [/bin/sh] The shell used to deliver piped email. 145USENET_MAILER_PATH [/usr/lib/news/inews] The name of the program 146 used to submit news. 147USENET_MAILER_FLAGS [rlsDFMmn] The mailer flags for the usenet mailer. 148USENET_MAILER_ARGS [-m -h -n] The command line arguments for the 149 usenet mailer. 150HOSTMAP_SPEC [dbm -o /etc/hostmap] The value for the builtin 151 hostmap key definition. You can redefine this 152 to change the class, flags, and filename of 153 the hostmap. The default flag (-o) makes this 154 map optional. 155 156In addition, the following boolean flags may be defined -- the value 157is ignored. 158 159NEED_DOMAIN If set, the $j macro is defined as $w.$D. 160 If not set, $j is defined as $w. If this is 161 set, the domain must be defined using the line 162 DD<domainname> (probably in the domain file, 163 but possibly in the .mc file). You will only 164 need this if you define your system hostname 165 without a domain (type "hostname" -- if it 166 has no dots in the output, you qualify) AND 167 if you are not running the nameserver AND if 168 the first (canonical) name in /etc/hosts for 169 your machine has no domain -- OR if you are 170 running Ultrix or OSF/1 sendmail. Either of 171 these is probably a mistake. 172 173+---------+ 174| DOMAINS | 175+---------+ 176 177You will probably want to collect domain-dependent defines into one 178file, referenced by the DOMAIN macro. For example, our Berkeley 179domain file includes definitions for several internal distinguished 180hosts: 181 182UUCP_RELAY The host that will forward UUCP-addressed email. 183 If not defined, all UUCP sites must be directly 184 connected. 185BITNET_RELAY The host that will forward BITNET-addressed email. 186 If not defined, the .BITNET pseudo-domain won't work. 187CSNET_RELAY The host that will forward CSNET-addressed email. 188 If not defined, the .CSNET pseudo-domain won't work. 189LOCAL_RELAY The site that will handle unqualified names -- that 190 is, names with out an @domain extension. If not set, 191 they are assumed to belong on this machine. This 192 allows you to have a central site to store a 193 company- or department-wide alias database. This 194 only works at small sites, and there are better 195 methods. 196 197The domain file can also be used to define a domain name, if needed 198(using "DD<domain>") and set certain site-wide features. If all hosts 199at your site masquerade behind one email name, you could also use 200MASQUERADE_AS here. 201 202You do not have to define a domain -- in particular, if you are a 203single machine sitting off somewhere, it is probably more work than 204it's worth. This is just a mechanism for combining "domain dependent 205knowledge" into one place. 206 207+---------+ 208| MAILERS | 209+---------+ 210 211There are fewer mailers supported in this version than the previous 212version, owing mostly to a simpler world. 213 214local The local and prog mailers. You will almost always 215 need these; the only exception is if you relay ALL 216 your mail to another site. This mailer is included 217 automatically. 218 219smtp The Simple Mail Transport Protocol mailer. This does 220 not hide hosts behind a gateway or another other 221 such hack; it assumes a world where everyone is 222 running the name server. 223 224uucp The Unix-to-Unix Copy Program mailer. Actually, this 225 defines two mailers, "uucp" and "suucp". The latter 226 is for when you know that the UUCP mailer at the other 227 end can handle multiple recipients in one transfer. 228 When you invoke this, sendmail looks for all names in 229 the $=U class and sends them to the uucp mailer; all 230 names in the $=Y class are sent to suucp. Note that 231 this is a function of what version of rmail runs on 232 the receiving end, and hence may be out of your control. 233 234usenet Usenet (network news) delivery. If this is specified, 235 an extra rule is added to ruleset 0 that forwards all 236 local email for users named ``group.usenet'' to the 237 ``inews'' program. Note that this works for all groups, 238 and may be considered a security problem. 239 240fax Facsimile transmission. This is experimental and based 241 on Sam Leffler's FlexFAX software. For more information, 242 see below. 243 244 245+----------+ 246| FEATURES | 247+----------+ 248 249Special features can be requested using the "FEATURE" macro. For 250example, the .mc line: 251 252 FEATURE(use_cw_file) 253 254tells sendmail that you want to have it read an /etc/sendmail.cw 255file to get values for class $=w. Available features are: 256 257use_cw_file Read the file /etc/sendmail.cw file to get alternate 258 names for this host. This might be used if you were 259 on a host that MXed for a dynamic set of other 260 hosts. If the set is static, just including the line 261 "Cw<name1> <name2> ..." is probably superior. 262 The actual filename can be overridden by redefining 263 confCW_FILE. 264redirect Reject all mail addressed to "address.REDIRECT" with 265 a ``551 User not local; please try <address>'' message. 266 If this is set, you can alias people who have left 267 to their new address with ".REDIRECT" appended. 268nouucp Don't do anything special with UUCP addresses at all. 269notsticky By default, email sent to "user@local.host" are marked 270 as "sticky" -- that is, the local addresses aren't 271 matched against UDB and don't go through ruleset 5. 272 This features disables this treatment. It would 273 normally be used on network gateway machines. 274 275Other FEATUREs should be defined, but I was trying to keep these 276config files fairly lean and mean. 277 278 279+-------+ 280| HACKS | 281+-------+ 282 283Some things just can't be called features. To make this clear, 284they go in the hack subdirectory and are referenced using the HACK 285macro. These will tend to be site-dependent. The release 286includes the Berkeley-dependent "cssubdomain" hack (that makes 287sendmail accept local names in either Berkeley.EDU or CS.Berkeley.EDU; 288this is intended as a short-term aid while we move hosts into 289subdomains. 290 291 292+--------------------+ 293| SITE CONFIGURATION | 294+--------------------+ 295 296Complex sites will need more local configuration information, such as 297lists of UUCP hosts they speak with directly. This can get a bit more 298tricky. For an example of a "complex" site, see cf/ucbvax.mc. 299 300The SITECONFIG macro allows you to indirectly reference site-dependent 301configuration information stored in the siteconfig subdirectory. For 302example, the line 303 304 SITECONFIG(uucp.ucbvax, ucbvax, U) 305 306reads the file uucp.ucbvax for local connection information. The 307second parameter is the local name (in this case just "ucbvax" since 308it is locally connected, and hence a UUCP hostname) and the name of 309the class in which to store the host information. Another SITECONFIG 310line reads 311 312 SITECONFIG(uucp.ucbarpa, ucbarpa.Berkeley.EDU, W) 313 314This says that the file uucp.ucbarpa contains the list of UUCP sites 315connected to ucbarpa.Berkeley.EDU. The $=W class will be used to 316store this list. [The machine ucbarpa is gone now, but I've left 317this out-of-date configuration file around to demonstrate how you 318might do this.] 319 320The siteconfig file (e.g., siteconfig/uucp.ucbvax.m4) contains nothing 321more than a sequence of SITE macros describing connectivity. For 322example: 323 324 SITE(cnmat) 325 SITE(sgi olympus) 326 327The second example demonstrates that you can use two names on the 328same line; these are usually aliases for the same host (or are at 329least in the same company). 330 331 332+-------------------+ 333| TWEAKING RULESETS | 334+-------------------+ 335 336For more complex configurations, you can define special rules. 337The macro LOCAL_RULE_3 introduces rules that are used in canonicalizing 338the names. Any modifications made here are reflected in the header. 339 340A common use is to convert old UUCP addreses to SMTP addresses using 341the UUCPSMTP macro. For example: 342 343 LOCAL_RULE_3 344 UUCPSMTP(decvax, decvax.dec.com) 345 UUCPSMTP(research, research.att.com) 346 347will cause addresses of the form "decvax!user" and "research!user" 348to be converted to "user@decvax.dec.com" and "user@research.att.com" 349respectively. 350 351This could also be used to look hosts in a database map: 352 353 LOCAL_RULE_3 354 R$* < @ $+ > $* $: $1 < @ $(hostmap $2 $) > $3 355 356This map would be defined in the LOCAL_CONFIG portion, as shown below. 357 358Similarly, LOCAL_RULE_0 can be used to introduce new parsing rules. 359For example, new rules are needed to parse hostnames that you accept 360via MX records. For example, you might have: 361 362 LOCAL_RULE_0 363 R$+ < @ cnmat.Berkeley.EDU > $#uucp $@ cnmat $: $1 364 365You would use this if you had installed an MX record for cnmat.Berkeley.EDU 366pointing at this host; this rule catches the message and forwards it on 367using UUCP. 368 369A similar macro is LOCAL_CONFIG. This introduces lines added after the 370boilerplate option setting but before rulesets, and can be used to 371declare local database maps or whatever. For example: 372 373 LOCAL_CONFIG 374 Khostmap hash /etc/hostmap.db 375 Kyplocal nis -m hosts.byname 376 377 378+---------------------------+ 379| MASQUERADING AND RELAYING | 380+---------------------------+ 381 382You can have your host masquerade as another using 383 384 MASQUERADE_AS(host.domain) 385 386This causes outgoing SMTP mail to be labelled as coming from the 387indicated domain, rather than $j. One normally masquerades as one 388of your own subdomains (for example, it's unlikely that I would 389choose to masquerade as an MIT site). 390 391there are always users that need to be "exposed" -- that is, their 392internal site name should be displayed instead of the masquerade name. 393Root is an example. You can add users to this list using 394 395 EXPOSED_USER(usernames) 396 397This adds users to class E; you could also use something like 398 399 FE/etc/sendmail.cE 400 401You can also arrange to relay all unqualified names (that is, names 402without @host) to a relay host. For example, if you have a central 403email server, you might relay to that host so that users don't have 404to have .forward files or aliases. You can do this using 405 406 define(`LOCAL_RELAY', mailer:hostname) 407 408The ``mailer:'' can be omitted, in which case the mailer defaults to 409"smtp". There are some user names that you don't want relayed, perhaps 410because of local aliases. A common example is root, which may be 411locally aliased. You can add entries to this list using 412 413 LOCAL_USER(usernames) 414 415This adds users to class L; you could also use something like 416 417 FL/etc/sendmail.cL 418 419If you want all mail sent to a centralized hub, as for a shared 420/var/spool/mail scheme, use 421 422 define(`MAIL_HUB', mailer:hostname) 423 424Again, ``mailer:'' defaults to "smtp". If you define both LOCAL_RELAY 425and MAIL_HUB, unqualified names and names in class L will be sent to 426the LOCAL_RELAY and other local names will be sent to MAIL_HUB. For 427example, if are on machine mastodon.CS.Berkeley.EDU, the following 428combinations of settings will have the indicated effects: 429 430email sent to.... eric eric@mastodon.CS.Berkeley.EDU 431 432LOCAL_RELAY set to mail.CS.Berkeley.EDU (delivered locally) 433mail.CS.Berkeley.EDU 434 435MAIL_HUB set to mammoth.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU 436mammoth.CS.Berkeley.EDU 437 438Both LOCAL_RELAY and mail.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU 439MAIL_HUB set as above 440 441 442+-------------------------------+ 443| NON-SMTP BASED CONFIGURATIONS | 444+-------------------------------+ 445 446These configuration files are designed primarily for use by SMTP-based 447sites. I don't pretend that they are well tuned for UUCP-only or 448UUCP-primarily nodes (the latter is defined as a small local net 449connected to the rest of the world via UUCP). However, there is one 450hook to handle some special cases. 451 452You can define a ``smart host'' that understands a richer address syntax 453using: 454 455 define(`SMART_HOST', mailer:hostname) 456 457In this case, the ``mailer:'' defaults to "suucp". Any messages that 458can't be handled using the usual UUCP rules are passed to this host. 459 460If you are on a local SMTP-based net that connects to the outside 461world via UUCP, you can use LOCAL_NET_CONFIG to add appropriate rules. 462For example: 463 464 define(`SMART_HOST', suucp:uunet) 465 LOCAL_NET_CONFIG 466 R$* < @ $* .$m > $* $#smtp $@ $2.$m $: $1 < @ $2.$m > $3 467 468This will cause all names that end in your domain name ($m) via 469SMTP; anything else will be sent via suucp (smart UUCP) to uunet. 470 471 472+------------------+ 473| FlexFAX SOFTWARE | 474+------------------+ 475 476Sam Leffler's FlexFAX software is still in beta test -- but he expects a 477public version out "later this week" [as of 3/1/93]. The following 478blurb is direct from Sam: 479 480 $Header: /usr/people/sam/fax/RCS/HOWTO,v 1.7 93/02/08 09:00:55 sam Exp $ 481 482 How To Obtain This Software (in case all you get is this file) 483 484 The source code is available for public ftp on 485 sgi.com sgi/fax/v2.1beta.tar.Z 486 (192.48.153.1) 487 488 You can also obtain inst'able images for Silicon Graphics machines from 489 sgi.com sgi/fax/v2.1beta.inst.tar 490 (192.48.153.1) 491 492 For example, 493 % ftp -n sgi.com 494 .... 495 ftp> user anonymous 496 ... <type in password> 497 ftp> cd sgi/fax 498 ftp> binary 499 ftp> get v2.1beta.tar.Z 500 501 If you cannot use FTP at all, there is a service called "ftpmail" 502 available from gateekeeper.dec.com: you can send e-mail to this 503 machine and it will use FTP to retrieve files for you and send you the 504 files back again via e-mail. To find out more about the ftpmail 505 service, send a message to "ftpmail@gatekeeper.dec.com" whose body 506 consists of the single line "help". 507 508 Internal to Silicon Graphics there are inst'able images on the host 509 flake.asd in the directory /d/dist. Thus you can do something like: 510 511 % inst -f flake.asd.sgi.com:/d/dist/flexfax 512 513 to install the software on your machine. 514 515 The external distributions come in a compressed or uncompressed tar 516 file. To extract the source distribution: 517 518 % zcat v2.1beta.tar.Z | tar xf - 519 520 (uncompress and extract individual files in current directory). To 521 unpack and install the client portion of the inst'able distribution: 522 523 % mkdir dist 524 % cd dist; tar xf ../v2.1beta.inst.tar; cd .. 525 % inst -f dist/flexfax 526 ... 527 inst> go 528 529 (Note, the dist subdirectory is because some versions of inst fail if 530 the files are in the current directory.) Server binaries is also 531 included in the inst'able images as flexfax.server.*. It is not 532 installed by default, so to get it also you need to extract the do: 533 534 % inst -f flexfax 535 ... 536 inst> install flexfax.server.* 537 inst> go 538 539 The SGI binaries were built for Version 4.0.5 of the IRIX operating 540 system. They should work w/o problem on earlier versions of the 541 system, but I have not fully tested this. Also, note that to install a 542 server on an SGI machine, you need to have installed the Display 543 PostScript execution environment product (dps_eoe). Otherwise, the fax 544 server will not be able to convert PostScript to facsimile for 545 transmission. 546 547 If you are working from the source distribution, look at the file README 548 in the top of the source tree. If you are working from the inst images, 549 you need to run faxaddmodem to setup and configure your fax modem. Do 550 man faxaddmodem for more information. 551 552Also from Sam: 553 554 A mailing list for users of this software is located on sgi.com. 555 If you want to join this mailing list or have a list-related request 556 such as getting your name removed from it, send a request to 557 558 flexfax-request@sgi.com 559 560 Submissions (including bug reports) should be directed to: 561 562 flexfax@sgi.com 563 564 565+--------------------------------+ 566| TWEAKING CONFIGURATION OPTIONS | 567+--------------------------------+ 568 569There are a large number of configuration options that don't normally 570need to be changed. However, if you feel you need to tweak them, you 571can define the following M4 variables. This list is shown in four 572columns: the name you define, the default value for that definition, 573the option or macro that is affected (either Ox for an option or Dx 574for a macro), and a brief description. Greater detail of the semantics 575can be found in the Installation and Operations Guide. 576 577M4 Variable Name Default Mac/Opt Description 578confMAILER_NAME MAILER-DAEMON Dn The sender name used for 579 internally generated 580 outgoing messages. 581confFROM_LINE From $?<$<$|$g$. $d The From_ line used when 582 Dl sending to files or programs. 583confFROM_HEADER $?x$x <$g>$|$g$. The format of an internally 584 Dq generated From: address. 585confOPERATORS .:%@!^/[] Do Address operator characters. 586confSTMP_LOGIN_MSG $j Sendmail $v/$Z ready at $b 587 De The initial (spontaneous) 588 SMTP greeting message. 589confEIGHT_BIT_INPUT False O8 Use 8-bit input? 590confALIAS_WAIT 10 Oa Wait (in minutes) for alias 591 file rebuild. 592confMIN_FREE_BLOCKS 4 Ob Minimum number of free blocks 593 on queue filesystem to accept 594 SMTP mail. 595confBLANK_SUB . OB Blank (space) substitution 596 character. 597confCON_EXPENSIVE False Oc Connect immediately to 598 mailers marked expensive? 599confCHECKPOINT_INTERVAL 10 OC Checkpoint queue files 600 every N recipients. 601confDELIVERY_MODE background Od Default delivery mode. 602confAUTO_REBUILD False OD Automatically rebuild 603 alias file if needed. 604confERROR_MODE (undefined) Oe Error message mode. 605confERROR_MESSAGE (undefined) OE Error message header/file. 606confSAVE_FROM_LINES False Of Save extra leading 607 From_ lines. 608confTEMP_FILE_MODE 0600 OF Temporary file mode. 609confDEF_GROUP_ID 1 Og Default group id. 610confMATCH_GECOS False OG Match GECOS field. 611confMAX_HOP 17 Oh Maximum hop count. 612confIGNORE_DOTS False Oi Ignore dot as terminator 613 for incoming messages? 614confBIND_OPTS (empty) OI Default options for BIND. 615confMCI_CACHE_SIZE 2 Ok Size of open connection cache. 616confMCI_CACHE_TIMEOUT 5m OK Open connection cache timeout. 617confLOG_LEVEL 9 OL Log level. 618confME_TOO False Om Include sender in group 619 expansions. 620confCHECK_ALIASES True On Check RHS of aliases when 621 running newaliases. 622confOLD_STYLE_HEADERS True Oo Assume that headers without 623 special chars are old style. 624confPRIVACY_FLAGS public Op Privacy flags. 625confCOPY_ERRORS_TO (undefined) OP Address for additional copies 626 of all error messages. 627confQUEUE_FACTOR (undefined) Oq Slope of queue-only function 628confREAD_TIMEOUT (undefined) Or SMTP read timeouts. 629confSAFE_QUEUE True Os Commit all messages to disk 630 before forking. 631confMESSAGE_TIMEOUT 5d OT Timeout for messages before 632 sending error message. 633confTIME_ZONE USE_SYSTEM Oz Time zone info -- can be 634 USE_SYSTEM to use the system's 635 idea, USE_TZ to use the user's 636 TZ envariable, or something 637 else to force that value. 638confDEF_USER_ID 1 Ou Default user id. 639confNO_WILDCARD_MX False Ow No wildcard MX records matches 640 our domain. 641confQUEUE_LA 8 Ox Load average at which queue-only 642 function kicks in. 643confREFUSE_LA 12 OX Load average at which incoming 644 SMTP connections are refused. 645confSEPARATE_PROC False Oy Run all deliveries in a 646 separate process. 647confWORK_RECIPIENT_FACTOR 648 (undefined) OY Cost of each recipient. 649confWORK_CLASS_FACTOR (undefined) Oz Priority multiplier for class. 650confWORK_TIME_FACTOR (undefined) OZ Cost of each delivery attempt. 651confCW_FILE /etc/sendmail.cw Name of file used to get the 652 Fw local additions to the $=w 653 class. 654 655 656+-----------+ 657| HIERARCHY | 658+-----------+ 659 660Within this directory are several subdirectories, to wit: 661 662m4 General support routines. These are typically 663 very important and should not be changed without 664 very careful consideration. 665 666cf The configuration files themselves. They have 667 ".mc" suffixes, and must be run through m4 to 668 become complete. The resulting output should 669 have a ".cf" suffix. 670 671ostype Definitions describing a particular operating 672 system type. These should always be referenced 673 using the OSTYPE macro in the .mc file. Examples 674 include "bsd4.3", "bsd4.4", "sunos3.5", and 675 "sunos4.1". 676 677domain Definitions describing a particular domain, referenced 678 using the DOMAIN macro in the .mc file. These are 679 site dependent; for example, we contribute "cs.exposed.m4" 680 and "cs.hidden.m4" which both describe hosts in the 681 CS.Berkeley.EDU subdomain; the former displays the local 682 hostname (e.g., mammoth.CS.Berkeley.EDU), whereas the 683 latter does its best to hide the identity of the local 684 workstation inside the CS subdomain. 685 686mailer Descriptions of mailers. These are referenced using 687 the MAILER macro in the .mc file. 688 689sh Shell files used when building the .cf file from the 690 .mc file in the cf subdirectory. 691 692feature These hold special orthogonal features that you might 693 want to include. They should be referenced using 694 the FEATURE macro. 695 696hack Local hacks. These can be referenced using the HACK 697 macro. They shouldn't be of more than voyeuristic 698 interest outside the .Berkeley.EDU domain, but who knows? 699 We've all got our own peccadilloes. 700 701siteconfig Site configuration -- e.g., tables of locally connected 702 UUCP sites. 703 704 705+------------------------+ 706| ADMINISTRATIVE DETAILS | 707+------------------------+ 708 709The following sections detail usage of certain internal parts of the 710sendmail.cf file. Read them carefully if you are trying to modify 711the current model. If you find the above descriptions adequate, these 712should be {boring, confusing, tedious, ridiculous} (pick one or more). 713 714RULESETS (* means built in to sendmail) 715 716 0 * Parsing 717 1 * Sender rewriting 718 2 * Recipient rewriting 719 3 * Canonicalization 720 4 * Post cleanup 721 5 * Local address rewrite (after aliasing) 722 6 Bottom half of Ruleset 3 723 7 Hook for recursive ruleset 0 call 724 8 725 9 726 727 728MAILERS 729 730 0 local, prog local and program mailers 731 1 smtp SMTP channel 732 2 uucp UNIX-to-UNIX Copy Program 733 3 netnews Network News delivery 734 4 fax Sam Leffler's FlexFAX software 735 736 737MACROS 738 739 A 740 B Bitnet Relay 741 C CSNET Relay 742 D The local domain -- usually not needed 743 E 744 F FAX Relay 745 G 746 H mail Hub (for mail clusters) 747 I 748 J 749 K 750 L 751 M Masquerade (who I claim to be) 752 N 753 O 754 P 755 Q 756 R Relay (for unqualified names) 757 S Smart Host 758 T 759 U my UUCP name (if I have a UUCP connection) 760 V UUCP Relay (class V hosts) 761 W UUCP Relay (class W hosts) 762 X UUCP Relay (class X hosts) 763 Y UUCP Relay (all other hosts) 764 Z Version number 765 766 767CLASSES 768 769 A 770 B 771 C 772 D 773 E addresses that should not seem to come from $M 774 F hosts we forward for 775 G 776 H 777 I 778 J 779 K 780 L addresses that should not be forwarded to $R 781 M 782 N 783 O operators that indicate network operations (cannot be in local names) 784 P 785 Q 786 R 787 S 788 T 789 U locally connected UUCP hosts 790 V UUCP hosts connected to relay $V 791 W UUCP hosts connected to relay $W 792 X UUCP hosts connected to relay $X 793 Y locally connected smart UUCP hosts 794 Z 795 . the class containing only a dot 796 797 798M4 DIVERSIONS 799 800 1 Local host detection and resolution 801 2 Local Ruleset 3 additions 802 3 Local Ruleset 0 additions 803 4 UUCP Ruleset 0 additions 804 5 locally interpreted names (overrides $R) 805 6 local configuration (at top of file) 806 7 mailer definitions 807 8 special local name recognition (late in ruleset 3) 808 9 special local name recognition (late in ruleset 0) 809