On 24.06.19 21:42, Stefan Bauer wrote:
>we're publishing lookup tables through our control git repo but hashing all
>tables before commiting them to git is cumbersome. What do you recommend?
Am Di., 25. Juni 2019 um 13:34 Uhr schrieb Matus UHLAR - fantomas <
uh...@fantomas.sk>:
you can try
Thank you for your answer, but this brings in another piece of software.
Want to keep it simple.
Am Di., 25. Juni 2019 um 13:34 Uhr schrieb Matus UHLAR - fantomas <
uh...@fantomas.sk>:
> On 24.06.19 21:42, Stefan Bauer wrote:
> >we're publishing lookup tables through our control git repo but
Matus UHLAR - fantomas wrote on 6/25/2019 6:34 AM:
On 24.06.19 21:42, Stefan Bauer wrote:
we're publishing lookup tables through our control git repo but
hashing all
tables before commiting them to git is cumbersome. What do you
recommend?
...
Whate do you recommend?
you can try rbldnsd
Matus UHLAR - fantomas skrev den 2019-06-25 13:34:
I'm aware of http://www.postfix.org/DATABASE_README.html#types
but none of them look simple. we like it plain and simple. No db
or ldap or
another instance, that could go wild.
Whate do you recommend?
you can try rbldnsd and
Matus UHLAR - fantomas skrev den 2019-06-25 13:34:
I'm aware of http://www.postfix.org/DATABASE_README.html#types
but none of them look simple. we like it plain and simple. No db or
ldap or
another instance, that could go wild.
Whate do you recommend?
you can try rbldnsd and
On 24.06.19 21:42, Stefan Bauer wrote:
we're publishing lookup tables through our control git repo but hashing all
tables before commiting them to git is cumbersome. What do you recommend?
several postfix servers are getting same lookup table from central
repository.
we're using it this ways:
Hi,
we're publishing lookup tables through our control git repo but hashing all
tables before commiting them to git is cumbersome. What do you recommend?
several postfix servers are getting same lookup table from central
repository.
we're using it this ways:
smtpd_sender_restrictions =
