| README (42575) | README (43730) |
|---|---|
| 1 2 3 NEW SENDMAIL CONFIGURATION FILES 4 5 Eric Allman <eric@Sendmail.ORG> 6 | 1 2 3 NEW SENDMAIL CONFIGURATION FILES 4 5 Eric Allman <eric@Sendmail.ORG> 6 |
| 7 @(#)README 8.184 (Berkeley) 12/29/1998 | 7 @(#)README 8.186 (Berkeley) 2/3/1999 |
| 8 9 10This document describes the sendmail configuration files being used 11at Berkeley. These use features in the new (R8) sendmail; they will 12not work on other versions. 13 14These configuration files are probably not as general as previous 15versions, and don't handle as many of the weird cases automagically. --- 272 unchanged lines hidden (view full) --- 288 mailer. 289FAX_MAILER_MAX [100000] The maximum size message accepted for 290 transmission by FAX. 291POP_MAILER_PATH [/usr/lib/mh/spop] The pathname of the POP mailer. 292POP_MAILER_FLAGS [Penu] Flags added to POP mailer. Flags "lsDFM" 293 are always added. 294POP_MAILER_ARGS [pop $u] The arguments passed to the POP mailer. 295PROCMAIL_MAILER_PATH [/usr/local/bin/procmail] The path to the procmail | 8 9 10This document describes the sendmail configuration files being used 11at Berkeley. These use features in the new (R8) sendmail; they will 12not work on other versions. 13 14These configuration files are probably not as general as previous 15versions, and don't handle as many of the weird cases automagically. --- 272 unchanged lines hidden (view full) --- 288 mailer. 289FAX_MAILER_MAX [100000] The maximum size message accepted for 290 transmission by FAX. 291POP_MAILER_PATH [/usr/lib/mh/spop] The pathname of the POP mailer. 292POP_MAILER_FLAGS [Penu] Flags added to POP mailer. Flags "lsDFM" 293 are always added. 294POP_MAILER_ARGS [pop $u] The arguments passed to the POP mailer. 295PROCMAIL_MAILER_PATH [/usr/local/bin/procmail] The path to the procmail |
| 296 program. This is also used by FEATURE(local_procmail). | 296 program. This is also used by 297 FEATURE(`local_procmail'). |
| 297PROCMAIL_MAILER_FLAGS [SPhnu9] Flags added to Procmail mailer. Flags 298 ``DFM'' are always set. This is NOT used by | 298PROCMAIL_MAILER_FLAGS [SPhnu9] Flags added to Procmail mailer. Flags 299 ``DFM'' are always set. This is NOT used by |
| 299 FEATURE(local_procmail); tweak LOCAL_MAILER_FLAGS | 300 FEATURE(`local_procmail'); tweak LOCAL_MAILER_FLAGS |
| 300 instead. 301PROCMAIL_MAILER_ARGS [procmail -Y -m $h $f $u] The arguments passed to 302 the Procmail mailer. This is NOT used by | 301 instead. 302PROCMAIL_MAILER_ARGS [procmail -Y -m $h $f $u] The arguments passed to 303 the Procmail mailer. This is NOT used by |
| 303 FEATURE(local_procmail); tweak LOCAL_MAILER_ARGS | 304 FEATURE(`local_procmail'); tweak LOCAL_MAILER_ARGS |
| 304 instead. 305PROCMAIL_MAILER_MAX [undefined] If set, the maximum size message that 306 will be accepted by the procmail mailer. 307MAIL11_MAILER_PATH [/usr/etc/mail11] The path to the mail11 mailer. 308MAIL11_MAILER_FLAGS [nsFx] Flags for the mail11 mailer. 309MAIL11_MAILER_ARGS [mail11 $g $x $h $u] Arguments passed to the mail11 310 mailer. 311PH_MAILER_PATH [/usr/local/etc/phquery] The path to the phquery --- 10 unchanged lines hidden (view full) --- 322 will be accepted by the cyrus mailer. 323CYRUS_MAILER_USER [cyrus:mail] The user and group to become when 324 running the cyrus mailer. 325CYRUS_BB_MAILER_FLAGS [undefined] The flags used by the cyrusbb 326 mailer. The flags lsDFMnP are always included. 327CYRUS_BB_MAILER_ARGS [deliver -e -m $u] The arguments passed 328 to deliver cyrusbb mail. 329confEBINDIR [/usr/libexec] The directory for executables. | 305 instead. 306PROCMAIL_MAILER_MAX [undefined] If set, the maximum size message that 307 will be accepted by the procmail mailer. 308MAIL11_MAILER_PATH [/usr/etc/mail11] The path to the mail11 mailer. 309MAIL11_MAILER_FLAGS [nsFx] Flags for the mail11 mailer. 310MAIL11_MAILER_ARGS [mail11 $g $x $h $u] Arguments passed to the mail11 311 mailer. 312PH_MAILER_PATH [/usr/local/etc/phquery] The path to the phquery --- 10 unchanged lines hidden (view full) --- 323 will be accepted by the cyrus mailer. 324CYRUS_MAILER_USER [cyrus:mail] The user and group to become when 325 running the cyrus mailer. 326CYRUS_BB_MAILER_FLAGS [undefined] The flags used by the cyrusbb 327 mailer. The flags lsDFMnP are always included. 328CYRUS_BB_MAILER_ARGS [deliver -e -m $u] The arguments passed 329 to deliver cyrusbb mail. 330confEBINDIR [/usr/libexec] The directory for executables. |
| 330 Currently used for FEATURE(local_lmtp) and 331 FEATURE(smrsh). | 331 Currently used for FEATURE(`local_lmtp') and 332 FEATURE(`smrsh'). |
| 332 333 334 335+---------+ 336| DOMAINS | 337+---------+ 338 339You will probably want to collect domain-dependent defines into one --- 109 unchanged lines hidden (view full) --- 449 with the file /etc/procmailrcs/host.com reading: 450 451 :0 # forward mail for host.com 452 ! -oi -f $1 person@other.host 453 454 This would arrange for (anything)@host.com to be sent 455 to person@other.host. Within the procmail script, $1 is 456 the name of the sender and $2 is the name of the recipient. | 333 334 335 336+---------+ 337| DOMAINS | 338+---------+ 339 340You will probably want to collect domain-dependent defines into one --- 109 unchanged lines hidden (view full) --- 450 with the file /etc/procmailrcs/host.com reading: 451 452 :0 # forward mail for host.com 453 ! -oi -f $1 person@other.host 454 455 This would arrange for (anything)@host.com to be sent 456 to person@other.host. Within the procmail script, $1 is 457 the name of the sender and $2 is the name of the recipient. |
| 457 If you use this with FEATURE(local_procmail), the FEATURE | 458 If you use this with FEATURE(`local_procmail'), the FEATURE |
| 458 should be listed first. 459 460mail11 The DECnet mail11 mailer, useful only if you have the mail11 461 program from gatekeeper.dec.com:/pub/DEC/gwtools (and 462 DECnet, of course). This is for Phase IV DECnet support; 463 if you have Phase V at your site you may have additional 464 problems. 465 --- 7 unchanged lines hidden (view full) --- 473 "user+detail@local.host" syntax; it will deliver the mail to 474 the user's "detail" mailbox if the mailbox's ACL permits. 475 The cyrusbb mailer delivers to a system-wide cyrus mailbox 476 if the mailbox's ACL permits. 477 478 479The local mailer accepts addresses of the form "user+detail", where 480the "+detail" is not used for mailbox matching but is available | 459 should be listed first. 460 461mail11 The DECnet mail11 mailer, useful only if you have the mail11 462 program from gatekeeper.dec.com:/pub/DEC/gwtools (and 463 DECnet, of course). This is for Phase IV DECnet support; 464 if you have Phase V at your site you may have additional 465 problems. 466 --- 7 unchanged lines hidden (view full) --- 474 "user+detail@local.host" syntax; it will deliver the mail to 475 the user's "detail" mailbox if the mailbox's ACL permits. 476 The cyrusbb mailer delivers to a system-wide cyrus mailbox 477 if the mailbox's ACL permits. 478 479 480The local mailer accepts addresses of the form "user+detail", where 481the "+detail" is not used for mailbox matching but is available |
| 481to certain local mail programs (in particular, see FEATURE(local_procmail)). 482For example, "eric", "eric+sendmail", and "eric+sww" all indicate 483the same user, but additional arguments <null>, "sendmail", and "sww" 484may be provided for use in sorting mail. | 482to certain local mail programs (in particular, see 483FEATURE(`local_procmail')). For example, "eric", "eric+sendmail", and 484"eric+sww" all indicate the same user, but additional arguments <null>, 485"sendmail", and "sww" may be provided for use in sorting mail. |
| 485 486 487+----------+ 488| FEATURES | 489+----------+ 490 491Special features can be requested using the "FEATURE" macro. For 492example, the .mc line: 493 | 486 487 488+----------+ 489| FEATURES | 490+----------+ 491 492Special features can be requested using the "FEATURE" macro. For 493example, the .mc line: 494 |
| 494 FEATURE(use_cw_file) | 495 FEATURE(`use_cw_file') |
| 495 496tells sendmail that you want to have it read an /etc/sendmail.cw 497file to get values for class $=w. The FEATURE may contain a single 498optional parameter -- for example: 499 | 496 497tells sendmail that you want to have it read an /etc/sendmail.cw 498file to get values for class $=w. The FEATURE may contain a single 499optional parameter -- for example: 500 |
| 500 FEATURE(mailertable, dbm /usr/lib/mailertable) | 501 FEATURE(`mailertable', `dbm /usr/lib/mailertable') |
| 501 502The default database map type for the table features can be set with 503 504 define(`DATABASE_MAP_TYPE', `dbm') 505 506which would set it to use ndbm databases. The default is the Berkeley DB 507hash database format. Note that you must still declare a database map type 508if you specify an argument to a FEATURE. DATABASE_MAP_TYPE is only used --- 40 unchanged lines hidden (view full) --- 549 to make a distinct domain-wide namespace. Prior to 550 8.7 this was the default, and notsticky was used to 551 turn this off. 552 553mailertable Include a "mailer table" which can be used to override 554 routing for particular domains. The argument of the 555 FEATURE may be the key definition. If none is specified, 556 the definition used is: | 502 503The default database map type for the table features can be set with 504 505 define(`DATABASE_MAP_TYPE', `dbm') 506 507which would set it to use ndbm databases. The default is the Berkeley DB 508hash database format. Note that you must still declare a database map type 509if you specify an argument to a FEATURE. DATABASE_MAP_TYPE is only used --- 40 unchanged lines hidden (view full) --- 550 to make a distinct domain-wide namespace. Prior to 551 8.7 this was the default, and notsticky was used to 552 turn this off. 553 554mailertable Include a "mailer table" which can be used to override 555 routing for particular domains. The argument of the 556 FEATURE may be the key definition. If none is specified, 557 the definition used is: |
| 558 |
|
| 557 hash -o /etc/mailertable | 559 hash -o /etc/mailertable |
| 560 |
|
| 558 Keys in this database are fully qualified domain names 559 or partial domains preceded by a dot -- for example, 560 "vangogh.CS.Berkeley.EDU" or ".CS.Berkeley.EDU". 561 Values must be of the form: 562 mailer:domain 563 where "mailer" is the internal mailer name, and "domain" 564 is where to send the message. These maps are not 565 reflected into the message header. As a special case, --- 9 unchanged lines hidden (view full) --- 575 576domaintable Include a "domain table" which can be used to provide 577 domain name mapping. Use of this should really be 578 limited to your own domains. It may be useful if you 579 change names (e.g., your company changes names from 580 oldname.com to newname.com). The argument of the 581 FEATURE may be the key definition. If none is specified, 582 the definition used is: | 561 Keys in this database are fully qualified domain names 562 or partial domains preceded by a dot -- for example, 563 "vangogh.CS.Berkeley.EDU" or ".CS.Berkeley.EDU". 564 Values must be of the form: 565 mailer:domain 566 where "mailer" is the internal mailer name, and "domain" 567 is where to send the message. These maps are not 568 reflected into the message header. As a special case, --- 9 unchanged lines hidden (view full) --- 578 579domaintable Include a "domain table" which can be used to provide 580 domain name mapping. Use of this should really be 581 limited to your own domains. It may be useful if you 582 change names (e.g., your company changes names from 583 oldname.com to newname.com). The argument of the 584 FEATURE may be the key definition. If none is specified, 585 the definition used is: |
| 586 |
|
| 583 hash -o /etc/domaintable | 587 hash -o /etc/domaintable |
| 588 |
|
| 584 The key in this table is the domain name; the value is 585 the new (fully qualified) domain. Anything in the 586 domaintable is reflected into headers; that is, this 587 is done in ruleset 3. 588 589bitdomain Look up bitnet hosts in a table to try to turn them into 590 internet addresses. The table can be built using the 591 bitdomain program contributed by John Gardiner Myers. 592 The argument of the FEATURE may be the key definition; if 593 none is specified, the definition used is: | 589 The key in this table is the domain name; the value is 590 the new (fully qualified) domain. Anything in the 591 domaintable is reflected into headers; that is, this 592 is done in ruleset 3. 593 594bitdomain Look up bitnet hosts in a table to try to turn them into 595 internet addresses. The table can be built using the 596 bitdomain program contributed by John Gardiner Myers. 597 The argument of the FEATURE may be the key definition; if 598 none is specified, the definition used is: |
| 599 |
|
| 594 hash -o /etc/bitdomain.db | 600 hash -o /etc/bitdomain.db |
| 601 |
|
| 595 Keys are the bitnet hostname; values are the corresponding 596 internet hostname. 597 598uucpdomain Similar feature for UUCP hosts. The default map definition 599 is: | 602 Keys are the bitnet hostname; values are the corresponding 603 internet hostname. 604 605uucpdomain Similar feature for UUCP hosts. The default map definition 606 is: |
| 607 |
|
| 600 hash -o /etc/uudomain.db | 608 hash -o /etc/uudomain.db |
| 609 |
|
| 601 At the moment there is no automagic tool to build this 602 database. 603 604always_add_domain 605 Include the local host domain even on locally delivered 606 mail. Normally it is not added on unqualified names. 607 However, if you use a shared message store but do not use 608 the same user name space everywhere, you may need the host --- 45 unchanged lines hidden (view full) --- 654 addresses as for masquerading are looked up, i.e. only header 655 sender addresses unless the allmasquerade and/or 656 masquerade_envelope features are given. Qualified addresses 657 must have the domain part in the list of names given by the 658 by the macros GENERICS_DOMAIN or GENERICS_DOMAIN_FILE 659 (analogously to MASQUERADE_DOMAIN and MASQUERADE_DOMAIN_FILE, 660 see below). 661 | 610 At the moment there is no automagic tool to build this 611 database. 612 613always_add_domain 614 Include the local host domain even on locally delivered 615 mail. Normally it is not added on unqualified names. 616 However, if you use a shared message store but do not use 617 the same user name space everywhere, you may need the host --- 45 unchanged lines hidden (view full) --- 663 addresses as for masquerading are looked up, i.e. only header 664 sender addresses unless the allmasquerade and/or 665 masquerade_envelope features are given. Qualified addresses 666 must have the domain part in the list of names given by the 667 by the macros GENERICS_DOMAIN or GENERICS_DOMAIN_FILE 668 (analogously to MASQUERADE_DOMAIN and MASQUERADE_DOMAIN_FILE, 669 see below). 670 |
| 662 The argument of FEATURE(genericstable) may be the map | 671 The argument of FEATURE(`genericstable') may be the map |
| 663 definition; the default map definition is: 664 665 hash -o /etc/genericstable 666 667 The key for this table is either the full address or the 668 unqualified username (the former is tried first); the 669 value is the new user address. If the new user address does 670 not include a domain, it will be qualified in the standard 671 manner, i.e. using $j or the masquerade name. Note that the 672 address being looked up must be fully qualified. For local | 672 definition; the default map definition is: 673 674 hash -o /etc/genericstable 675 676 The key for this table is either the full address or the 677 unqualified username (the former is tried first); the 678 value is the new user address. If the new user address does 679 not include a domain, it will be qualified in the standard 680 manner, i.e. using $j or the masquerade name. Note that the 681 address being looked up must be fully qualified. For local |
| 673 mail, it is necessary to use FEATURE(always_add_domain) for 674 the addresses to be qualified. | 682 mail, it is necessary to use FEATURE(`always_add_domain') 683 for the addresses to be qualified. |
| 675 676virtusertable A domain-specific form of aliasing, allowing multiple 677 virtual domains to be hosted on one machine. For example, 678 if the virtuser table contained: 679 680 info@foo.com foo-info 681 info@bar.com bar-info 682 @baz.org jane@elsewhere.net --- 11 unchanged lines hidden (view full) --- 694 All the host names on the left hand side (foo.com, bar.com, 695 and baz.org) must be in $=w. The default map definition is: 696 697 hash -o /etc/virtusertable 698 699 A new definition can be specified as the second argument of 700 the FEATURE macro, such as 701 | 684 685virtusertable A domain-specific form of aliasing, allowing multiple 686 virtual domains to be hosted on one machine. For example, 687 if the virtuser table contained: 688 689 info@foo.com foo-info 690 info@bar.com bar-info 691 @baz.org jane@elsewhere.net --- 11 unchanged lines hidden (view full) --- 703 All the host names on the left hand side (foo.com, bar.com, 704 and baz.org) must be in $=w. The default map definition is: 705 706 hash -o /etc/virtusertable 707 708 A new definition can be specified as the second argument of 709 the FEATURE macro, such as 710 |
| 702 FEATURE(virtusertable, dbm -o /etc/mail/virtusers) | 711 FEATURE(`virtusertable', `dbm -o /etc/mail/virtusers') |
| 703 704nodns We aren't running DNS at our site (for example, 705 we are UUCP-only connected). It's hard to consider 706 this a "feature", but hey, it had to go somewhere. 707 Actually, as of 8.7 this is a no-op -- remove "dns" from 708 the hosts service switch entry instead. 709 710nullclient This is a special case -- it creates a stripped down --- 77 unchanged lines hidden (view full) --- 788 Turns on the ability to allow relaying based on the MX 789 records of the host portion of an incoming recipient; that 790 is, if an MX record for host foo.com points to your site, 791 you will accept and relay mail addressed to foo.com. See 792 description below for more information before using this 793 feature. Also, see the KNOWNBUGS entry regarding bestmx 794 map lookups. 795 | 712 713nodns We aren't running DNS at our site (for example, 714 we are UUCP-only connected). It's hard to consider 715 this a "feature", but hey, it had to go somewhere. 716 Actually, as of 8.7 this is a no-op -- remove "dns" from 717 the hosts service switch entry instead. 718 719nullclient This is a special case -- it creates a stripped down --- 77 unchanged lines hidden (view full) --- 797 Turns on the ability to allow relaying based on the MX 798 records of the host portion of an incoming recipient; that 799 is, if an MX record for host foo.com points to your site, 800 you will accept and relay mail addressed to foo.com. See 801 description below for more information before using this 802 feature. Also, see the KNOWNBUGS entry regarding bestmx 803 map lookups. 804 |
| 796 FEATURE(relay_based_on_MX) does not necessarily allow | 805 FEATURE(`relay_based_on_MX') does not necessarily allow |
| 797 routing of these messages which you expect to be allowed, 798 if route address syntax (or %-hack syntax) is used. If 799 this is a problem, add entries to the access-table or use | 806 routing of these messages which you expect to be allowed, 807 if route address syntax (or %-hack syntax) is used. If 808 this is a problem, add entries to the access-table or use |
| 800 FEATURE(loose_relay_check). | 809 FEATURE(`loose_relay_check'). |
| 801 802relay_local_from 803 Allows relaying if the domain portion of the mail sender 804 is a local host. This should only be used if absolutely 805 necessary as it opens a window for spammers. Specifically, 806 they can send mail to your mail server that claims to be 807 from your domain (either directly or via a routed address), 808 and you will go ahead and relay it out to arbitrary hosts --- 14 unchanged lines hidden (view full) --- 823 inside a firewall that has only a limited view of the 824 Internet host name space, this could cause problems. In this 825 case you probably want to use this feature to accept all 826 domains on input, even if they are unresolvable. 827 828access_db Turns on the access database feature. The access db gives 829 you the ability to allow or refuse to accept mail from 830 specified domains for administrative reasons. By default, | 810 811relay_local_from 812 Allows relaying if the domain portion of the mail sender 813 is a local host. This should only be used if absolutely 814 necessary as it opens a window for spammers. Specifically, 815 they can send mail to your mail server that claims to be 816 from your domain (either directly or via a routed address), 817 and you will go ahead and relay it out to arbitrary hosts --- 14 unchanged lines hidden (view full) --- 832 inside a firewall that has only a limited view of the 833 Internet host name space, this could cause problems. In this 834 case you probably want to use this feature to accept all 835 domains on input, even if they are unresolvable. 836 837access_db Turns on the access database feature. The access db gives 838 you the ability to allow or refuse to accept mail from 839 specified domains for administrative reasons. By default, |
| 831 the access database specification is 832 ``hash -o /etc/mail/access''. The format of the 833 database is described below. | 840 the access database specification is: |
| 834 | 841 |
| 842 hash -o /etc/mail/access 843 844 The format of the database is described below. 845 |
|
| 835blacklist_recipients 836 Turns on the ability to block incoming mail for certain 837 recipient usernames, hostnames, or addresses. For 838 example, you can block incoming mail to user nobody, 839 host foo.mydomain.com, or guest@bar.mydomain.com. 840 These specifications are put in the access db as 841 described below. 842 --- 40 unchanged lines hidden (view full) --- 883lists of UUCP hosts they speak with directly. This can get a bit more 884tricky. For an example of a "complex" site, see cf/ucbvax.mc. 885 886If your host is known by several different names, you need to augment 887the $=w class. This is a list of names by which you are known, and 888anything sent to an address using a host name in this list will be 889treated as local mail. You can do this in two ways: either create 890the file /etc/sendmail.cw containing a list of your aliases (one per | 846blacklist_recipients 847 Turns on the ability to block incoming mail for certain 848 recipient usernames, hostnames, or addresses. For 849 example, you can block incoming mail to user nobody, 850 host foo.mydomain.com, or guest@bar.mydomain.com. 851 These specifications are put in the access db as 852 described below. 853 --- 40 unchanged lines hidden (view full) --- 894lists of UUCP hosts they speak with directly. This can get a bit more 895tricky. For an example of a "complex" site, see cf/ucbvax.mc. 896 897If your host is known by several different names, you need to augment 898the $=w class. This is a list of names by which you are known, and 899anything sent to an address using a host name in this list will be 900treated as local mail. You can do this in two ways: either create 901the file /etc/sendmail.cw containing a list of your aliases (one per |
| 891line), and use ``FEATURE(use_cw_file)'' in the .mc file, or add the | 902line), and use ``FEATURE(`use_cw_file')'' in the .mc file, or add the |
| 892line: 893 894 Cw alias.host.name 895 896at the end of that file. See the ``vangogh.mc'' file for an example. 897Be sure you use the fully-qualified name of the host, rather than a 898short name. 899 --- 209 unchanged lines hidden (view full) --- 1109 1110 MASQUERADE_DOMAIN_FILE(filename) 1111 1112to read the list of names from the indicated file. 1113 1114Normally only header addresses are masqueraded. If you want to 1115masquerade the envelope as well, use 1116 | 903line: 904 905 Cw alias.host.name 906 907at the end of that file. See the ``vangogh.mc'' file for an example. 908Be sure you use the fully-qualified name of the host, rather than a 909short name. 910 --- 209 unchanged lines hidden (view full) --- 1120 1121 MASQUERADE_DOMAIN_FILE(filename) 1122 1123to read the list of names from the indicated file. 1124 1125Normally only header addresses are masqueraded. If you want to 1126masquerade the envelope as well, use 1127 |
| 1117 FEATURE(masquerade_envelope) | 1128 FEATURE(`masquerade_envelope') |
| 1118 1119There are always users that need to be "exposed" -- that is, their 1120internal site name should be displayed instead of the masquerade name. 1121Root is an example. You can add users to this list using 1122 1123 EXPOSED_USER(usernames) 1124 1125This adds users to class E; you could also use something like 1126 1127 FE/etc/sendmail.cE 1128 1129You can also arrange to relay all unqualified names (that is, names 1130without @host) to a relay host. For example, if you have a central 1131email server, you might relay to that host so that users don't have 1132to have .forward files or aliases. You can do this using 1133 | 1129 1130There are always users that need to be "exposed" -- that is, their 1131internal site name should be displayed instead of the masquerade name. 1132Root is an example. You can add users to this list using 1133 1134 EXPOSED_USER(usernames) 1135 1136This adds users to class E; you could also use something like 1137 1138 FE/etc/sendmail.cE 1139 1140You can also arrange to relay all unqualified names (that is, names 1141without @host) to a relay host. For example, if you have a central 1142email server, you might relay to that host so that users don't have 1143to have .forward files or aliases. You can do this using 1144 |
| 1134 define(`LOCAL_RELAY', mailer:hostname) | 1145 define(`LOCAL_RELAY', `mailer:hostname') |
| 1135 1136The ``mailer:'' can be omitted, in which case the mailer defaults to 1137"relay". There are some user names that you don't want relayed, perhaps 1138because of local aliases. A common example is root, which may be 1139locally aliased. You can add entries to this list using 1140 1141 LOCAL_USER(usernames) 1142 1143This adds users to class L; you could also use something like 1144 1145 FL/etc/sendmail.cL 1146 1147If you want all incoming mail sent to a centralized hub, as for a 1148shared /var/spool/mail scheme, use 1149 | 1146 1147The ``mailer:'' can be omitted, in which case the mailer defaults to 1148"relay". There are some user names that you don't want relayed, perhaps 1149because of local aliases. A common example is root, which may be 1150locally aliased. You can add entries to this list using 1151 1152 LOCAL_USER(usernames) 1153 1154This adds users to class L; you could also use something like 1155 1156 FL/etc/sendmail.cL 1157 1158If you want all incoming mail sent to a centralized hub, as for a 1159shared /var/spool/mail scheme, use 1160 |
| 1150 define(`MAIL_HUB', mailer:hostname) | 1161 define(`MAIL_HUB', `mailer:hostname') |
| 1151 1152Again, ``mailer:'' defaults to "relay". If you define both LOCAL_RELAY | 1162 1163Again, ``mailer:'' defaults to "relay". If you define both LOCAL_RELAY |
| 1153and MAIL_HUB _AND_ you have FEATURE(stickyhost), unqualified names will | 1164and MAIL_HUB _AND_ you have FEATURE(`stickyhost'), unqualified names will |
| 1154be sent to the LOCAL_RELAY and other local names will be sent to MAIL_HUB. 1155Names in $=L will be delivered locally, so you MUST have aliases or 1156.forward files for them. 1157 1158For example, if you are on machine mastodon.CS.Berkeley.EDU and you have | 1165be sent to the LOCAL_RELAY and other local names will be sent to MAIL_HUB. 1166Names in $=L will be delivered locally, so you MUST have aliases or 1167.forward files for them. 1168 1169For example, if you are on machine mastodon.CS.Berkeley.EDU and you have |
| 1159FEATURE(stickyhost), the following combinations of settings will have the | 1170FEATURE(`stickyhost'), the following combinations of settings will have the |
| 1160indicated effects: 1161 1162email sent to.... eric eric@mastodon.CS.Berkeley.EDU 1163 1164LOCAL_RELAY set to mail.CS.Berkeley.EDU (delivered locally) 1165mail.CS.Berkeley.EDU (no local aliasing) (aliasing done) 1166 1167MAIL_HUB set to mammoth.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU 1168mammoth.CS.Berkeley.EDU (aliasing done) (aliasing done) 1169 1170Both LOCAL_RELAY and mail.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU 1171MAIL_HUB set as above (no local aliasing) (aliasing done) 1172 | 1171indicated effects: 1172 1173email sent to.... eric eric@mastodon.CS.Berkeley.EDU 1174 1175LOCAL_RELAY set to mail.CS.Berkeley.EDU (delivered locally) 1176mail.CS.Berkeley.EDU (no local aliasing) (aliasing done) 1177 1178MAIL_HUB set to mammoth.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU 1179mammoth.CS.Berkeley.EDU (aliasing done) (aliasing done) 1180 1181Both LOCAL_RELAY and mail.CS.Berkeley.EDU mammoth.CS.Berkeley.EDU 1182MAIL_HUB set as above (no local aliasing) (aliasing done) 1183 |
| 1173If you do not have FEATURE(stickyhost) set, then LOCAL_RELAY and | 1184If you do not have FEATURE(`stickyhost') set, then LOCAL_RELAY and |
| 1174MAIL_HUB act identically, with MAIL_HUB taking precedence. 1175 1176If you want all outgoing mail to go to a central relay site, define 1177SMART_HOST as well. Briefly: 1178 1179 LOCAL_RELAY applies to unqualified names (e.g., "eric"). 1180 MAIL_HUB applies to names qualified with the name of the 1181 local host (e.g., "eric@mastodon.CS.Berkeley.EDU"). --- 22 unchanged lines hidden (view full) --- 1204* Better checking on sender information. 1205* Access database. 1206* Header checks. 1207 1208Relaying (transmission of messages from a site outside your domain to 1209another site outside your domain) is denied by default. Note that 1210this changed in sendmail 8.9; previous versions allowed relaying by 1211default. If you want to revert to the old behaviour, you will need | 1185MAIL_HUB act identically, with MAIL_HUB taking precedence. 1186 1187If you want all outgoing mail to go to a central relay site, define 1188SMART_HOST as well. Briefly: 1189 1190 LOCAL_RELAY applies to unqualified names (e.g., "eric"). 1191 MAIL_HUB applies to names qualified with the name of the 1192 local host (e.g., "eric@mastodon.CS.Berkeley.EDU"). --- 22 unchanged lines hidden (view full) --- 1215* Better checking on sender information. 1216* Access database. 1217* Header checks. 1218 1219Relaying (transmission of messages from a site outside your domain to 1220another site outside your domain) is denied by default. Note that 1221this changed in sendmail 8.9; previous versions allowed relaying by 1222default. If you want to revert to the old behaviour, you will need |
| 1212to use FEATURE(promiscuous_relay). You can allow certain domains to | 1223to use FEATURE(`promiscuous_relay'). You can allow certain domains to |
| 1213relay through your server by adding their domain name or IP address to 1214class 'R' ($=R) using RELAY_DOMAIN() and RELAY_DOMAIN_FILE() or via the 1215access database (described below). 1216 1217If you use 1218 | 1224relay through your server by adding their domain name or IP address to 1225class 'R' ($=R) using RELAY_DOMAIN() and RELAY_DOMAIN_FILE() or via the 1226access database (described below). 1227 1228If you use 1229 |
| 1219 FEATURE(relay_entire_domain) | 1230 FEATURE(`relay_entire_domain') |
| 1220 1221then any host in any of your local domains (that is, the $=m class) 1222will be relayed (that is, you will accept mail either to or from any 1223host in your domain). 1224 1225You can also allow relaying based on the MX records of the host 1226portion of an incoming recipient address by using 1227 | 1231 1232then any host in any of your local domains (that is, the $=m class) 1233will be relayed (that is, you will accept mail either to or from any 1234host in your domain). 1235 1236You can also allow relaying based on the MX records of the host 1237portion of an incoming recipient address by using 1238 |
| 1228 FEATURE(relay_based_on_MX) | 1239 FEATURE(`relay_based_on_MX') |
| 1229 1230For example, if your server receives a recipient of user@domain.com 1231and domain.com lists your server in its MX records, the mail will be 1232accepted for relay to domain.com. Note that this will stop spammers 1233from using your host to relay spam but it will not stop outsiders from 1234using your server as a relay for their site (that is, they set up an 1235MX record pointing to your mail server, and you will relay mail addressed 1236to them without any prior arrangement). Along the same lines, 1237 | 1240 1241For example, if your server receives a recipient of user@domain.com 1242and domain.com lists your server in its MX records, the mail will be 1243accepted for relay to domain.com. Note that this will stop spammers 1244from using your host to relay spam but it will not stop outsiders from 1245using your server as a relay for their site (that is, they set up an 1246MX record pointing to your mail server, and you will relay mail addressed 1247to them without any prior arrangement). Along the same lines, 1248 |
| 1238 FEATURE(relay_local_from) | 1249 FEATURE(`relay_local_from') |
| 1239 1240will allow relaying if the sender specifies a return path (i.e. 1241MAIL FROM: <user@domain>) domain which is a local domain. This a 1242dangerous feature as it will allow spammers to spam using your mail 1243server by simply specifying a return address of user@your.domain.com. 1244It should not be used unless absolutely necessary. 1245 1246If source routing is used in the recipient address (i.e. 1247RCPT TO: <user%site.com@othersite.com>), sendmail will check 1248user@site.com for relaying if othersite.com is an allowed relay host | 1250 1251will allow relaying if the sender specifies a return path (i.e. 1252MAIL FROM: <user@domain>) domain which is a local domain. This a 1253dangerous feature as it will allow spammers to spam using your mail 1254server by simply specifying a return address of user@your.domain.com. 1255It should not be used unless absolutely necessary. 1256 1257If source routing is used in the recipient address (i.e. 1258RCPT TO: <user%site.com@othersite.com>), sendmail will check 1259user@site.com for relaying if othersite.com is an allowed relay host |
| 1249in either class 'R', class 'm' if FEATURE(relay_entire_domain) is used, 1250or the access database if FEATURE(access_db) is used. To prevent | 1260in either class 'R', class 'm' if FEATURE(`relay_entire_domain') is used, 1261or the access database if FEATURE(`access_db') is used. To prevent |
| 1251the address from being stripped down, use: 1252 | 1262the address from being stripped down, use: 1263 |
| 1253 FEATURE(loose_relay_check) | 1264 FEATURE(`loose_relay_check') |
| 1254 1255If you think you need to use this feature, you probably do not. This 1256should only be used for sites which have no control over the addresses 1257that they provide a gateway for. Use this FEATURE with caution as it 1258can allow spammers to relay through your server if not setup properly. 1259 1260As of 8.9, sendmail will refuse mail if the MAIL FROM: parameter has 1261an unresolvable domain (i.e., one that DNS, your local name service, 1262or special case rules in ruleset 3 cannot locate). If you want to 1263continue to accept such domains, e.g. because you are inside a 1264firewall that has only a limited view of the Internet host name space 1265(note that you will not be able to return mail to them unless you have 1266some "smart host" forwarder), use 1267 | 1265 1266If you think you need to use this feature, you probably do not. This 1267should only be used for sites which have no control over the addresses 1268that they provide a gateway for. Use this FEATURE with caution as it 1269can allow spammers to relay through your server if not setup properly. 1270 1271As of 8.9, sendmail will refuse mail if the MAIL FROM: parameter has 1272an unresolvable domain (i.e., one that DNS, your local name service, 1273or special case rules in ruleset 3 cannot locate). If you want to 1274continue to accept such domains, e.g. because you are inside a 1275firewall that has only a limited view of the Internet host name space 1276(note that you will not be able to return mail to them unless you have 1277some "smart host" forwarder), use 1278 |
| 1268 FEATURE(accept_unresolvable_domains) | 1279 FEATURE(`accept_unresolvable_domains') |
| 1269 1270sendmail will also refuse mail if the MAIL FROM: parameter is not 1271fully qualified (i.e., contains a domain as well as a user). If you 1272want to continue to accept such senders, use 1273 | 1280 1281sendmail will also refuse mail if the MAIL FROM: parameter is not 1282fully qualified (i.e., contains a domain as well as a user). If you 1283want to continue to accept such senders, use 1284 |
| 1274 FEATURE(accept_unqualified_senders) | 1285 FEATURE(`accept_unqualified_senders') |
| 1275 1276An ``access'' database can be created to accept or reject mail from 1277selected domains. For example, you may choose to reject all mail 1278originating from known spammers. To enable such a database, use 1279 | 1286 1287An ``access'' database can be created to accept or reject mail from 1288selected domains. For example, you may choose to reject all mail 1289originating from known spammers. To enable such a database, use 1290 |
| 1280 FEATURE(access_db) | 1291 FEATURE(`access_db') |
| 1281 1282The FEATURE macro can accept a second parameter giving the key file 1283definition for the database; for example 1284 | 1292 1293The FEATURE macro can accept a second parameter giving the key file 1294definition for the database; for example 1295 |
| 1285 FEATURE(access_db, hash -o /etc/mail/access) | 1296 FEATURE(`access_db', `hash -o /etc/mail/access') |
| 1286 1287Remember, since /etc/mail/access is a database, after creating the text 1288file as described below, you must use makemap to create the database 1289map. For example: 1290 | 1297 1298Remember, since /etc/mail/access is a database, after creating the text 1299file as described below, you must use makemap to create the database 1300map. For example: 1301 |
| 1291makemap hash /etc/mail/access < /etc/mail/access | 1302 makemap hash /etc/mail/access < /etc/mail/access |
| 1292 1293The table itself uses e-mail addresses, domain names, and network 1294numbers as keys. For example, 1295 1296 spammer@aol.com REJECT 1297 cyberspammer.com REJECT 1298 192.168.212 REJECT 1299 --- 30 unchanged lines hidden (view full) --- 1330 1331would accept mail from okay.cyberspammer.com, but would reject mail 1332from all other hosts at cyberspammer.com with the indicated message. 1333It would allow accept mail from any hosts in the sendmail.org domain, 1334and allow relaying for the 128.32.*.* network. Note, UUCP users may 1335need to add hostname.UUCP to the access database or class 'R' ($=R). 1336If you also use: 1337 | 1303 1304The table itself uses e-mail addresses, domain names, and network 1305numbers as keys. For example, 1306 1307 spammer@aol.com REJECT 1308 cyberspammer.com REJECT 1309 192.168.212 REJECT 1310 --- 30 unchanged lines hidden (view full) --- 1341 1342would accept mail from okay.cyberspammer.com, but would reject mail 1343from all other hosts at cyberspammer.com with the indicated message. 1344It would allow accept mail from any hosts in the sendmail.org domain, 1345and allow relaying for the 128.32.*.* network. Note, UUCP users may 1346need to add hostname.UUCP to the access database or class 'R' ($=R). 1347If you also use: 1348 |
| 1338 FEATURE(relay_hosts_only) | 1349 FEATURE(`relay_hosts_only') |
| 1339 1340then the above example will allow relaying for sendmail.org, but not 1341hosts within the sendmail.org domain. Note that this will also require 1342hosts listed in class 'R' ($=R) to be fully qualified host names. 1343 1344You can also use the access database to block sender addresses based on 1345the username portion of the address. For example: 1346 1347 FREE.STEALTH.MAILER@ 550 Spam not accepted 1348 1349Note that you must include the @ after the username to signify that 1350this database entry is for checking only the username portion of the 1351sender address. 1352 1353If you use: 1354 | 1350 1351then the above example will allow relaying for sendmail.org, but not 1352hosts within the sendmail.org domain. Note that this will also require 1353hosts listed in class 'R' ($=R) to be fully qualified host names. 1354 1355You can also use the access database to block sender addresses based on 1356the username portion of the address. For example: 1357 1358 FREE.STEALTH.MAILER@ 550 Spam not accepted 1359 1360Note that you must include the @ after the username to signify that 1361this database entry is for checking only the username portion of the 1362sender address. 1363 1364If you use: 1365 |
| 1355 FEATURE(blacklist_recipients) | 1366 FEATURE(`blacklist_recipients') |
| 1356 1357then you can add entries to the map for local users, hosts in your 1358domains, or addresses in your domain which should not receive mail: 1359 1360 badlocaluser 550 Mailbox disabled for this username 1361 host.mydomain.com 550 That host does not accept mail 1362 user@otherhost.mydomain.com 550 Mailbox disabled for this recipient 1363 --- 8 unchanged lines hidden (view full) --- 1372 cyberspammer.com REJECT 1373 1374Mail can't be sent to spammer@aol.com or anyone at cyberspammer.com. 1375 1376There is also a ``Realtime Blackhole List'' run by the MAPS project 1377at http://maps.vix.com/. This is a database maintained in DNS of 1378spammers. To use this database, use 1379 | 1367 1368then you can add entries to the map for local users, hosts in your 1369domains, or addresses in your domain which should not receive mail: 1370 1371 badlocaluser 550 Mailbox disabled for this username 1372 host.mydomain.com 550 That host does not accept mail 1373 user@otherhost.mydomain.com 550 Mailbox disabled for this recipient 1374 --- 8 unchanged lines hidden (view full) --- 1383 cyberspammer.com REJECT 1384 1385Mail can't be sent to spammer@aol.com or anyone at cyberspammer.com. 1386 1387There is also a ``Realtime Blackhole List'' run by the MAPS project 1388at http://maps.vix.com/. This is a database maintained in DNS of 1389spammers. To use this database, use 1390 |
| 1380 FEATURE(rbl) | 1391 FEATURE(`rbl') |
| 1381 1382This will cause sendmail to reject mail from any site in the 1383Realtime Blackhole List database. You can specify an alternative 1384RBL name server to contact by specifying an argument to the FEATURE. 1385 1386The features described above make use of the check_relay, check_mail, 1387and check_rcpt rulesets. If you wish to include your own checks, 1388you can put your checks in the rulesets Local_check_relay, --- 26 unchanged lines hidden (view full) --- 1415 1416 LOCAL_RULESETS 1417 HMessage-Id: $>CheckMessageId 1418 1419 SCheckMessageId 1420 R< $+ @ $+ > $@ OK 1421 R$* $#error $: 553 Header Error 1422 | 1392 1393This will cause sendmail to reject mail from any site in the 1394Realtime Blackhole List database. You can specify an alternative 1395RBL name server to contact by specifying an argument to the FEATURE. 1396 1397The features described above make use of the check_relay, check_mail, 1398and check_rcpt rulesets. If you wish to include your own checks, 1399you can put your checks in the rulesets Local_check_relay, --- 26 unchanged lines hidden (view full) --- 1426 1427 LOCAL_RULESETS 1428 HMessage-Id: $>CheckMessageId 1429 1430 SCheckMessageId 1431 R< $+ @ $+ > $@ OK 1432 R$* $#error $: 553 Header Error 1433 |
| 1423Users of FEATURE(nullclient) who desire to use the anti-spam and 1424anti-relaying capabilities should replace FEATURE(nullclient, mailhub) | 1434Users of FEATURE(`nullclient') who desire to use the anti-spam and 1435anti-relaying capabilities should replace FEATURE(`nullclient', `mailhub') |
| 1425with: 1426 1427 undefine(`ALIAS_FILE') 1428 define(`MAIL_HUB', `mailhub') 1429 define(`SMART_HOST', `mailhub') 1430 define(`confFORWARD_PATH', `') 1431 1432where mailhub is the fully qualified hostname for their mail server. | 1436with: 1437 1438 undefine(`ALIAS_FILE') 1439 define(`MAIL_HUB', `mailhub') 1440 define(`SMART_HOST', `mailhub') 1441 define(`confFORWARD_PATH', `') 1442 1443where mailhub is the fully qualified hostname for their mail server. |
| 1444The above rules will provide the relaying to the mailhub without local 1445alias and forward file expansion. To match the other behavior of 1446FEATURE(`nullclient'), you should also add these lines along with those 1447listed above: |
|
| 1433 | 1448 |
| 1449 MASQUERADE_AS(`mailhub') 1450 FEATURE(`allmasquerade') 1451 FEATURE(`masquerade_envelope') |
|
| 1434 | 1452 |
| 1453 |
|
| 1435+--------------------------------+ 1436| ADDING NEW MAILERS OR RULESETS | 1437+--------------------------------+ 1438 1439Sometimes you may need to add entirely new mailers or rulesets. They 1440should be introduced with the constructs MAILER_DEFINITIONS and 1441LOCAL_RULESETS respectively. For example: 1442 --- 14 unchanged lines hidden (view full) --- 1457sites. I don't pretend that they are well tuned for UUCP-only or 1458UUCP-primarily nodes (the latter is defined as a small local net 1459connected to the rest of the world via UUCP). However, there is one 1460hook to handle some special cases. 1461 1462You can define a ``smart host'' that understands a richer address syntax 1463using: 1464 | 1454+--------------------------------+ 1455| ADDING NEW MAILERS OR RULESETS | 1456+--------------------------------+ 1457 1458Sometimes you may need to add entirely new mailers or rulesets. They 1459should be introduced with the constructs MAILER_DEFINITIONS and 1460LOCAL_RULESETS respectively. For example: 1461 --- 14 unchanged lines hidden (view full) --- 1476sites. I don't pretend that they are well tuned for UUCP-only or 1477UUCP-primarily nodes (the latter is defined as a small local net 1478connected to the rest of the world via UUCP). However, there is one 1479hook to handle some special cases. 1480 1481You can define a ``smart host'' that understands a richer address syntax 1482using: 1483 |
| 1465 define(`SMART_HOST', mailer:hostname) | 1484 define(`SMART_HOST', `mailer:hostname') |
| 1466 1467In this case, the ``mailer:'' defaults to "relay". Any messages that 1468can't be handled using the usual UUCP rules are passed to this host. 1469 1470If you are on a local SMTP-based net that connects to the outside 1471world via UUCP, you can use LOCAL_NET_CONFIG to add appropriate rules. 1472For example: 1473 | 1485 1486In this case, the ``mailer:'' defaults to "relay". Any messages that 1487can't be handled using the usual UUCP rules are passed to this host. 1488 1489If you are on a local SMTP-based net that connects to the outside 1490world via UUCP, you can use LOCAL_NET_CONFIG to add appropriate rules. 1491For example: 1492 |
| 1474 define(`SMART_HOST', suucp:uunet) | 1493 define(`SMART_HOST', `suucp:uunet') |
| 1475 LOCAL_NET_CONFIG 1476 R$* < @ $* .$m. > $* $#smtp $@ $2.$m. $: $1 < @ $2.$m. > $3 1477 1478This will cause all names that end in your domain name ($m) via 1479SMTP; anything else will be sent via suucp (smart UUCP) to uunet. | 1494 LOCAL_NET_CONFIG 1495 R$* < @ $* .$m. > $* $#smtp $@ $2.$m. $: $1 < @ $2.$m. > $3 1496 1497This will cause all names that end in your domain name ($m) via 1498SMTP; anything else will be sent via suucp (smart UUCP) to uunet. |
| 1480If you have FEATURE(nocanonify), you may need to omit the dots after | 1499If you have FEATURE(`nocanonify'), you may need to omit the dots after |
| 1481the $m. If you are running a local DNS inside your domain which is 1482not otherwise connected to the outside world, you probably want to 1483use: 1484 | 1500the $m. If you are running a local DNS inside your domain which is 1501not otherwise connected to the outside world, you probably want to 1502use: 1503 |
| 1485 define(`SMART_HOST', smtp:fire.wall.com) | 1504 define(`SMART_HOST', `smtp:fire.wall.com') |
| 1486 LOCAL_NET_CONFIG 1487 R$* < @ $* . > $* $#smtp $@ $2. $: $1 < @ $2. > $3 1488 1489That is, send directly only to things you found in your DNS lookup; 1490anything else goes through SMART_HOST. 1491 1492You may need to turn off the anti-spam rules in order to accept | 1505 LOCAL_NET_CONFIG 1506 R$* < @ $* . > $* $#smtp $@ $2. $: $1 < @ $2. > $3 1507 1508That is, send directly only to things you found in your DNS lookup; 1509anything else goes through SMART_HOST. 1510 1511You may need to turn off the anti-spam rules in order to accept |
| 1493UUCP mail with FEATURE(promiscuous_relay) and 1494FEATURE(accept_unresolvable_domains). | 1512UUCP mail with FEATURE(`promiscuous_relay') and 1513FEATURE(`accept_unresolvable_domains'). |
| 1495 1496 1497+-----------+ 1498| WHO AM I? | 1499+-----------+ 1500 1501Normally, the $j macro is automatically defined to be your fully 1502qualified domain name (FQDN). Sendmail does this by getting your --- 8 unchanged lines hidden (view full) --- 1511 Dmbar.com 1512 define(`confDOMAIN_NAME', `$w.$m')dnl 1513 1514 1515+--------------------+ 1516| USING MAILERTABLES | 1517+--------------------+ 1518 | 1514 1515 1516+-----------+ 1517| WHO AM I? | 1518+-----------+ 1519 1520Normally, the $j macro is automatically defined to be your fully 1521qualified domain name (FQDN). Sendmail does this by getting your --- 8 unchanged lines hidden (view full) --- 1530 Dmbar.com 1531 define(`confDOMAIN_NAME', `$w.$m')dnl 1532 1533 1534+--------------------+ 1535| USING MAILERTABLES | 1536+--------------------+ 1537 |
| 1519To use FEATURE(mailertable), you will have to create an external | 1538To use FEATURE(`mailertable'), you will have to create an external |
| 1520database containing the routing information for various domains. 1521For example, a mailertable file in text format might be: 1522 1523 .my.domain xnet:%1.my.domain 1524 uuhost1.my.domain suucp:uuhost1 1525 .bitnet smtp:relay.bit.net 1526 1527This should normally be stored in /etc/mailertable. The actual --- 42 unchanged lines hidden (view full) --- 1570The user database was not originally intended for mapping full names 1571to login names (e.g., Eric.Allman => eric), but some people are using 1572it that way. (I would recommend that you set up aliases for this 1573purpose instead -- since you can specify multiple alias files, this 1574is fairly easy.) The intent was to locate the default maildrop at 1575a site, but allow you to override this by sending to a specific host. 1576 1577If you decide to set up the user database in this fashion, it is | 1539database containing the routing information for various domains. 1540For example, a mailertable file in text format might be: 1541 1542 .my.domain xnet:%1.my.domain 1543 uuhost1.my.domain suucp:uuhost1 1544 .bitnet smtp:relay.bit.net 1545 1546This should normally be stored in /etc/mailertable. The actual --- 42 unchanged lines hidden (view full) --- 1589The user database was not originally intended for mapping full names 1590to login names (e.g., Eric.Allman => eric), but some people are using 1591it that way. (I would recommend that you set up aliases for this 1592purpose instead -- since you can specify multiple alias files, this 1593is fairly easy.) The intent was to locate the default maildrop at 1594a site, but allow you to override this by sending to a specific host. 1595 1596If you decide to set up the user database in this fashion, it is |
| 1578imperative that you not use FEATURE(stickyhost) -- otherwise, | 1597imperative that you not use FEATURE(`stickyhost') -- otherwise, |
| 1579e-mail sent to Full.Name@local.host.name will be rejected. 1580 1581To build the internal form of the user database, use: 1582 1583 makemap btree /usr/data/base.db < /usr/data/base.txt 1584 1585As a general rule, I am adamantly opposed to using full names as 1586e-mail addresses, since they are not in any sense unique. For example, --- 123 unchanged lines hidden (view full) --- 1710 (trusted users) class. 1711confCR_FILE FR class [/etc/mail/relay-domains] Name of 1712 file used to get the local additions 1713 to the $=R (hosts allowed to relay) 1714 class. 1715confTRUSTED_USERS Ct class [no default] Names of users to add to 1716 the list of trusted users. This list 1717 always includes root, uucp, and daemon. | 1598e-mail sent to Full.Name@local.host.name will be rejected. 1599 1600To build the internal form of the user database, use: 1601 1602 makemap btree /usr/data/base.db < /usr/data/base.txt 1603 1604As a general rule, I am adamantly opposed to using full names as 1605e-mail addresses, since they are not in any sense unique. For example, --- 123 unchanged lines hidden (view full) --- 1729 (trusted users) class. 1730confCR_FILE FR class [/etc/mail/relay-domains] Name of 1731 file used to get the local additions 1732 to the $=R (hosts allowed to relay) 1733 class. 1734confTRUSTED_USERS Ct class [no default] Names of users to add to 1735 the list of trusted users. This list 1736 always includes root, uucp, and daemon. |
| 1718 See also FEATURE(use_ct_file). | 1737 See also FEATURE(`use_ct_file'). |
| 1719confSMTP_MAILER - [esmtp] The mailer name used when 1720 SMTP connectivity is required. 1721 One of "smtp", "smtp8", or "esmtp". 1722confUUCP_MAILER - [uucp-old] The mailer to be used by 1723 default for bang-format recipient 1724 addresses. See also discussion of 1725 $=U, $=Y, and $=Z in the MAILER(uucp) 1726 section. --- 529 unchanged lines hidden --- | 1738confSMTP_MAILER - [esmtp] The mailer name used when 1739 SMTP connectivity is required. 1740 One of "smtp", "smtp8", or "esmtp". 1741confUUCP_MAILER - [uucp-old] The mailer to be used by 1742 default for bang-format recipient 1743 addresses. See also discussion of 1744 $=U, $=Y, and $=Z in the MAILER(uucp) 1745 section. --- 529 unchanged lines hidden --- |