ACCESS(5) | ACCESS(5) |
postmap -q "string" /etc/postfix/access
postmap -q - /etc/postfix/access <inputfile
Normally, the access(5) table is specified as a text file that serves as input to the postmap(1) command. The result, an indexed file in dbm or db format, is used for fast searching by the mail system. Execute the command " postmap /etc/postfix/access" to rebuild an indexed file after changing the corresponding text file.
When the table is provided via other means such as NIS, LDAP or SQL, the same lookups are done as for ordinary indexed files.
Alternatively, the table can be provided as a regular-expression map where patterns are given as regular expressions, or lookups can be directed to TCP-based server. In those cases, the lookups are done in a slightly different way as described below under "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
pattern action | When pattern matches a mail address, domain or host address, perform the corresponding action. |
blank lines and comments | Empty lines and whitespace-only lines are ignored, as are lines whose first non-whitespace character is a `#'. |
multi-line text | A logical line starts with non-whitespace text. A line that starts with whitespace continues a logical line. |
user@domain | Matches the specified mail address. |
domain.tld |
Matches domain.tld as the domain part of an email address. |
.domain.tld | Matches subdomains of domain.tld, but only when the string smtpd_access_maps is not listed in the Postfix parent_domain_matches_subdomains configuration setting. |
user@ | Matches all mail addresses with the specified user part. |
Note: lookup of the null sender address is not possible with some types of lookup table. By default, Postfix uses <> as the lookup key for such addresses. The value is specified with the smtpd_null_access_lookup_key parameter in the Postfix main.cf file.
domain.tld |
Matches domain.tld. |
.domain.tld | Matches subdomains of domain.tld, but only when the string smtpd_access_maps is not listed in the Postfix parent_domain_matches_subdomains configuration setting. |
net.work.addr.ess |
net.work.addr |
net.work |
net |
Matches the specified IPv4 host address or subnetwork. An IPv4 host address is a sequence of four decimal octets separated by ".". Subnetworks are matched by repeatedly truncating the last ".octet" from the remote IPv4 host address string until a match is found in the access table, or until further truncation is not possible. NOTE 1: The access map lookup key must be in canonical form: do not specify unnecessary null characters, and do not enclose network address information with "[]" characters. NOTE 2: use the cidr lookup table type to specify network/netmask patterns. See cidr_table(5) for details. |
net:work:addr:ess |
net:work:addr |
net:work |
net |
Matches the specified IPv6 host address or subnetwork. An IPv6 host address is a sequence of three to eight hexadecimal octet pairs separated by ":". Subnetworks are matched by repeatedly truncating the last ":octetpair" from the remote IPv6 host address string until a match is found in the access table, or until further truncation is not possible. NOTE 1: the truncation and comparison are done with the string representation of the IPv6 host address. Thus, not all the ":" subnetworks will be tried. NOTE 2: The access map lookup key must be in canonical form: do not specify unnecessary null characters, and do not enclose network address information with "[]" characters. NOTE 3: use the cidr lookup table type to specify network/netmask patterns. See cidr_table(5) for details. IPv6 support is available in Postfix 2.2 and later. |
OK | Accept the address etc. that matches the pattern. |
all-numerical | An all-numerical result is treated as OK. This format is generated by address-based relay authorization schemes such as pop-before-smtp. |
4NN text |
5NN text |
Reject the address etc. that matches the pattern, and respond with the numerical three-digit code and text. 4NN means "try again later", while 5NN means "do not try again". The following responses have special meaning for the Postfix SMTP server: |
421 text (Postfix 2.3 and later) |
521 text (Postfix 2.6 and later) | After responding with the numerical three-digit code and text, disconnect immediately from the SMTP client. This frees up SMTP server resources so that they can be made available to another SMTP client. |
Note: The "521" response should be used only with botnets and other malware where interoperability is of no concern. The "send 521 and disconnect" behavior is NOT defined in the SMTP standard. |
REJECT optional text... | Reject the address etc. that matches the pattern. Reply with " $access_map_reject_code optional text..." when the optional text is specified, otherwise reply with a generic error response message. |
DEFER optional text... |
Reject the address etc. that matches the pattern. Reply with " $access_map_defer_code optional text..." when the optional text is specified, otherwise reply with a generic error response message. |
DEFER_IF_REJECT optional text... |
Defer the request if some later restriction would result in a REJECT action. Reply with " $access_map_defer_code 4.7.1 optional text..." when the optional text is specified, otherwise reply with a generic error response message. |
DEFER_IF_PERMIT optional text... |
Defer the request if some later restriction would result in a an explicit or implicit PERMIT action. Reply with " $access_map_defer_code 4.7.1 optional text..." when the optional text is specified, otherwise reply with a generic error response message. |
restriction... | Apply the named UCE restriction(s) (permit, reject, reject_unauth_destination, and so on). |
BCC user@domain |
Send one copy of the message to the specified recipient. |
DISCARD optional text... |
Claim successful delivery and silently discard the message. Log the optional text if specified, otherwise log a generic message. |
DUNNO |
Pretend that the lookup key was not found. This prevents Postfix from trying substrings of the lookup key (such as a subdomain name, or a network address subnetwork). |
FILTER transport:destination |
After the message is queued, send the entire message through the specified external content filter. The transport name specifies the first field of a mail delivery agent definition in master.cf; the syntax of the next-hop destination is described in the manual page of the corresponding delivery agent. More information about external content filters is in the Postfix FILTER_README file. |
HOLD optional text... |
Place the message on the hold queue, where it will sit until someone either deletes it or releases it for delivery. Log the optional text if specified, otherwise log a generic message. Mail that is placed on hold can be examined with the postcat(1) command, and can be destroyed or released with the postsuper(1) command. |
PREPEND headername: headervalue |
Prepend the specified message header to the message. When more than one PREPEND action executes, the first prepended header appears before the second etc. prepended header. |
REDIRECT user@domain |
After the message is queued, send the message to the specified address instead of the intended recipient(s). |
WARN optional text... |
Log a warning with the optional text, together with client information and if available, with helo, sender, recipient and protocol information. |
• | When a sender address matches a REJECT action, the Postfix SMTP server will transform a recipient DSN status (e.g., 4.1.1-4.1.6) into the corresponding sender DSN status, and vice versa. |
• | When non-address information matches a REJECT action (such as the HELO command argument or the client hostname/address), the Postfix SMTP server will transform a sender or recipient DSN status into a generic non-address DSN status (e.g., 4.0.0). |
Each pattern is a regular expression that is applied to the entire string being looked up. 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, nor is user+foo broken up into user and foo.
Patterns are applied in the order as specified in the table, until a pattern is found that matches the search string.
Actions are the same as with indexed file lookups, with the additional feature that parenthesized substrings from the pattern can be interpolated as $1, $2 and so on.
Each lookup operation uses the entire query string once. 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, nor is user+foo broken up into user and foo.
Actions are the same as with indexed file lookups.
/etc/postfix/main.cf:
smtpd_client_restrictions =
check_client_access hash:/etc/postfix/access
/etc/postfix/access:
1.2.3 REJECT
1.2.3.4 OK
Execute the command "postmap /etc/postfix/access" after editing the file.
August 25, 2011 |