Postfix docs Search Results:

Looking for search in entire archive - Found 185 matches in 57 files
Showing results 1 - 25
Postfix Configuration Parameters, Feb 8 2008
The default list is system dependent. On systems with NIS, the default is to search the local alias database, then the NIS alias database.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a user name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a user name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
Search path for Cyrus SASL application configuration files, currently used only to locate the $smtpd_sasl_path.conf file.
Specify zero or more directories separated by a colon character, or an empty value to use Cyrus SASL's built-in search path.
The sender_dependent_relayhost_maps search string that will be used instead of the null sender address.
The local(8) delivery agent search list for finding a .forward file with user-specified delivery methods. The first file that is found is used.
The following $name expansions are done on forward_path before the search actually happens. The result of $name expansion is filtered with the character set that is specified with the forward_expansion_filter parameter.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
The list is matched left to right, and the search stops on the first match. Specify "!pattern" to exclude an address or network block from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
The table search order is as follows:
The table search order is as follows:
Search the specified access database for the client hostname, parent domains, client IP address, or networks obtained by stripping least significant octets. See the access(5) manual page for details.
Search the specified access database for the ETRN domain name or its parent domains. See the access(5) manual page for details.
Search the specified access(5) database for the HELO or EHLO hostname or parent domains, and execute the corresponding action.
Search the specified access(5) database for the MX hosts for the HELO or EHLO hostname, and execute the corresponding action.
Search the specified access(5) database for the DNS servers for the HELO or EHLO hostname, and execute the corresponding action.
Search the specified access(5) database for the resolved RCPT TO address, domain, parent domains, or localpart@, and execute the corresponding action.
Search the specified access(5) database for the MX hosts for the RCPT TO address, and execute the corresponding action. Note: a result of "OK" is not allowed for safety reasons. Instead, use DUNNO in order to exclude specific hosts from blacklists. This feature is available in Postfix 2.1 and later.
...limit of 20 lines reached, additional matching lines are not shown...

Postfix Configuration Parameters, Feb 8 2008
The default list is system dependent. On systems with NIS, the default is to search the local alias database, then the NIS alias database.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a user name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a user name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
Search path for Cyrus SASL application configuration files, currently used only to locate the $smtpd_sasl_path.conf file.
Specify zero or more directories separated by a colon character, or an empty value to use Cyrus SASL's built-in search path.
The sender_dependent_relayhost_maps search string that will be used instead of the null sender address.
The local(8) delivery agent search list for finding a .forward file with user-specified delivery methods. The first file that is found is used.
The following $name expansions are done on forward_path before the search actually happens. The result of $name expansion is filtered with the character set that is specified with the forward_expansion_filter parameter.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
The list is matched left to right, and the search stops on the first match. Specify "!pattern" to exclude an address or network block from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
The table search order is as follows:
The table search order is as follows:
Search the specified access database for the client hostname, parent domains, client IP address, or networks obtained by stripping least significant octets. See the access(5) manual page for details.
Search the specified access database for the ETRN domain name or its parent domains. See the access(5) manual page for details.
Search the specified access(5) database for the HELO or EHLO hostname or parent domains, and execute the corresponding action.
Search the specified access(5) database for the MX hosts for the HELO or EHLO hostname, and execute the corresponding action.
Search the specified access(5) database for the DNS servers for the HELO or EHLO hostname, and execute the corresponding action.
Search the specified access(5) database for the resolved RCPT TO address, domain, parent domains, or localpart@, and execute the corresponding action.
Search the specified access(5) database for the MX hosts for the RCPT TO address, and execute the corresponding action. Note: a result of "OK" is not allowed for safety reasons. Instead, use DUNNO in order to exclude specific hosts from blacklists. This feature is available in Postfix 2.1 and later.
...limit of 20 lines reached, additional matching lines are not shown...

