1 2 3 NEW SENDMAIL CONFIGURATION FILES 4 5 Eric Allman <eric@CS.Berkeley.EDU> 6 7 @(#)README 6.18 (Berkeley) 03/29/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. The FEATURE may contain a single 256optional parameter -- for example: 257 258 FEATURE(mailertable, dbm /usr/lib/mailertable) 259 260Available features are: 261 262use_cw_file Read the file /etc/sendmail.cw file to get alternate 263 names for this host. This might be used if you were 264 on a host that MXed for a dynamic set of other 265 hosts. If the set is static, just including the line 266 "Cw<name1> <name2> ..." is probably superior. 267 The actual filename can be overridden by redefining 268 confCW_FILE. 269redirect Reject all mail addressed to "address.REDIRECT" with 270 a ``551 User not local; please try <address>'' message. 271 If this is set, you can alias people who have left 272 to their new address with ".REDIRECT" appended. 273nouucp Don't do anything special with UUCP addresses at all. 274notsticky By default, email sent to "user@local.host" are marked 275 as "sticky" -- that is, the local addresses aren't 276 matched against UDB and don't go through ruleset 5. 277 This features disables this treatment. It would 278 normally be used on network gateway machines. 279mailertable Include a "mailer table" which can be used to override 280 routing for particular domains. The argument of the 281 FEATURE may be the key definition. If none is specified, 282 the definition used is: 283 hash /etc/mailertable.db -o 284 Keys in this database must be of the form: 285 mailer:domain 286 287Other FEATUREs should be defined, but I was trying to keep these 288config files fairly lean and mean. 289 290 291+-------+ 292| HACKS | 293+-------+ 294 295Some things just can't be called features. To make this clear, 296they go in the hack subdirectory and are referenced using the HACK 297macro. These will tend to be site-dependent. The release 298includes the Berkeley-dependent "cssubdomain" hack (that makes 299sendmail accept local names in either Berkeley.EDU or CS.Berkeley.EDU; 300this is intended as a short-term aid while we move hosts into 301subdomains. 302 303 304+--------------------+ 305| SITE CONFIGURATION | 306+--------------------+ 307 308Complex sites will need more local configuration information, such as 309lists of UUCP hosts they speak with directly. This can get a bit more 310tricky. For an example of a "complex" site, see cf/ucbvax.mc. 311 312The SITECONFIG macro allows you to indirectly reference site-dependent 313configuration information stored in the siteconfig subdirectory. For 314example, the line 315 316 SITECONFIG(uucp.ucbvax, ucbvax, U) 317 318reads the file uucp.ucbvax for local connection information. The 319second parameter is the local name (in this case just "ucbvax" since 320it is locally connected, and hence a UUCP hostname) and the name of 321the class in which to store the host information. Another SITECONFIG 322line reads 323 324 SITECONFIG(uucp.ucbarpa, ucbarpa.Berkeley.EDU, W) 325 326This says that the file uucp.ucbarpa contains the list of UUCP sites 327connected to ucbarpa.Berkeley.EDU. The $=W class will be used to 328store this list. [The machine ucbarpa is gone now, but I've left 329this out-of-date configuration file around to demonstrate how you 330might do this.] 331 332The siteconfig file (e.g., siteconfig/uucp.ucbvax.m4) contains nothing 333more than a sequence of SITE macros describing connectivity. For 334example: 335 336 SITE(cnmat) 337 SITE(sgi olympus) 338 339The second example demonstrates that you can use two names on the 340same line; these are usually aliases for the same host (or are at 341least in the same company). 342 343 344+-------------------+ 345| TWEAKING RULESETS | 346+-------------------+ 347 348For more complex configurations, you can define special rules. 349The macro LOCAL_RULE_3 introduces rules that are used in canonicalizing 350the names. Any modifications made here are reflected in the header. 351 352A common use is to convert old UUCP addreses to SMTP addresses using 353the UUCPSMTP macro. For example: 354 355 LOCAL_RULE_3 356 UUCPSMTP(decvax, decvax.dec.com) 357 UUCPSMTP(research, research.att.com) 358 359will cause addresses of the form "decvax!user" and "research!user" 360to be converted to "user@decvax.dec.com" and "user@research.att.com" 361respectively. 362 363This could also be used to look hosts in a database map: 364 365 LOCAL_RULE_3 366 R$* < @ $+ > $* $: $1 < @ $(hostmap $2 $) > $3 367 368This map would be defined in the LOCAL_CONFIG portion, as shown below. 369 370Similarly, LOCAL_RULE_0 can be used to introduce new parsing rules. 371For example, new rules are needed to parse hostnames that you accept 372via MX records. For example, you might have: 373 374 LOCAL_RULE_0 375 R$+ < @ cnmat.Berkeley.EDU > $#uucp $@ cnmat $: $1 376 377You would use this if you had installed an MX record for cnmat.Berkeley.EDU 378pointing at this host; this rule catches the message and forwards it on 379using UUCP. 380 381You can also tweak rulesets 1 and 2 using LOCAL_RULE_1 and LOCAL_RULE_2. 382These rulesets are normally empty. 383 384A similar macro is LOCAL_CONFIG. This introduces lines added after the 385boilerplate option setting but before rulesets, and can be used to 386declare local database maps or whatever. For example: 387 388 LOCAL_CONFIG 389 Khostmap hash /etc/hostmap.db 390 Kyplocal nis -m hosts.byname 391 392 393+---------------------------+ 394| MASQUERADING AND RELAYING | 395+---------------------------+ 396 397You can have your host masquerade as another using 398 399 MASQUERADE_AS(host.domain) 400 401This causes outgoing SMTP mail to be labelled as coming from the 402indicated domain, rather than $j. One normally masquerades as one 403of your own subdomains (for example, it's unlikely that I would 404choose to masquerade as an MIT site). 405 406there are always users that need to be "exposed" -- that is, their 407internal site name should be displayed instead of the masquerade name. 408Root is an example. You can add users to this list using 409 410 EXPOSED_USER(usernames) 411 412This adds users to class E; you could also use something like 413 414 FE/etc/sendmail.cE 415 416You can also arrange to relay all unqualified names (that is, names 417without @host) to a relay host. For example, if you have a central 418email server, you might relay to that host so that users don't have 419to have .forward files or aliases. You can do this using 420 421 define(`LOCAL_RELAY', mailer:hostname) 422 423The ``mailer:'' can be omitted, in which case the mailer defaults to 424"smtp". There are some user names that you don't want relayed, perhaps 425because of local aliases. A common example is root, which may be 426locally aliased. You can add entries to this list using 427 428 LOCAL_USER(usernames) 429 430This adds users to class L; you could also use something like 431 432 FL/etc/sendmail.cL 433 434If you want all mail sent to a centralized hub, as for a shared 435/var/spool/mail scheme, use 436 437 define(`MAIL_HUB', mailer:hostname) 438 439Again, ``mailer:'' defaults to "smtp". If you define both LOCAL_RELAY 440and MAIL_HUB, unqualified names and names in class L will be sent to 441the LOCAL_RELAY and other local names will be sent to MAIL_HUB. For 442example, if are on machine mastodon.CS.Berkeley.EDU, the following 443combinations of settings will have the indicated effects: 444 445email sent to.... eric eric@mastodon.CS.Berkeley.EDU 446 447LOCAL_RELAY set to mail.CS.Berkeley.EDU (delivered locally) 448mail.CS.Berkeley.EDU 449 450MAIL_HUB set to mammoth.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU 451mammoth.CS.Berkeley.EDU 452 453Both LOCAL_RELAY and mail.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU 454MAIL_HUB set as above 455 456 457+-------------------------------+ 458| NON-SMTP BASED CONFIGURATIONS | 459+-------------------------------+ 460 461These configuration files are designed primarily for use by SMTP-based 462sites. I don't pretend that they are well tuned for UUCP-only or 463UUCP-primarily nodes (the latter is defined as a small local net 464connected to the rest of the world via UUCP). However, there is one 465hook to handle some special cases. 466 467You can define a ``smart host'' that understands a richer address syntax 468using: 469 470 define(`SMART_HOST', mailer:hostname) 471 472In this case, the ``mailer:'' defaults to "suucp". Any messages that 473can't be handled using the usual UUCP rules are passed to this host. 474 475If you are on a local SMTP-based net that connects to the outside 476world via UUCP, you can use LOCAL_NET_CONFIG to add appropriate rules. 477For example: 478 479 define(`SMART_HOST', suucp:uunet) 480 LOCAL_NET_CONFIG 481 R$* < @ $* .$m > $* $#smtp $@ $2.$m $: $1 < @ $2.$m > $3 482 483This will cause all names that end in your domain name ($m) via 484SMTP; anything else will be sent via suucp (smart UUCP) to uunet. 485 486 487+------------------+ 488| FlexFAX SOFTWARE | 489+------------------+ 490 491Sam Leffler's FlexFAX software is still in beta test -- but he expects a 492public version out "later this week" [as of 3/1/93]. The following 493blurb is direct from Sam: 494 495 $Header: /usr/people/sam/fax/RCS/HOWTO,v 1.7 93/02/08 09:00:55 sam Exp $ 496 497 How To Obtain This Software (in case all you get is this file) 498 499 The source code is available for public ftp on 500 sgi.com sgi/fax/v2.1beta.tar.Z 501 (192.48.153.1) 502 503 You can also obtain inst'able images for Silicon Graphics machines from 504 sgi.com sgi/fax/v2.1beta.inst.tar 505 (192.48.153.1) 506 507 For example, 508 % ftp -n sgi.com 509 .... 510 ftp> user anonymous 511 ... <type in password> 512 ftp> cd sgi/fax 513 ftp> binary 514 ftp> get v2.1beta.tar.Z 515 516 If you cannot use FTP at all, there is a service called "ftpmail" 517 available from gateekeeper.dec.com: you can send e-mail to this 518 machine and it will use FTP to retrieve files for you and send you the 519 files back again via e-mail. To find out more about the ftpmail 520 service, send a message to "ftpmail@gatekeeper.dec.com" whose body 521 consists of the single line "help". 522 523 Internal to Silicon Graphics there are inst'able images on the host 524 flake.asd in the directory /d/dist. Thus you can do something like: 525 526 % inst -f flake.asd.sgi.com:/d/dist/flexfax 527 528 to install the software on your machine. 529 530 The external distributions come in a compressed or uncompressed tar 531 file. To extract the source distribution: 532 533 % zcat v2.1beta.tar.Z | tar xf - 534 535 (uncompress and extract individual files in current directory). To 536 unpack and install the client portion of the inst'able distribution: 537 538 % mkdir dist 539 % cd dist; tar xf ../v2.1beta.inst.tar; cd .. 540 % inst -f dist/flexfax 541 ... 542 inst> go 543 544 (Note, the dist subdirectory is because some versions of inst fail if 545 the files are in the current directory.) Server binaries is also 546 included in the inst'able images as flexfax.server.*. It is not 547 installed by default, so to get it also you need to extract the do: 548 549 % inst -f flexfax 550 ... 551 inst> install flexfax.server.* 552 inst> go 553 554 The SGI binaries were built for Version 4.0.5 of the IRIX operating 555 system. They should work w/o problem on earlier versions of the 556 system, but I have not fully tested this. Also, note that to install a 557 server on an SGI machine, you need to have installed the Display 558 PostScript execution environment product (dps_eoe). Otherwise, the fax 559 server will not be able to convert PostScript to facsimile for 560 transmission. 561 562 If you are working from the source distribution, look at the file README 563 in the top of the source tree. If you are working from the inst images, 564 you need to run faxaddmodem to setup and configure your fax modem. Do 565 man faxaddmodem for more information. 566 567Also from Sam: 568 569 A mailing list for users of this software is located on sgi.com. 570 If you want to join this mailing list or have a list-related request 571 such as getting your name removed from it, send a request to 572 573 flexfax-request@sgi.com 574 575 Submissions (including bug reports) should be directed to: 576 577 flexfax@sgi.com 578 579 580+--------------------------------+ 581| TWEAKING CONFIGURATION OPTIONS | 582+--------------------------------+ 583 584There are a large number of configuration options that don't normally 585need to be changed. However, if you feel you need to tweak them, you 586can define the following M4 variables. This list is shown in four 587columns: the name you define, the default value for that definition, 588the option or macro that is affected (either Ox for an option or Dx 589for a macro), and a brief description. Greater detail of the semantics 590can be found in the Installation and Operations Guide. 591 592M4 Variable Name Default Mac/Opt Description 593confMAILER_NAME MAILER-DAEMON Dn The sender name used for 594 internally generated 595 outgoing messages. 596confFROM_LINE From $g $d Dl The From_ line used when 597 sending to files or programs. 598confFROM_HEADER $?x$x <$g>$|$g$. The format of an internally 599 Dq generated From: address. 600confOPERATORS .:%@!^/[] Do Address operator characters. 601confSTMP_LOGIN_MSG $j Sendmail $v/$Z ready at $b 602 De The initial (spontaneous) 603 SMTP greeting message. 604confEIGHT_BIT_INPUT True O8 Use 8-bit input? 605confALIAS_WAIT 10 Oa Wait (in minutes) for alias 606 file rebuild. 607confMIN_FREE_BLOCKS 4 Ob Minimum number of free blocks 608 on queue filesystem to accept 609 SMTP mail. 610confBLANK_SUB . OB Blank (space) substitution 611 character. 612confCON_EXPENSIVE False Oc Connect immediately to 613 mailers marked expensive? 614confCHECKPOINT_INTERVAL 10 OC Checkpoint queue files 615 every N recipients. 616confDELIVERY_MODE background Od Default delivery mode. 617confAUTO_REBUILD False OD Automatically rebuild 618 alias file if needed. 619confERROR_MODE (undefined) Oe Error message mode. 620confERROR_MESSAGE (undefined) OE Error message header/file. 621confSAVE_FROM_LINES False Of Save extra leading 622 From_ lines. 623confTEMP_FILE_MODE 0600 OF Temporary file mode. 624confDEF_GROUP_ID 1 Og Default group id. 625confMATCH_GECOS False OG Match GECOS field. 626confMAX_HOP 17 Oh Maximum hop count. 627confIGNORE_DOTS False Oi Ignore dot as terminator 628 for incoming messages? 629confBIND_OPTS (empty) OI Default options for BIND. 630confMCI_CACHE_SIZE 2 Ok Size of open connection cache. 631confMCI_CACHE_TIMEOUT 5m OK Open connection cache timeout. 632confLOG_LEVEL 9 OL Log level. 633confME_TOO False Om Include sender in group 634 expansions. 635confCHECK_ALIASES True On Check RHS of aliases when 636 running newaliases. 637confOLD_STYLE_HEADERS True Oo Assume that headers without 638 special chars are old style. 639confDAEMON_OPTIONS (undefined) OO SMTP daemon options. 640confPRIVACY_FLAGS authwarnings Op Privacy flags. 641confCOPY_ERRORS_TO (undefined) OP Address for additional copies 642 of all error messages. 643confQUEUE_FACTOR (undefined) Oq Slope of queue-only function 644confREAD_TIMEOUT (undefined) Or SMTP read timeouts. 645confSAFE_QUEUE True Os Commit all messages to disk 646 before forking. 647confMESSAGE_TIMEOUT 5d/4h OT Timeout for messages before 648 sending error/warning message. 649confTIME_ZONE USE_SYSTEM Oz Time zone info -- can be 650 USE_SYSTEM to use the system's 651 idea, USE_TZ to use the user's 652 TZ envariable, or something 653 else to force that value. 654confDEF_USER_ID 1 Ou Default user id. 655confUSERDB_SPEC (undefined) OU User database specification. 656confFALLBACK_MX (undefined) OV Fallback MX host. 657confNO_WILDCARD_MX False Ow No wildcard MX records matches 658 our domain. 659confQUEUE_LA 8 Ox Load average at which queue-only 660 function kicks in. 661confREFUSE_LA 12 OX Load average at which incoming 662 SMTP connections are refused. 663confSEPARATE_PROC False Oy Run all deliveries in a 664 separate process. 665confWORK_RECIPIENT_FACTOR 666 (undefined) OY Cost of each recipient. 667confWORK_CLASS_FACTOR (undefined) Oz Priority multiplier for class. 668confWORK_TIME_FACTOR (undefined) OZ Cost of each delivery attempt. 669confCW_FILE /etc/sendmail.cw Name of file used to get the 670 Fw local additions to the $=w 671 class. 672 673 674+-----------+ 675| HIERARCHY | 676+-----------+ 677 678Within this directory are several subdirectories, to wit: 679 680m4 General support routines. These are typically 681 very important and should not be changed without 682 very careful consideration. 683 684cf The configuration files themselves. They have 685 ".mc" suffixes, and must be run through m4 to 686 become complete. The resulting output should 687 have a ".cf" suffix. 688 689ostype Definitions describing a particular operating 690 system type. These should always be referenced 691 using the OSTYPE macro in the .mc file. Examples 692 include "bsd4.3", "bsd4.4", "sunos3.5", and 693 "sunos4.1". 694 695domain Definitions describing a particular domain, referenced 696 using the DOMAIN macro in the .mc file. These are 697 site dependent; for example, we contribute "cs.exposed.m4" 698 and "cs.hidden.m4" which both describe hosts in the 699 CS.Berkeley.EDU subdomain; the former displays the local 700 hostname (e.g., mammoth.CS.Berkeley.EDU), whereas the 701 latter does its best to hide the identity of the local 702 workstation inside the CS subdomain. 703 704mailer Descriptions of mailers. These are referenced using 705 the MAILER macro in the .mc file. 706 707sh Shell files used when building the .cf file from the 708 .mc file in the cf subdirectory. 709 710feature These hold special orthogonal features that you might 711 want to include. They should be referenced using 712 the FEATURE macro. 713 714hack Local hacks. These can be referenced using the HACK 715 macro. They shouldn't be of more than voyeuristic 716 interest outside the .Berkeley.EDU domain, but who knows? 717 We've all got our own peccadilloes. 718 719siteconfig Site configuration -- e.g., tables of locally connected 720 UUCP sites. 721 722 723+------------------------+ 724| ADMINISTRATIVE DETAILS | 725+------------------------+ 726 727The following sections detail usage of certain internal parts of the 728sendmail.cf file. Read them carefully if you are trying to modify 729the current model. If you find the above descriptions adequate, these 730should be {boring, confusing, tedious, ridiculous} (pick one or more). 731 732RULESETS (* means built in to sendmail) 733 734 0 * Parsing 735 1 * Sender rewriting 736 2 * Recipient rewriting 737 3 * Canonicalization 738 4 * Post cleanup 739 5 * Local address rewrite (after aliasing) 740 6 Bottom half of Ruleset 3 741 7 Hook for recursive ruleset 0 call 742 8 743 9 744 745 746MAILERS 747 748 0 local, prog local and program mailers 749 1 smtp SMTP channel 750 2 uucp UNIX-to-UNIX Copy Program 751 3 netnews Network News delivery 752 4 fax Sam Leffler's FlexFAX software 753 754 755MACROS 756 757 A 758 B Bitnet Relay 759 C CSNET Relay 760 D The local domain -- usually not needed 761 E 762 F FAX Relay 763 G 764 H mail Hub (for mail clusters) 765 I 766 J 767 K 768 L 769 M Masquerade (who I claim to be) 770 N 771 O 772 P 773 Q 774 R Relay (for unqualified names) 775 S Smart Host 776 T 777 U my UUCP name (if I have a UUCP connection) 778 V UUCP Relay (class V hosts) 779 W UUCP Relay (class W hosts) 780 X UUCP Relay (class X hosts) 781 Y UUCP Relay (all other hosts) 782 Z Version number 783 784 785CLASSES 786 787 A 788 B 789 C 790 D 791 E addresses that should not seem to come from $M 792 F hosts we forward for 793 G 794 H 795 I 796 J 797 K 798 L addresses that should not be forwarded to $R 799 M 800 N 801 O operators that indicate network operations (cannot be in local names) 802 P 803 Q 804 R 805 S 806 T 807 U locally connected UUCP hosts 808 V UUCP hosts connected to relay $V 809 W UUCP hosts connected to relay $W 810 X UUCP hosts connected to relay $X 811 Y locally connected smart UUCP hosts 812 Z 813 . the class containing only a dot 814 815 816M4 DIVERSIONS 817 818 1 Local host detection and resolution 819 2 Local Ruleset 3 additions 820 3 Local Ruleset 0 additions 821 4 UUCP Ruleset 0 additions 822 5 locally interpreted names (overrides $R) 823 6 local configuration (at top of file) 824 7 mailer definitions 825 8 special local name recognition (late in ruleset 3) 826 9 special local rulesets (1 and 2) 827