On Mo, Jun 01, 2020 at 20:28:12 -0700, PGNet Dev wrote:
for websites it seems that, for all practical purposes, ecc ssl certs are all
that's needed anymore
does the same hold true for smtp(d)?
That depends. The AVM Fritzbox for example can only use RSA, so if your
Fritzbox should send mail re
See POSTSCREEN_README for logging examples and explanation, also
on-line at http://www.postfix.org/POSTSCREEN_README.html.
That includes PASS NEW, PASS OLD, and if some example is missing.
please let me know.
Wietse
I route mail for a number of relay_domains - recipient addresses are
validated using verify via address_verify_transport
For *one* of these domains, I'd like to validate addresses using an ldap
map configured with relay_recipient_maps rather than smtp lookahead.
I have the ldap connection working
Is there a command-line tool that can simulate postfix's ip-matching syntax
with semicolons and double dots?
# echo "127.0.0.3"|grepcidr "127.0.0.[1;3;5]"
grepcidr: Not a valid pattern: 127.0.0.[1;3;5]
# echo "127.0.0.3"|grepcidr "127.0.0.[1..5]"
grepcidr: Not a valid pattern: 127.0.0.[1..5]
Jonathan Engbrecht:
> I route mail for a number of relay_domains - recipient addresses are
> validated using verify via address_verify_transport
>
> For *one* of these domains, I'd like to validate addresses using an ldap
> map configured with relay_recipient_maps rather than smtp lookahead.
>
>
Dominic Raferd:
> Is there a command-line tool that can simulate postfix's ip-matching syntax
> with semicolons and double dots?
>
> # echo "127.0.0.3"|grepcidr "127.0.0.[1;3;5]"
> grepcidr: Not a valid pattern: 127.0.0.[1;3;5]
> # echo "127.0.0.3"|grepcidr "127.0.0.[1..5]"
> grepcidr: Not a valid