Postfix Configuration Parameters, Feb 8 2008
The default list is system dependent. On systems with NIS, the default is to search the local alias database, then the NIS alias database.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a user name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a user name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
Search path for Cyrus SASL application configuration files, currently used only to locate the $smtpd_sasl_path.conf file.
Specify zero or more directories separated by a colon character, or an empty value to use Cyrus SASL's built-in search path.
The sender_dependent_relayhost_maps search string that will be used instead of the null sender address.
The local(8) delivery agent search list for finding a .forward file with user-specified delivery methods. The first file that is found is used.
The following $name expansions are done on forward_path before the search actually happens. The result of $name expansion is filtered with the character set that is specified with the forward_expansion_filter parameter.
Specify a list of user names, "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the first match. A "/file/name" pattern is replaced by its contents; a "type:table" lookup table is matched when a name matches a lookup key (the lookup result is ignored). Continue long lines by starting the next line with whitespace. Specify "!pattern" to exclude a name from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
The list is matched left to right, and the search stops on the first match. Specify "!pattern" to exclude an address or network block from the list. The form "!/file/name" is supported only in Postfix version 2.4 and later.
The table search order is as follows:
The table search order is as follows:
Search the specified access database for the client hostname, parent domains, client IP address, or networks obtained by stripping least significant octets. See the access(5) manual page for details.
Search the specified access database for the ETRN domain name or its parent domains. See the access(5) manual page for details.
Search the specified access(5) database for the HELO or EHLO hostname or parent domains, and execute the corresponding action.
Search the specified access(5) database for the MX hosts for the HELO or EHLO hostname, and execute the corresponding action.
Search the specified access(5) database for the DNS servers for the HELO or EHLO hostname, and execute the corresponding action.
Search the specified access(5) database for the resolved RCPT TO address, domain, parent domains, or localpart@, and execute the corresponding action.
Search the specified access(5) database for the MX hosts for the RCPT TO address, and execute the corresponding action. Note: a result of "OK" is not allowed for safety reasons. Instead, use DUNNO in order to exclude specific hosts from blacklists. This feature is available in Postfix 2.1 and later.
...limit of 20 lines reached, additional matching lines are not shown...

Postfix LDAP Howto, Feb 8 2008
server_host = ldap.example.com search_base = dc=example, dc=com
Upon receiving mail for a local address "ldapuser" that isn't found in the /etc/aliases database, Postfix will search the LDAP server listening at port 389 on ldap.example.com. It will bind anonymously, search for any directory entries whose mailacceptinggeneralid attribute is "ldapuser", read the "maildrop" attributes of those found, and build a list of their maildrops, which will be treated as RFC822 addresses to which the message will be delivered.
search_base = dc=example, dc=com query_filter = mail=%s result_attribute = memberaddr $ postmap -q agroup@example.com ldap:simple.cf auser@example.org,buser@example.org
We search "dc=example, dc=com". The "mail" attribute is used in the query_filter to locate the right group, the "result_attribute" setting described in ldap_table(5) is used to specify that "memberaddr" values from the matching group are to be returned as a comma separated list.
search_base = dc=example, dc=com query_filter = mail=%s result_attribute = maildrop special_result_attribute = memberdn $ postmap -q agroup@example.com ldap:special.cf auser@mailhub.example.com,buser@mailhub.example.com
search_base = dc=example, dc=com query_filter = mail=%s result_attribute = maildrop expand.cf ...
search_base = dc=example, dc=com query_filter = mail=%s result_attribute = maildrop special_result_attribute = memberdn $ postmap -q auser@example.com ldap:no_expand.cf ldap:expand.cf auser@mailhub.example.com $ postmap -q agroup@example.com ldap:no_expand.cf ldap:expand.cf auser@mailhub.example.com,buser@mailhub.example.com $ postmap -q bgroup@example.com ldap:no_expand.cf ldap:expand.cf bgroup@mlm.example.com
search_base = dc=example, dc=com query_filter = mail=%s result_attribute = memberaddr special_result_attribute = memberdn terminal_result_attribute = maildrop leaf_result_attribute = mail $ postmap -q auser@example.com ldap:fancy.cf auser@mailhub.example.com $ postmap -q cuser@example.com ldap:fancy.cf cuser@example.com $ postmap -q agroup@example.com ldap:fancy.cf auser@mailhub.example.com,buser@mailhub.example.com,auser@example.org,buser@example.org $ postmap -q bgroup@example.com ldap:fancy.cf bgroup@mlm.example.com
Carsten Hoeger: Search scope handling.
Victor Duchovni: ldap_bind() timeout. With fixes from LaMont Jones: OpenLDAP cache deprecation. Limits on recursion, expansion and search results size. LDAP connection sharing for maps differing only in the query parameters.
Gunnar Wrobel provided a first implementation of a feature to limit LDAP search results to leaf nodes only. Victor generalized this into the Postfix 2.4 "leaf_result_attribute" feature.

Postfix SASL Howto, Feb 8 2008
When sending mail, the Postfix SMTP client can look up the remote SMTP server hostname or destination domain (the address right-hand part) in a SASL password table, and if a username/password is found, it will use that username and password to authenticate to the remote SMTP server. And as of version 2.3, Postfix can be configured to search its SASL password table by the sender email address.
Postfix version 2.3 supports multiple ISP accounts. This can be useful when one person uses the same machine for work and for personal use, or when people with different ISP accounts share the same Postfix server. To make this possible, Postfix 2.3 supports per-sender SASL passwords and per-sender relay hosts. In the example below, Postfix will search the SASL password file by sender before it searches that same file by destination. Likewise, Postfix will search the per-sender relayhost file, and use the default relayhost

