On 28 Nov 2017, at 21:09 (-0500), Viktor Dukhovni wrote:
On Tue, Nov 28, 2017 at 08:57:05PM -0500, Bill Cole wrote:
I fear that I've misunderstood something for a very long time...
Why might hwsrv-205226.hostwindsdns.com not be hitting the
(redundant, I
think) entries here?
The postmap(1) command does not support any of the partial key
lookups performed by Postfix when doing access(5), transport(5),
virtual(5), generic(5), ... lookups. Indeed not all these
higher-level
map types generate partial keys in the same way. So postmap cannot
without further (not-yet implemented options) know how to do these
lookups.
Which also answers my unasked question: "Why isn't there a postmap
option to specify a lookup strategy?"
Thanks, Viktor. I have confirmed the desired behavior elsewise:
bigsky:~ root# telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 toaster.scconsult.com ESMTP Postfix
xclient name=hwsrv-205226.hostwindsdns.com
220 toaster.scconsult.com ESMTP Postfix
ehlo hwsrv-205226.hostwindsdns.com
250-toaster.scconsult.com
250-PIPELINING
250-SIZE 40960000
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250 SMTPUTF8
mail from:<>
250 2.1.0 Ok
rcpt to:<b...@scconsult.com>
550 5.7.1 <hwsrv-205226.hostwindsdns.com[127.0.0.1]>: Client host
rejected: Too many brute force attacks from your hosting provider
quit
221 2.0.0 Bye
Connection closed by foreign host.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Currently Seeking Steady Work: https://linkedin.com/in/billcole
