Lines Matching refs:example
69 use -D_CF_DIR_=/path/to/cf/dir/ -- note the trailing slash! For example:
121 This example is specific to the Computer Science Division at Berkeley.
145 influence a FEATURE() should be done before that feature. For example,
165 one normally quotes both values to prevent expansion. For example,
170 to be comments. For example, if you have
183 arguments, those quotes can't be used in arguments. For example,
279 commas in them -- for example, use
289 example, /var/spool/mqueue/qd* will use all of the
421 file, referenced by the DOMAIN macro. For example, the Berkeley
514 This is designed to be used in mailertables. For example,
538 FEATURE(`local_procmail')). For example, "eric", "eric+sendmail", and
548 example, the .mc line:
554 optional parameters -- for example:
666 or partial domains preceded by a dot -- for example,
732 ordinary users, it can break local aliases. For example,
754 to the masquerade name (used in MASQUERADE_AS). For example,
810 old+*@foo.org new+%1@example.com
811 gen+*@foo.org %1@example.com
822 virtual domains to be hosted on one machine. For example,
829 @baz.org jane@example.net
834 will be sent to jane@example.net, mail to joe@bar.com will
842 @foo.org %1@example.com
844 meaning someone@foo.org will be sent to someone@example.com.
849 old+*@foo.org new+%2@example.com
850 gen+*@foo.org %2@example.com
851 +*@foo.org %1%3@example.com
852 X++@foo.org Z%3@example.com
947 For example, this allows it to use the maildrop
997 like example.com instead of host.example.com.
1002 For example, if you specify ``foo.com'', then mail to or
1080 example, you can block incoming mail to user nobody,
1115 an example. The dnsbl feature can be included several times
1146 occurs an error is generated. For example,
1148 FEATURE(`enhdnsbl', `dnsbl.example.com', `', `t', `127.0.0.2.')
1153 as they are allowed in the LHS of rules. As the example
1176 Take the following example:
1197 Take the following example:
1300 queuegroup A simple example how to select a queue group based
1303 access map using the tag QGRP:, for example:
1305 QGRP:example.com main
1328 GreetPause:example.com 5000
1498 do it for you (and probably not the way you expected). For example,
1515 the UUCPSMTP macro. For example:
1533 For example, new rules are needed to parse hostnames that you accept
1534 via MX records. For example, you might have:
1549 whatever. For example:
1566 one of one's own subdomains (for example, it's unlikely that
1613 Root is an example (which has been "exposed" by default prior to 8.10).
1623 without @host) to a relay host. For example, if you have a central
1631 because of local aliases. A common example is root, which may be
1653 For example, if you are on machine mastodon.CS.Berkeley.EDU and you have
1706 unique name. For example:
1710 Here, the word `Servers' will be the cluster name. As an example, assume
1759 sendmailMTAAliasValue: ca@example.org
1761 sendmailMTAAliasValue: gshapiro@example.com
1810 specify the map parameters when setting ALIAS_FILE. For example:
1843 For example, FEATURE(`mailertable', `LDAP') would use the map definition:
1852 An example LDAP LDIF entry using this map might be:
1860 dn: sendmailMTAKey=example.com, sendmailMTAMapName=mailer, dc=sendmail, dc=org
1866 sendmailMTAKey: example.com
1867 sendmailMTAMapValue: relay:[smtp.example.com]
1872 dn: sendmailMTAKey=example.com@etrn, sendmailMTAMapName=mailer, dc=sendmail, dc=org
1878 sendmailMTAKey: example.com
1879 sendmailMTAMapValue: relay:[mx.example.com]
1884 Servers cluster, LDAP would return two answers for the example.com map key
1888 specify the map parameters when using the FEATURE(). For example:
1904 use the default LDAP schema. For example:
1945 An example LDAP LDIF entry would look like:
1953 sendmailMTAClassValue: example.com
1964 sendmailMTAClassValue: example.com
1972 specify the map parameters when using the class command. For example:
1989 address (e.g., user@example.com) and then on the domain portion
1990 (e.g., @example.com). Be sure to setup your domain for LDAP routing using
1993 LDAPROUTE_DOMAIN(`example.com')
1998 the LDAP query. For example, if the mail is addressed to
1999 user@host1.example.com, normally the LDAP lookup would only be done for
2000 'user@host1.example.com' and '@host1.example.com'. However, if
2001 LDAPROUTE_EQUIVALENT(`host1.example.com') is used, the lookups would also be
2002 done on 'user@example.com' and '@example.com' after attempting the
2003 host1.example.com lookups.
2085 contain an RFC 822 compliant address. Some example LDAP records (in LDIF
2088 dn: uid=tom, o=example.com, c=US
2090 mailLocalAddress: tom@example.com
2091 mailRoutingAddress: thomas@mailhost.example.com
2093 This would deliver mail for tom@example.com to thomas@mailhost.example.com.
2095 dn: uid=dick, o=example.com, c=US
2097 mailLocalAddress: dick@example.com
2098 mailHost: eng.example.com
2100 This would relay mail for dick@example.com to the same address but redirect
2101 the mail to MX records listed for the host eng.example.com (unless the
2104 dn: uid=harry, o=example.com, c=US
2106 mailLocalAddress: harry@example.com
2107 mailHost: mktmail.example.com
2108 mailRoutingAddress: harry@mkt.example.com
2110 This would relay mail for harry@example.com to the MX records listed for
2111 the host mktmail.example.com using the new address harry@mkt.example.com
2114 dn: uid=virtual.example.com, o=example.com, c=US
2116 mailLocalAddress: @virtual.example.com
2117 mailHost: server.example.com
2118 mailRoutingAddress: virtual@example.com
2120 This would send all mail destined for any username @virtual.example.com to
2121 the machine server.example.com's MX servers and deliver to the address
2122 virtual@example.com on that relay machine.
2173 For example, if your server receives a recipient of user@domain.com
2227 <example.net!user@local.host> would be relayed to <user@example.net>.
2272 selected domains. For example, you may choose to reject all mail
2281 definition for the database; for example
2292 To:user@example.com RELAY
2298 map. For example:
2304 For example,
2332 requires a tag. For example,
2358 ruleset would reject it, for example, if the domain
2408 For example:
2417 Connect:suspicious.example.com QUARANTINE:Mail from suspicious host
2434 error code to match it. For example, if you use
2436 To:user@example.com ERROR:450 mailbox full
2448 then the above example will allow relaying for sendmail.org, but not
2453 the username portion of the address. For example:
2479 as value part in the access map. Taking the example from above:
2491 FEATURE(`dnsbl', `dnsbl.example.com')
2502 text or action. For example,
2504 FEATURE(`dnsbl', `dnsbl.example.com', `quarantine')
2507 at `dnsbl.example.com'.
2513 example:
2515 FEATURE(`dnsbl', `dnsbl.example.com', `',
2516 `"451 Temporary lookup failure for " $&{client_addr} " in dnsbl.example.com"')
2546 example if you wanted to block senders with all numeric usernames
2640 in sendmail.cf. For example, this can be used to check the validity of
2677 example usage is to reject messages which do not have a Message-Id:
2679 not a guaranteed spam indicator. This ruleset is an example and should
2808 by their HEX value with a leading '+'. For example:
2928 Example: e-mail sent to secure.example.com should only use an encrypted
2929 connection. E-mail received from hosts within the laptop.example.com domain
2934 TLS_Srv:secure.example.com ENCR:112
2935 TLS_Clt:laptop.example.com PERM+VERIFY:112
2948 A default case can be specified by using just the tag. For example,
2977 LOCAL_RULESETS respectively. For example:
2990 respectively. For example, to add a local ruleset that decides
3012 name and equates. For example:
3024 For example, the two commands:
3076 For example:
3108 result. For example, in some environments gethostname returns
3143 For example, a mailertable file in text format might be:
3160 -- for example, even though ".my.domain" is listed first in the
3161 above example, an entry of "uuhost1.my.domain" will match the second
3173 the host name. For example, the first line above sends everything
3178 particularly on gateways. For example, you may want to MX
3216 example, the UNIX software-development community has at least two
3232 centralized mail machine, for example, to forward all
3236 using plussed users. For example, a client might include
3746 this. For example, if "FTP.Foo.ORG"
4132 each of which contains a single element of the class. For example,
4175 site dependent; for example, "CS.Berkeley.EDU.m4"