PowerMTA automatically expands that to aol.com, aol.de, and aol.co.uk. domain-macro topLevel com, de, co.ukĪnd then use it in the tag ttings.
To use this feature, you would first define a domain macro with the desired list of bindings. & .uk), PowerMTA has the ability to define top level domain macros. To include domains that have different root domains (e.g.
bounce-after 1h log-commands yes bounce-after 4d bounce-after 6d In the following example, commands will be logged for all proper subdomains of (but not for itself) and undelivered messages to any address at will bounce after four days, except for messages to, which will bounce after one hour. When PowerMTA reads the configuration file, it merges settings for related domains from more general to more specific domains, so you can provide defaults for all domains by specifying them for the "*" pseudo-domain or for a specific site by specifying them for the toplevel domain for the site. When PowerMTA needs to determine what parameters to use for a specific domain, it uses the best matching (most specific) entry, regardless of the order domain directives are placed into the configuration file. Domain directives may be added in any order to the configuration file. matches all domains in dotted decimal format. The actual IP address in the domain must match the given CIDR specification (ip prefix and mask number of significant bits). Matches domains in the dotted decimal format, like. domain Matches domain as well as its subdomains. *.domain Matches any subdomains of domain, but not the domain itself. domain A single, fully qualified domain name.
The directive should be specified within a entry, like in bounce-after 6d ĭomains can be specified in one of the following formats: * Matches all domains. Directives Defined The directive affects items (like e-mail queued, outgoing connections, etc.) related to the specified domain name. and are reserved and the only two tags that should use &. If using a pickup directory, the format is. parameter of the smtp-listener directive. They apply only when specifically requested, like in the source=. Named entries are used to override the settings obtained based on the source IP address. Still, contrary to the domain entries, source entries cannot be automatically sorted, which is why you need to specify them in the order you wish them used. Note that PowerMTA merges ("inherits") settings in source entries like it does for the domain entries, allowing you to provide defaults in a more generic entry (such as 0/0 ). The first matching entry for any directive is used, so it is important to enter them in the proper order - from more specific to more general, as in the example below: # matches 10.0.0.5 only. Source entries are scanned sequentially by PowerMTA when a new incoming connection request is received.
A entry to be applied by name specifies its name in the entry, like in. In the example above, only the first eight bits (the 10 portion) are significant, so any IP addresses starting with 10. CIDR specifications are formed by an IP address prefix and by the number of significant bits within the 32-bit number formed by the prefix. Each entry to be applied by IP address specifies either an IP address in dotted decimal notation (like 10.0.0.1 ), or a range of IP addresses in CIDR notation (like 10.0.0.0/8 ). Per-source directives can be specified in two ways: by IP address and by name. The directive should be specified within a entry, like in log-connections yes Directives Defined The directive affects incoming SMTP connections from the given source.