Lines Matching +refs:feature +refs:define +refs:name
67 name of your configuration file. If you are running a version of M4
98 # to a name of your own choosing.
105 is a copyright by another name. The divert(0) restores regular output.
148 influence a FEATURE() should be done before that feature. For example,
149 a define(`PROCMAIL_MAILER_PATH', ...) should be done before
154 *** Berkeley-specific assumptions built in, such as the name ***
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").
328 HELP_FILE [/etc/mail/helpfile] The name of the file
373 USENET_MAILER_PATH [/usr/lib/news/inews] The name of the program
501 change the name of the Unix domain socket, or
574 mailer is the internal mailer name, such as ``uucp-new'' and the hostname
575 is the name of the host as appropriate for that mailer) or just 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
584 at your site masquerade behind one email name, you could also use
587 You do not have to define a domain -- in particular, if you are a
609 running the name server. This file actually defines
663 name of the sender and $2 is the name of the recipient.
678 to do CCSO name server lookups. The phquery program, which
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,
847 where "mailer" is the internal mailer name, and "domain"
863 domain name mapping. Use of this should really be
872 The key in this table is the domain name; the value is
888 uucpdomain Similar feature for UUCP hosts. The default map definition
900 the same user name space everywhere, you may need the host
901 name on local names. An optional argument specifies
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
930 to the masquerade name (used in MASQUERADE_AS). For example,
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
957 form, which can change both the domain name and the user name.
961 domain to class {G}. This feature is similar to the userdb
980 manner, i.e., using $j or the masquerade name. Note that the
993 GENERICS_DOMAIN_FILE is used, this feature will cause
1058 VIRTUSER_DOMAIN_FILE is used, this feature will cause
1076 is the name of that hub.
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:
1114 2. Argument vector including name of the program
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.
1171 e.g., com. This can happen if you give your host a name
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
1221 sender address does not include a domain name. If your
1223 you will need to use this feature to accept unqualified
1233 cannot be located in the host name service (e.g., an A or
1235 only a limited view of the Internet host name space, this
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
1430 Preserve the name of the recipient host if LUSER_RELAY is
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
1536 names (i.e., the server name instead of the client name).
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
1663 second parameter is the local name (in this case just "ucbvax" since
1665 parameter is the name of both a macro to store the local name (in
1666 this case, {U}) and the name of the class (e.g., {U}) in which to store
1674 is, the name of the relay to which the hosts listed in uucp.ucbarpa
1680 special; the second parameter is assumed to be the UUCP name of the
1681 local site, rather than the name of a remote site, and the UUCP name
1711 define what will go over the wire, UUCP uses the policy that you
1725 uucp-old (obsolete name: "uucp")
1728 everything and prepends $U (your UUCP name) to the sender's
1734 uucp-new (obsolete name: "suucp")
1754 local hostname, unless there is no host name on the address
1755 at all (e.g., "wolf") or the host component is a UUCP host name
1756 instead of a domain name ("somehost!wolf" instead of
1762 On host grasp.insa-lyon.fr (UUCP host name "grasp"), the following
1783 the heuristics will add the @uucp.relay.name or @local.host.name to
1784 this address. However, if you map foo to foo.host.name first, it
1786 feature.
1793 For more complex configurations, you can define special rules.
1855 The masquerade name is not normally canonified, so it is important
1895 internal site name should be displayed instead of the masquerade name.
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
1958 MAIL_HUB applies to names qualified with the name of the
1970 For duplicate suppression to work properly, the host name is best
1973 define(`MAIL_HUB', `host.domain.')
1987 each LDAP entry. To set the LDAP cluster name to use for a particular
1989 unique name. For example:
1991 define(`confLDAP_CLUSTER', `Servers')
1993 Here, the word `Servers' will be the cluster name. As an example, assume
2016 define(`ALIAS_FILE', `ldap:')
2095 define(`ALIAS_FILE', `ldap:-k (&(objectClass=mailGroup)(mail=%0)) -v mgrpRFC822MailMember')
2110 with the map name, a search attribute of sendmailMTAKey, and the value
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
2366 must contain a fully qualified host name as its value. Similarly, if
2424 through your server by adding their domain name or IP address to class
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
2520 an unresolvable domain (i.e., one that DNS, your local name service,
2523 IP address can't be mapped to a host name. If you want to continue
2525 has only a limited view of the Internet host name space (note that you
2574 `lookupdotdomain' another way to enable the feature of the
2575 same name (see above).
2616 backward compatibility) without any tag, unless the specific feature
2644 name is unresolvable. "Accept" does not mean
2762 hostnames and usernames). Enabling this feature will keep you from
2814 blocklists, use the access_db feature and add:
2851 NOT create a mailer with the name OK. Return values that do not start
2916 the access map, specify a third parameter (`n') to this feature and
2957 3. When using a default ruleset for headers, the name of the header
3030 DN (CN) is the distinguished (common) name of a cert, and CA is a
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')
3071 ${server_name} the name of the server of the current outgoing SMTP
3206 CN:name name must match ${cn_subject}
3208 CS:name name must match ${cert_subject}
3209 CI:name name must match ${cert_issuer}
3345 only performed if the access map is used; if the authinfo feature
3415 Note: you don't need to add a name for the ruleset, it is implicitly
3427 MAIL_FILTER(`name', `equates')
3428 INPUT_MAIL_FILTER(`name', `equates')
3431 name and equates. For example:
3440 but also populates the m4 variable `confINPUT_MAIL_FILTERS' with the name
3452 define(`confINPUT_MAIL_FILTERS', `archive, spamcheck')
3454 In general, INPUT_MAIL_FILTER() should be used unless you need to define
3471 QUEUE_GROUP(`name', `equates')
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')
3502 This will cause all names that end in your domain name ($m) to be sent
3509 define(`SMART_HOST', `smtp:fire.wall.com')
3526 qualified domain name (FQDN). Sendmail does this by getting your
3527 host name using gethostname and then calling gethostbyname on the
3529 only the root of the host name (such as "foo"); gethostbyname is
3532 you MUST define confDOMAIN_NAME to be your fully qualified domain
3533 name. This is usually done using:
3536 define(`confDOMAIN_NAME', `$w.$m')dnl
3545 anything sent to an address using a host name in this list will be
3549 ``LOCAL_DOMAIN(`alias.host.name')''. Be sure you use the fully-qualified
3550 name of the host, rather than a short name.
3553 a look at the virtusertable feature, which is also explained at
3575 a dot matches the full host name indicated. LHS entries beginning
3576 with a dot match anything ending with that domain name (including
3589 configuration name of a mailer (that is, an M line in the
3593 the host name. For example, the first line above sends everything
3594 addressed to "anything.my.domain" to that same host name, but using
3628 e-mail sent to Full.Name@local.host.name will be rejected.
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
3731 confMAILER_NAME $n macro [MAILER-DAEMON] The sender name used
3736 determine your local domain name,
3739 domain name.
3741 configuration version name.
3779 confSMTP_MAILER - [esmtp] The mailer name used when
3788 confLOCAL_MAILER - [local] The mailer name used when
3791 confRELAY_MAILER - [relay] The default mailer name used
4202 does not include a host name.
4204 name phrase (@,;:\()[] are automatic).
4409 name of the UNIX socket if EGD is
4460 confHELO_NAME HeloName If defined, use as name for EHLO/HELO
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
4795 U my UUCP name (if you have a UUCP connection)