Lines Matching +refs:have +refs:feature
148 influence a FEATURE() should be done before that feature. For example,
153 *** BE SURE YOU CUSTOMIZE THESE FILES! They have some ***
195 ``A'' to have value ``B''. Macros are expanded as they are read, so
201 to be comments. For example, if you have
227 Unfortunately, the M4 on BSDI 1.0 doesn't work -- you'll have to use a
564 belong on this machine. This allows you to have a
577 a variant on SMTP) is used. WARNING: if you have a wildcard MX
579 have a trailing dot so that you won't get the mail diverted back
587 You do not have to define a domain -- in particular, if you are a
651 domain to a single person?". If you have this mailer
670 mail11 The DECnet mail11 mailer, useful only if you have the mail11
673 if you have Phase V at your site you may have additional
718 tells sendmail that you want to have it read an /etc/mail/local-host-names
732 feature that uses a map.
757 If this is set, you can alias people who have left
760 nouucp Don't route UUCP addresses. This feature takes one
762 `reject': reject addresses which have "!" in the local
770 nopercenthack Don't treat % as routing character. This feature takes one
772 `reject': reject addresses which have % in the local
789 be used by sites that only act as mail gateways or which have
812 addresses which have only a hostname, e.g.,
816 stickyhost This feature is sometimes used with LOCAL_RELAY,
888 uucpdomain Similar feature for UUCP hosts. The default map definition
905 feature will cause recipient addresses to also masquerade
913 feature ONLY if you can guarantee that the ENTIRE
919 this feature is given, only the hosts listed in class {M} (see
921 if you have several domains with disjoint namespaces hosted
926 MASQUERADE_DOMAIN (see below) is set, this feature will
931 if you have:
938 this feature, only foo.org and bar.com are masqueraded.
944 This feature prevents the local mailer from masquerading even
945 if MASQUERADE_AS is used. MASQUERADE_AS will only have effect
950 genericstable is in use, this feature will cause envelope
954 genericstable This feature will cause unqualified addresses (i.e., without
961 domain to class {G}. This feature is similar to the userdb
965 features are given. Qualified addresses must have the domain
993 GENERICS_DOMAIN_FILE is used, this feature will cause
1012 jax@bar.com will also have a RFC 1893 compliant error code
1058 VIRTUSER_DOMAIN_FILE is used, this feature will cause
1078 The only other feature that should be used in conjunction
1083 feature is the pathname of an LMTP capable mailer. By
1095 WARNING: This feature sets LOCAL_MAILER_FLAGS unconditionally,
1099 The argument to this feature is the pathname of the
1110 This feature can take up to three arguments:
1133 WARNING: This feature sets LOCAL_MAILER_FLAGS unconditionally,
1140 domains, which will limit the feature to only apply to
1143 WILDCARD MX RECORDS!!! If you have a wildcard MX record
1144 that matches your domain, you cannot use this feature.
1179 will all be accepted for relaying. This feature changes
1188 feature. Also, see the KNOWNBUGS entry regarding bestmx
1202 of the sender address. This feature should only be used if
1204 forged. Use of this feature requires the "From:" tag to
1223 you will need to use this feature to accept unqualified
1237 use this feature to accept all domains on input, even if
1240 access_db Turns on the access database feature. The access db gives
1249 important information about this feature. Notice:
1266 section. Note: this feature is incompatible to the versions
1275 use_client_ptr If this feature is enabled then check_relay will override
1296 an example. The dnsbl feature can be included several times
1313 before the first use of this feature. Alternatively you
1338 i.e., `', is specified. This feature requires that sendmail
1386 10.1.2.3 can only have up to 4 open connections, the
1387 general limit it 10, and 127.0.0.1 does not have any
1414 subdomains are suppressed by the latter feature.
1420 user@site for relaying. This feature changes that
1433 LUSER_RELAY. This feature only works if the hostname is
1482 by default. If you have a machine with IPv6 only,
1509 and SMTP slamming protection. The feature can take an
1546 is required. Note, the block_bad_helo feature automatically
1552 Note: this feature will cause false positives, i.e., there
1553 are legitimate MTAs that do not have proper DNS entries.
1567 is excepted from the rules. Since we have explicitly
1573 through their ISP, whether or not they have valid rDNS.
1594 will have the effect of forcing a temporary failure for
1609 Note: this feature requires that the sendmail binary
1617 postfix-mta-sts-resolver (see feature/sts.m4
1712 should do what is right for the other end; if they change, you have
1782 if you have the address foo!bar!baz (and you are not sending to foo),
1786 feature.
1817 via MX records. For example, you might have:
1843 You can have your host masquerade as another using
1869 will, when relayed, be rewritten to have the MASQUERADE_AS address.
1906 without @host) to a relay host. For example, if you have a central
1907 email server, you might relay to that host so that users don't have
1908 to have .forward files or aliases. You can do this using
1929 and MAIL_HUB _AND_ you have FEATURE(`stickyhost'), unqualified names will
1933 Names in class {L} will be delivered locally, so you MUST have aliases or
1936 For example, if you are on machine mastodon.CS.Berkeley.EDU and you have
1937 FEATURE(`stickyhost'), the following combinations of settings will have the
1951 If you do not have FEATURE(`stickyhost') set, then LOCAL_RELAY and
1998 Every entry must have either a sendmailMTAHost or sendmailMTACluster
2000 individual host records can have surprising results (see the CAUTION
2269 (draft-lachman-laser-ldap-mail-routing-01). This feature enables
2288 By default, the feature will use the schemas as specified in the draft
2458 accepted for relay to domain.com. This feature may cause problems
2462 Note also that this feature will stop spammers from using your host
2472 dangerous feature as it will allow spammers to spam using your mail
2484 map entries. This feature allows spammers to abuse your mail server
2500 If you think you need to use this feature, you probably do not. This
2501 should only be used for sites which have no control over the addresses
2510 same feature (nouucp / nopercenthack) at all, addresses of the form
2526 will not be able to return mail to them unless you have some "smart
2574 `lookupdotdomain' another way to enable the feature of the
2616 backward compatibility) without any tag, unless the specific feature
2762 hostnames and usernames). Enabling this feature will keep you from
2763 sending mails to all addresses that have an error message or REJECT
2814 blocklists, use the access_db feature and add:
2867 my.domain and you have
2875 avoid this problem you have to use tagged entries:
2916 the access map, specify a third parameter (`n') to this feature and
2944 A default ruleset for headers which don't have a specific ruleset
2963 example usage is to reject messages which do not have a Message-Id:
3041 On systems which do not have the compile flag HASURANDOM set (see
3079 SMTP STARTTLS can allow relaying for remote SMTP clients which have
3104 (line breaks have been inserted for readability).
3121 To allow relaying only for a subset of machines that have a cert signed by
3133 Note: line breaks have been inserted after "CN=" for readability,
3151 (should) have been issued. The parameter is the value of ${verify}.
3189 VERIFY verification must have succeeded
3190 VERIFY:bits verification must have succeeded and ${cipher_bits} must
3215 should only be accepted if they have been authenticated. The host which
3218 have a matching CN, and must present a cert signed by a CA with one of
3315 and have an identity in the local domains.
3345 only performed if the access map is used; if the authinfo feature
3357 want to use DefaultAuthInfo (it is deprecated) then you have to
3378 other entries have default values. If one of user or authentication
3504 If you have FEATURE(`nocanonify'), you may need to omit the dots after
3552 If you want to have different address in different domains, take
3553 a look at the virtusertable feature, which is also explained at
3561 To use FEATURE(`mailertable'), you will have to create an external
3583 does not match any entry in the above table. You need to have
3694 particular, you'll have to have /SENDMAIL/ANY/SHELL/ in
3724 be quoted. In particular, arguments with commas will usually have to
4123 systems that do not have a
4130 demand" connections to have enough time
4198 [False] From: lines that have
4217 running NIS and you have a large group
4223 will only have their primary
4276 transaction have been rejected, sleep
4632 its group should be smmsp, and it should have mode 640. The database
4633 used by the MTA for AUTH must have a corresponding entry.
4649 feature/msp.m4 defines almost all settings for the MSP. Most of
4653 in feature/msp.m4. If it is directly defined (i.e., define()) then
4660 To see how the options are defined read feature/msp.m4.
4669 /etc/mail/local-host-names may have the following content:
4698 cf The configuration files themselves. They have
4701 have a ".cf" suffix.
4720 feature These hold special orthogonal features that you might
4795 U my UUCP name (if you have a UUCP connection)