Lines Matching +refs:define +refs:feature
148 influence a FEATURE() should be done before that feature. For example,
149 a define(`PROCMAIL_MAILER_PATH', ...) should be done before
178 define(`_FFR_NAME_HERE', 1)
194 Other important directives are define(A, B) which defines the macro
198 define(`SMART_HOST', `smart.foo.com')
208 # And then define the $X macro to be the return address
210 because ``define'' is an M4 keyword. If you want to use them, surround
215 it is not possible to define a rejection message containing a single
305 You MUST define an operating system environment, or the configuration
315 Operating system definitions are usually easy to write. They may define
325 define(`ALIAS_FILE', `a,b')
327 otherwise the define() primitive only sees "a").
578 record matching your domain, you probably want to define these to
582 The domain file can also be used to define a domain name, if needed
587 You do not have to define a domain -- in particular, if you are a
726 define(`DATABASE_MAP_TYPE', `dbm')
732 feature that uses a map.
760 nouucp Don't route UUCP addresses. This feature takes one
770 nopercenthack Don't treat % as routing character. This feature takes one
792 "define(`confBIND_OPTS', `-DNSRCH -DEFNAMES')" to turn off
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
926 MASQUERADE_DOMAIN (see below) is set, this feature will
938 this feature, only foo.org and bar.com are masqueraded.
944 This feature prevents the local mailer from masquerading even
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
993 GENERICS_DOMAIN_FILE is used, this feature will cause
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
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
1311 define(`DNSBL_MAP', `dns -R A')
1313 before the first use of this feature. Alternatively you
1318 define(`DNSBL_MAP', `dns -R A -r2')
1338 i.e., `', is specified. This feature requires that sendmail
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
1461 To define a MSA daemon with other parameters, use this
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
1609 Note: this feature requires that the sendmail binary
1617 postfix-mta-sts-resolver (see feature/sts.m4
1711 define what will go over the wire, UUCP uses the policy that you
1786 feature.
1793 For more complex configurations, you can define special rules.
1910 define(`LOCAL_RELAY', `mailer:hostname')
1926 define(`MAIL_HUB', `mailer:hostname')
1928 Again, ``mailer:'' defaults to "relay". If you define both LOCAL_RELAY
1954 If you want all outgoing mail to go to a central relay site, define
1973 define(`MAIL_HUB', `host.domain.')
1991 define(`confLDAP_CLUSTER', `Servers')
2016 define(`ALIAS_FILE', `ldap:')
2095 define(`ALIAS_FILE', `ldap:-k (&(objectClass=mailGroup)(mail=%0)) -v mgrpRFC822MailMember')
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
2510 same feature (nouucp / nopercenthack) at all, addresses of the form
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
2814 blocklists, use the access_db feature and add:
2916 the access map, specify a third parameter (`n') to this feature and
3036 define(`confCACERT_PATH', `/etc/mail/certs/')
3037 define(`confCACERT', `/etc/mail/certs/CA.cert.pem')
3038 define(`confSERVER_CERT', `/etc/mail/certs/my.cert.pem')
3039 define(`confSERVER_KEY', `/etc/mail/certs/my.key.pem')
3345 only performed if the access map is used; if the authinfo feature
3452 define(`confINPUT_MAIL_FILTERS', `archive, spamcheck')
3454 In general, INPUT_MAIL_FILTER() should be used unless you need to define
3486 You can define a ``smart host'' that understands a richer address syntax
3489 define(`SMART_HOST', `mailer:hostname')
3498 define(`SMART_HOST', `uucp-new:uunet')
3509 define(`SMART_HOST', `smtp:fire.wall.com')
3532 you MUST define confDOMAIN_NAME to be your fully qualified domain
3536 define(`confDOMAIN_NAME', `$w.$m')dnl
3553 a look at the virtusertable feature, which is also explained at
3708 you can define the following M4 variables. Note that some of these
3713 This list is shown in four columns: the name you define, the default
4602 define(`confDIRECT_SUBMISSION_MODIFIERS', `C')
4620 define(`confDONT_BLAME_SENDMAIL', `GroupReadableKeyFile')
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.
4667 Files that define classes, i.e., F{classname}, consist of lines
4720 feature These hold special orthogonal features that you might