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