Salon.com Technology | How Big Blue fell for Linux, Feb 8 2008
Search Directory -->About Salon Table Talk Newsletters Advertise in Salon Investor Relations
Search
Salon Search Directory -->About Salon Table Talk Newsletters Advertise in Salon Investor Relations

Postfix Small/Home Office Hints and Tips, Feb 8 2008
Postfix version 2.3 supports multiple ISP accounts. This can be useful when one person uses the same machine for work and for personal use, or when people with different ISP accounts share the same Postfix server. To make this possible, Postfix 2.3 supports per-sender SASL passwords and per-sender relay hosts. In the example below, Postfix will search the SASL password file by sender before it searches that same file by destination. Likewise, Postfix will search the per-sender relayhost file, and use the default relayhost

Postfix Installation From Source Code, Feb 8 2008
On Solaris, the "make" command and other utilities for software development are in /usr/ccs/bin, so you MUST have /usr/ccs/bin in your command search path. If these files do not exist, install the development packages first. See the Solaris FAQ item "Which packages do I need to install to support a C compiler?".
If the command produces compiler error messages, it may be time to search the web or to ask the postfix-users@postfix.org mailing list, but be sure to search the mailing list archives first. Some mailing list archives are linked from http://www.postfix.org/.

Postfix Address Rewriting, Feb 8 2008
sender_bcc_maps = type:table Search the specified "type:table" lookup table with the envelope sender address for an automatic BCC address. This feature is available in Postfix 2.1 and later.
recipient_bcc_maps = type:table Search the specified "type:table" lookup table with the envelope recipient address for an automatic BCC address. This feature is available in Postfix 2.1 and later.

Postfix Address Rewriting, Feb 8 2008
sender_bcc_maps = type:table Search the specified "type:table" lookup table with the envelope sender address for an automatic BCC address. This feature is available in Postfix 2.1 and later.
recipient_bcc_maps = type:table Search the specified "type:table" lookup table with the envelope recipient address for an automatic BCC address. This feature is available in Postfix 2.1 and later.

The Standard: Behind the Big Blue Wall, Feb 8 2008
  SEARCH
  advanced search

sendmail.net:, Feb 8 2008
home search about us site map policies
search

Postfix Debugging Howto, Feb 8 2008
Be sure that gdb is in the command search path, and export XAUTHORITY so that X access control works, for example:
Be sure that gdb is in the command search path.

Postfix PCRE Support, Feb 8 2008
When Postfix searches a pcre: or regexp: lookup table, each pattern is applied to the entire input string. Depending on the application, that string is an entire client hostname, an entire client IP address, or an entire mail address. Thus, no parent domain or parent network search is done, "user@domain" mail addresses are not broken up into their user and domain constituent parts, and "user+foo" is not broken up into user and foo.

Postfix Address Rewriting, Feb 8 2008
sender_bcc_maps = type:table Search the specified "type:table" lookup table with the envelope sender address for an automatic BCC address. This feature is available in Postfix 2.1 and later.
recipient_bcc_maps = type:table Search the specified "type:table" lookup table with the envelope recipient address for an automatic BCC address. This feature is available in Postfix 2.1 and later.

Postfix and Mailman deliver enhanced e-mail security and performance, Feb 8 2008
Search

SecurityPortal - Kurt's Closet: Postfix - the Sendmail replacement, Feb 8 2008
Home | Search | Feedback | Privacy Policy | Advertise | About SecurityPortal

Sharing Software, IBM to Release Mail Program Blueprint, Feb 8 2008
Home | Site Index | Site Search | Forums | Archives | Marketplace

SecurityPortal - Postfix - The Sendmail replacement part II, Feb 8 2008
Home | Search | Feedback | Privacy Policy | Advertise | About SecurityPortal

Venema aims to make network software safe, Feb 8 2008
Search Central

Linux Journal, Feb 8 2008
head Contains the "Search" and "Contact Us" links.

Postfix Lookup Table Overview, Feb 8 2008
Be sure to exercise all the partial address or parent domain queries that are documented under "table search order" in the relevant manual page: access(5), canonical(5), virtual(5), transport(5), or under the relevant configuration parameter: mynetworks, relay_domains, parent_domain_matches_subdomains.

Postfix Bottleneck Analysis, Feb 8 2008
Having found the high volume domains, it is often useful to search the logs for recent messages pertaining to the domains in question.

http://www.postfix.org#online, Feb 8 2008

HEC Montréal: Deployment of a Large-Scale Mail Installation, Feb 8 2008


Limit of 25 files reached.
New Query: Rank by:
Search results by Webglimpse Advanced Site Search Engine