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