| README (203004) | README (244833) |
|---|---|
| 1 2 SENDMAIL CONFIGURATION FILES 3 4This document describes the sendmail configuration files. It 5explains how to create a sendmail.cf file for use with sendmail. 6It also describes how to set options for sendmail which are explained 7in the Sendmail Installation and Operation guide (doc/op/op.me). 8 --- 1130 unchanged lines hidden (view full) --- 1139 like example.com instead of host.example.com. 1140 1141relay_hosts_only 1142 By default, names that are listed as RELAY in the access 1143 db and class {R} are treated as domain names, not host names. 1144 For example, if you specify ``foo.com'', then mail to or 1145 from foo.com, abc.foo.com, or a.very.deep.domain.foo.com 1146 will all be accepted for relaying. This feature changes | 1 2 SENDMAIL CONFIGURATION FILES 3 4This document describes the sendmail configuration files. It 5explains how to create a sendmail.cf file for use with sendmail. 6It also describes how to set options for sendmail which are explained 7in the Sendmail Installation and Operation guide (doc/op/op.me). 8 --- 1130 unchanged lines hidden (view full) --- 1139 like example.com instead of host.example.com. 1140 1141relay_hosts_only 1142 By default, names that are listed as RELAY in the access 1143 db and class {R} are treated as domain names, not host names. 1144 For example, if you specify ``foo.com'', then mail to or 1145 from foo.com, abc.foo.com, or a.very.deep.domain.foo.com 1146 will all be accepted for relaying. This feature changes |
| 1147 the behaviour to lookup individual host names only. | 1147 the behaviour to look up individual host names only. |
| 1148 1149relay_based_on_MX 1150 Turns on the ability to allow relaying based on the MX 1151 records of the host portion of an incoming recipient; that 1152 is, if an MX record for host foo.com points to your site, 1153 you will accept and relay mail addressed to foo.com. See 1154 description below for more information before using this 1155 feature. Also, see the KNOWNBUGS entry regarding bestmx --- 1069 unchanged lines hidden (view full) --- 2225By default, the feature will use the schemas as specified in the draft 2226and will not reject addresses not found by the LDAP lookup. However, 2227this behavior can be changed by giving additional arguments to the FEATURE() 2228command: 2229 2230 FEATURE(`ldap_routing', <mailHost>, <mailRoutingAddress>, <bounce>, 2231 <detail>, <nodomain>, <tempfail>) 2232 | 1148 1149relay_based_on_MX 1150 Turns on the ability to allow relaying based on the MX 1151 records of the host portion of an incoming recipient; that 1152 is, if an MX record for host foo.com points to your site, 1153 you will accept and relay mail addressed to foo.com. See 1154 description below for more information before using this 1155 feature. Also, see the KNOWNBUGS entry regarding bestmx --- 1069 unchanged lines hidden (view full) --- 2225By default, the feature will use the schemas as specified in the draft 2226and will not reject addresses not found by the LDAP lookup. However, 2227this behavior can be changed by giving additional arguments to the FEATURE() 2228command: 2229 2230 FEATURE(`ldap_routing', <mailHost>, <mailRoutingAddress>, <bounce>, 2231 <detail>, <nodomain>, <tempfail>) 2232 |
| 2233where | 2233where <mailHost> is a map definition describing how to look up an alternative |
| 2234mail host for a particular address; <mailRoutingAddress> is a map definition | 2234mail host for a particular address; <mailRoutingAddress> is a map definition |
| 2235describing how to lookup an alternative address for a particular address; | 2235describing how to look up an alternative address for a particular address; |
| 2236the <bounce> argument, if present and not the word "passthru", dictates 2237that mail should be bounced if neither a mailHost nor mailRoutingAddress 2238is found, if set to "sendertoo", the sender will be rejected if not 2239found in LDAP; and <detail> indicates what actions to take if the address 2240contains +detail information -- `strip' tries the lookup with the +detail 2241and if no matches are found, strips the +detail and tries the lookup again; 2242`preserve', does the same as `strip' but if a mailRoutingAddress match is 2243found, the +detail information is copied to the new address; the <nodomain> --- 2452 unchanged lines hidden (view full) --- 4696 3 Local Ruleset 0 additions 4697 4 UUCP Ruleset 0 additions 4698 5 locally interpreted names (overrides $R) 4699 6 local configuration (at top of file) 4700 7 mailer definitions 4701 8 DNS based blacklists 4702 9 special local rulesets (1 and 2) 4703 | 2236the <bounce> argument, if present and not the word "passthru", dictates 2237that mail should be bounced if neither a mailHost nor mailRoutingAddress 2238is found, if set to "sendertoo", the sender will be rejected if not 2239found in LDAP; and <detail> indicates what actions to take if the address 2240contains +detail information -- `strip' tries the lookup with the +detail 2241and if no matches are found, strips the +detail and tries the lookup again; 2242`preserve', does the same as `strip' but if a mailRoutingAddress match is 2243found, the +detail information is copied to the new address; the <nodomain> --- 2452 unchanged lines hidden (view full) --- 4696 3 Local Ruleset 0 additions 4697 4 UUCP Ruleset 0 additions 4698 5 locally interpreted names (overrides $R) 4699 6 local configuration (at top of file) 4700 7 mailer definitions 4701 8 DNS based blacklists 4702 9 special local rulesets (1 and 2) 4703 |
| 4704$Revision: 8.727 $, Last updated $Date: 2009/05/07 23:46:17 $ | 4704$Revision: 8.728 $, Last updated $Date: 2012/09/07 16:29:13 $ |