OK, I understand, it looks like we have the additional line which is wrong... must have pasted it in by accident, the correct line is the one below which is check_recipient_access hash:/etc/postfix/mx_access
Thank you! On Sat, Jan 31, 2015 at 7:09 AM, li...@rhsoft.net <li...@rhsoft.net> wrote: > > Am 31.01.2015 um 05:49 schrieb Joey J: > >> I'm getting the following when I start postfix ( literally that many >> times) >> >> /usr/sbin/postconf: warning: /etc/postfix/main.cf <http://main.cf>: >> unused parameter: mx_access=hash:/etc/postfix/mx_access >> >> Here is a section of my configuration, I cant' seem to figure out what >> I'm doing wrong. >> >> -------------------------------------- >> virtual_maps = hash:/etc/postfix/virtual >> hash:/etc/postfix/local-host-names >> >> alias_maps = hash:/etc/postfix/aliases >> mx_access = hash:/etc/postfix/mx_access >> relay_domains = /etc/postfix/backup_domains >> transport_maps = hash:/etc/postfix/transport, >> hash:/etc/postfix/transport_bounce >> relay_recipient_maps = hash:/etc/postfix/backup_domains_recipients, >> hash:/etc/postfix/transport_recipients >> > > as postfix telss you "mx_access = hash:/etc/postfix/mx_access" is the only > line where you use it which is pointless until a variable is used in a > smtpd_*_restricitions or somewhere else > > in other words: there is no such config parameter directly in main.cf > because postfix needs to know *where* to apply it and in which order > > go to that page, type CTRL+F followed by "mx_access" > http://www.postfix.org/postconf.5.html > > check_client_mx_access type:table > Search the specified access(5) database for the MX hosts for the client > hostname, 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.7 > and later. > -- Thanks! Joey
