Lines Matching refs:example
72 use -D_CF_DIR_=/path/to/cf/dir/ -- note the trailing slash! For example:
124 This example is specific to the Computer Science Division at Berkeley.
148 influence a FEATURE() should be done before that feature. For example,
176 one normally quotes both values to prevent expansion. For example,
181 to be comments. For example, if you have
194 arguments, those quotes can't be used in arguments. For example,
304 commas in them -- for example, use
314 example, /var/spool/mqueue/qd* will use all of the
520 file, referenced by the DOMAIN macro. For example, the Berkeley
625 This is designed to be used in mailertables. For example,
680 FEATURE(`local_procmail')). For example, "eric", "eric+sendmail", and
690 example, the .mc line:
696 optional parameters -- for example:
808 or partial domains preceded by a dot -- for example,
874 ordinary users, it can break local aliases. For example,
896 to the masquerade name (used in MASQUERADE_AS). For example,
952 old+*@foo.org new+%1@example.com
953 gen+*@foo.org %1@example.com
964 virtual domains to be hosted on one machine. For example,
971 @baz.org jane@example.net
976 will be sent to jane@example.net, mail to joe@bar.com will
984 @foo.org %1@example.com
986 meaning someone@foo.org will be sent to someone@example.com.
991 old+*@foo.org new+%2@example.com
992 gen+*@foo.org %2@example.com
993 +*@foo.org %1%3@example.com
994 X++@foo.org Z%3@example.com
1089 For example, this allows it to use the maildrop
1139 like example.com instead of host.example.com.
1144 For example, if you specify ``foo.com'', then mail to or
1222 example, you can block incoming mail to user nobody,
1257 an example. The dnsbl feature can be included several times
1288 occurs an error is generated. For example,
1290 FEATURE(`enhdnsbl', `dnsbl.example.com', `', `t', `127.0.0.2.')
1295 as they are allowed in the LHS of rules. As the example
1318 Take the following example:
1339 Take the following example:
1451 queuegroup A simple example how to select a queue group based
1454 access map using the tag QGRP:, for example:
1456 QGRP:example.com main
1479 GreetPause:example.com 5000
1595 tricky. For an example of a "complex" site, see cf/ucbvax.mc.
1599 example, the line
1627 example:
1632 The second example demonstrates that you can use two names on the
1721 do it for you (and probably not the way you expected). For example,
1738 the UUCPSMTP macro. For example:
1756 For example, new rules are needed to parse hostnames that you accept
1757 via MX records. For example, you might have:
1772 whatever. For example:
1789 one of one's own subdomains (for example, it's unlikely that
1836 Root is an example (which has been "exposed" by default prior to 8.10).
1846 without @host) to a relay host. For example, if you have a central
1854 because of local aliases. A common example is root, which may be
1876 For example, if you are on machine mastodon.CS.Berkeley.EDU and you have
1929 unique name. For example:
1933 Here, the word `Servers' will be the cluster name. As an example, assume
1982 sendmailMTAAliasValue: ca@example.org
1984 sendmailMTAAliasValue: gshapiro@example.com
2033 specify the map parameters when setting ALIAS_FILE. For example:
2066 For example, FEATURE(`mailertable', `LDAP') would use the map definition:
2075 An example LDAP LDIF entry using this map might be:
2083 dn: sendmailMTAKey=example.com, sendmailMTAMapName=mailer, dc=sendmail, dc=org
2089 sendmailMTAKey: example.com
2090 sendmailMTAMapValue: relay:[smtp.example.com]
2095 dn: sendmailMTAKey=example.com@etrn, sendmailMTAMapName=mailer, dc=sendmail, dc=org
2101 sendmailMTAKey: example.com
2102 sendmailMTAMapValue: relay:[mx.example.com]
2107 Servers cluster, LDAP would return two answers for the example.com map key
2111 specify the map parameters when using the FEATURE(). For example:
2127 use the default LDAP schema. For example:
2168 An example LDAP LDIF entry would look like:
2176 sendmailMTAClassValue: example.com
2187 sendmailMTAClassValue: example.com
2195 specify the map parameters when using the class command. For example:
2212 address (e.g., user@example.com) and then on the domain portion
2213 (e.g., @example.com). Be sure to setup your domain for LDAP routing using
2216 LDAPROUTE_DOMAIN(`example.com')
2221 the LDAP query. For example, if the mail is addressed to
2222 user@host1.example.com, normally the LDAP lookup would only be done for
2223 'user@host1.example.com' and '@host1.example.com'. However, if
2224 LDAPROUTE_EQUIVALENT(`host1.example.com') is used, the lookups would also be
2225 done on 'user@example.com' and '@example.com' after attempting the
2226 host1.example.com lookups.
2308 contain an RFC 822 compliant address. Some example LDAP records (in LDIF
2311 dn: uid=tom, o=example.com, c=US
2313 mailLocalAddress: tom@example.com
2314 mailRoutingAddress: thomas@mailhost.example.com
2316 This would deliver mail for tom@example.com to thomas@mailhost.example.com.
2318 dn: uid=dick, o=example.com, c=US
2320 mailLocalAddress: dick@example.com
2321 mailHost: eng.example.com
2323 This would relay mail for dick@example.com to the same address but redirect
2324 the mail to MX records listed for the host eng.example.com (unless the
2327 dn: uid=harry, o=example.com, c=US
2329 mailLocalAddress: harry@example.com
2330 mailHost: mktmail.example.com
2331 mailRoutingAddress: harry@mkt.example.com
2333 This would relay mail for harry@example.com to the MX records listed for
2334 the host mktmail.example.com using the new address harry@mkt.example.com
2337 dn: uid=virtual.example.com, o=example.com, c=US
2339 mailLocalAddress: @virtual.example.com
2340 mailHost: server.example.com
2341 mailRoutingAddress: virtual@example.com
2343 This would send all mail destined for any username @virtual.example.com to
2344 the machine server.example.com's MX servers and deliver to the address
2345 virtual@example.com on that relay machine.
2396 For example, if your server receives a recipient of user@domain.com
2450 <example.net!user@local.host> would be relayed to <user@example.net>.
2495 selected domains. For example, you may choose to reject all mail
2504 definition for the database; for example
2515 To:user@example.com RELAY
2521 map. For example:
2527 For example,
2555 requires a tag. For example,
2581 ruleset would reject it, for example, if the domain
2631 For example:
2640 Connect:suspicious.example.com QUARANTINE:Mail from suspicious host
2657 error code to match it. For example, if you use
2659 To:user@example.com ERROR:450 mailbox full
2671 then the above example will allow relaying for sendmail.org, but not
2676 the username portion of the address. For example:
2702 as value part in the access map. Taking the example from above:
2714 FEATURE(`dnsbl', `dnsbl.example.com')
2725 text or action. For example,
2727 FEATURE(`dnsbl', `dnsbl.example.com', `quarantine')
2730 at `dnsbl.example.com'.
2736 example:
2738 FEATURE(`dnsbl', `dnsbl.example.com', `',
2739 `"451 Temporary lookup failure for " $&{client_addr} " in dnsbl.example.com"')
2769 example if you wanted to block senders with all numeric usernames
2863 in sendmail.cf. For example, this can be used to check the validity of
2901 example usage is to reject messages which do not have a Message-Id:
2903 not a guaranteed spam indicator. This ruleset is an example and should
3032 by their HEX value with a leading '+'. For example:
3152 Example: e-mail sent to secure.example.com should only use an encrypted
3153 connection. E-mail received from hosts within the laptop.example.com domain
3158 TLS_Srv:secure.example.com ENCR:112
3159 TLS_Clt:laptop.example.com PERM+VERIFY:112
3172 A default case can be specified by using just the tag. For example,
3201 authenticated themselves. A very simple example is:
3229 For example:
3296 LOCAL_RULESETS respectively. For example:
3309 respectively. For example, to add a local ruleset that decides
3331 name and equates. For example:
3343 For example, the two commands:
3395 For example:
3427 result. For example, in some environments gethostname returns
3462 For example, a mailertable file in text format might be:
3479 -- for example, even though ".my.domain" is listed first in the
3480 above example, an entry of "uuhost1.my.domain" will match the second
3492 the host name. For example, the first line above sends everything
3497 particularly on gateways. For example, you may want to MX
3535 example, the UNIX software-development community has at least two
3551 centralized mail machine, for example, to forward all
3555 using plussed users. For example, a client might include
4069 this. For example, if "FTP.Foo.ORG"
4475 workarounds. For example, to allow for client authentication it
4528 each of which contains a single element of the class. For example,
4571 site dependent; for example, "CS.Berkeley.EDU.m4"