Lines Matching refs:will
99 The divert(-1) will delete the crud in the resulting output file.
115 mailer, and other important things. If you omit it, you will get an
174 it will not do what you expect, because the FEATURE(`foo') will be
197 8.10, all files will use this directory by default (some options may be
261 file build will puke. There are several environments available; look
289 example, /var/spool/mqueue/qd* will use all of the
312 local mailer and which are converted to MIME will be
335 SMTP_MAILER_MAX [undefined] The maximum size of messages that will
361 the SMTP mailers and which are converted to MIME will
376 the UUCP mailers and which are converted to MIME will
391 will be accepted by the procmail mailer.
408 will add the flag `e' to LOCAL_MAILER_FLAGS. Notice: there are
420 You will probably want to collect domain-dependent defines into one
425 UUCP_RELAY The host that will accept UUCP-addressed email.
428 BITNET_RELAY The host that will accept BITNET-addressed email.
430 DECNET_RELAY The host that will accept DECNET-addressed email.
432 of the form node::user will not work.
433 FAX_RELAY The host that will accept mail to the .FAX pseudo-domain.
435 LOCAL_RELAY The site that will handle unqualified names -- that
445 LUSER_RELAY The site that will handle lusers -- that is, apparently
478 local The local and prog mailers. You will almost always
569 the special keyword `LDAP'. If that keyword is used, the map will use the
584 names of users that will be ``trusted'', that is, able to
609 FEATURE(`nocanonify') will be overridden by setting the
631 expect a trailing dot (e.g., virtusertable) will
637 <user@host>, will be canonified (and hopefully fully
676 will forward to the indicated user using the local mailer,
678 will forward to the original user in the e-mail address
682 will give an error message with the indicated SMTP reply
729 feature will cause recipient addresses to also masquerade
733 if you send to "localalias", the originating sendmail will
736 alias likely does not exist, replies will fail. Use this
750 MASQUERADE_DOMAIN (see below) is set, this feature will
753 hosts within the masquerading domains will be rewritten
769 if MASQUERADE_AS is used. MASQUERADE_AS will only have effect
774 genericstable is in use, this feature will cause envelope
778 genericstable This feature will cause unqualified addresses (i.e., without
783 8.12), the MTA will only receive qualified addresses from the
803 does not include a domain, it will be qualified in the standard
817 GENERICS_DOMAIN_FILE is used, this feature will cause
831 then mail addressed to info@foo.com will be sent to the
832 address foo-info, mail addressed to info@bar.com will be
834 will be sent to jane@example.net, mail to joe@bar.com will
836 jax@bar.com will also have a RFC 1893 compliant error code
844 meaning someone@foo.org will be sent to someone@example.com.
882 VIRTUSER_DOMAIN_FILE is used, this feature will cause
965 domains, which will limit the feature to only apply to
966 these domains -- this will reduce unnecessary DNS
1004 will all be accepted for relaying. This feature changes
1011 you will accept and relay mail addressed to foo.com. See
1040 and you will go ahead and relay it out to arbitrary hosts
1044 Normally, MAIL FROM: commands in the SMTP session will be
1048 you will need to use this feature to accept unqualified
1056 Normally, MAIL FROM: commands in the SMTP session will be
1086 delay_checks The rulesets check_mail and check_relay will not be called
1088 Instead, those rulesets will be called by the check_rcpt
1089 ruleset; they will be skipped under certain circumstances.
1094 use_client_ptr If this feature is enabled then check_relay will override
1106 Without that second argument, the error message will be
1143 error message. By default, any successful lookup will
1150 will reject the e-mail if the lookup returns the value
1165 will be logged).
1236 check_rcpt ruleset will strip @othersite and recheck
1243 recipient address will be replaced by the host specified as
1254 that address will be looked up in the alias file; user+* and
1255 user will not be looked up). Only use if the local
1276 e-mails to. Note that MX records will be used if the
1356 Note: this feature will cause false positives, i.e., there
1385 this FEATURE() will not be applied to authenticated senders
1393 will whitelist IP address 1.2.3.4, so that the rDNS
1398 will have the effect of forcing a temporary failure for
1428 define what will go over the wire, UUCP uses the policy that you
1436 end will recognize. If at all possible, you should encourage the
1497 to convert all UUCP addresses to domain format -- otherwise, it will
1500 the heuristics will add the @uucp.relay.name or @local.host.name to
1502 will not add the local hostname. You can do this using the uucpdomain
1521 will cause addresses of the form "decvax!user" and "research!user"
1585 will not be delivered locally, any mail including any user@otherhost.domain
1586 will, when relayed, be rewritten to have the MASQUERADE_AS address.
1646 and MAIL_HUB _AND_ you have FEATURE(`stickyhost'), unqualified names will
1647 be sent to the LOCAL_RELAY and other local names will be sent to MAIL_HUB.
1650 Names in class {L} will be delivered locally, so you MUST have aliases or
1654 FEATURE(`stickyhost'), the following combinations of settings will have the
1683 really want absolutely everything to go to a single central site you will
1710 Here, the word `Servers' will be the cluster name. As an example, assume
1716 attribute or it will be ignored. Be careful as mixing clusters and
1735 By doing so, you will use the default schema which expands to a map
1781 Here, the aliases sendmail-list and owner-sendmail-list will be available
1782 only on etrn.sendmail.org but the postmaster alias will be available on
1825 When this keyword is given, that map will use LDAP lookups consisting of
1881 then these entries will give unexpected results. When the lookup is done
1901 mapkey is optional and if not provided the map key will be empty. This can
1943 will use "ClassName" for the sendmailMTAClassName.
1966 the result will be similar to the aliases caution above. When the lookup
2005 By default, the feature will use the schemas as specified in the draft
2006 and will not reject addresses not found by the LDAP lookup. However,
2018 is found, if set to "sendertoo", the sender will be rejected if not
2024 argument, if present, will prevent the @domain lookup if the full
2028 "queue" (the default), the MTA will locally queue the mail.
2139 If you really want to revert to the old behaviour, you will need to use
2165 will be relayed (that is, you will accept mail either to or from any
2174 and domain.com lists your server in its MX records, the mail will be
2177 case, mail will be temporarily rejected. It is usually better to
2179 Note also that this feature will stop spammers from using your host
2180 to relay spam but it will not stop outsiders from using your server
2182 to your mail server, and you will relay mail addressed to them
2187 will allow relaying if the sender specifies a return path (i.e.
2189 dangerous feature as it will allow spammers to spam using your mail
2209 RCPT TO:<user%site.com@othersite.com>), sendmail will check
2234 As of 8.9, sendmail will refuse mail if the MAIL FROM: parameter has
2241 will not be able to return mail to them unless you have some "smart
2260 sendmail will also refuse mail if the MAIL FROM: parameter is not
2329 If the required item is looked up in a map, it will be tried first
2343 is enabled. Your system will allow relaying to friend.domain, but
2345 domain will be allowed even if it ends up in one of the DNS based
2375 and IP addresses/nets. It will abort the current
2448 then the above example will allow relaying for sendmail.org, but not
2449 hosts within the sendmail.org domain. Note that this will also require
2477 hostnames and usernames). Enabling this feature will keep you from
2493 This will cause sendmail to reject mail from any site listed in the
2573 will not be called when a client connects or issues a MAIL command,
2574 respectively. Instead, those rulesets will be called by the check_rcpt
2575 ruleset; they will be skipped if a sender has been authenticated using
2577 If check_mail returns an error then the RCPT TO command will be rejected
2579 check_relay will be skipped. If the sender address (or a part of it) is
2581 will be skipped. This has an interesting side effect: if your domain is
2587 <user@my.domain> will not be rejected by check_relay even though
2604 If such an argument is given, the recipient will be looked up in the
2607 friend the exception. The rulesets check_mail and check_relay will be
2611 other two rulesets will be applied only if the recipient address is
2619 in the access map, mail to abuse@localdomain will get through (where
2630 ones will be ignored. As soon as you removed the old entries from
2632 the backward compatibility rules will not be in the generated .cf
2674 After all of the headers are read, the check_eoh ruleset will be called for
2731 rulesets should return the error code 421 which will cause
2743 In this text, cert will be used as an abbreviation for X.509 certificate,
2875 will be accepted unless ${verify} is SOFTWARE, in which case the connection
2955 will turn off STARTTLS when sending to broken.server (or any host
3022 of the filter such that the filter will actually be called by sendmail.
3039 commands will clear the list created by the prior INPUT_MAIL_FILTER()
3082 This will cause all names that end in your domain name ($m) to be sent
3083 via SMTP; anything else will be sent via uucp-new (smart UUCP) to uunet.
3125 anything sent to an address using a host name in this list will be
3141 To use FEATURE(`mailertable'), you will have to create an external
3161 above example, an entry of "uuhost1.my.domain" will match the second
3170 sendmail.cf file). The "host" will be the hostname passed to
3208 e-mail sent to Full.Name@local.host.name will be rejected.
3219 will be forced to suffer the indignity of being Stephen_R_Bourne_2?
3241 On the server, this will match an alias for "root+client1".
3242 If that is not found, the alias "root+*" will be tried,
3267 writable directory for forward files. This will allow anyone
3275 /etc/shells before they will be trusted (that is, before
3276 files and programs listed in them will be honored).
3302 be quoted. In particular, arguments with commas will usually have to
3389 that will be accepted (in bytes).
3436 to a host will prevent other sendmails
3446 deprecated and will be removed from
3565 statuses will be maintained before it
3633 will sleep for one second on most
3640 children the daemon will permit. After
3641 this number, connections will be
3655 will be delayed. If not set or <= 0,
3708 [undefined] If set, sendmail will do a
3721 entries. Essentially, this will stop
3749 "FTP" will return "FTP.Foo.ORG"; if
3770 will be inserted between the first and
3774 routine will never be invoked. You
3782 will only have their primary
3792 will be removed in future versions;
3815 If not set, the queue file will
3823 this user. Also, all programs will
3825 files will be written as this user.
3839 [False] If set, sendmail will _not_
3846 mail to addresses in this list will
3849 quotes), sendmail will skip
3858 safety checks. This will definitely
3886 settings will be used for all LDAP
3956 will slow down responding.
3965 filters will be contacted.
4020 If you use one DAEMON_OPTIONS macro, it will alter the parameters
4021 of the first of these. The second will still be defaulted; it
4025 additional DAEMON_OPTIONS macros, they will add additional daemons.
4047 the check_* rulesets). In accordance with the RFC, the MSA will ensure
4049 is relayed to another MTA. It will also enforce the normal address syntax