Re: best practice lookup table perormance - non hashed file
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 rbldnsd and reject_rhsbl_client. On 25.06.19 19:45, Stefan Bauer wrote: Thank you for your answer, but this brings in another piece of software. Want to keep it simple. avoiding software that perfectly fits required functionality doesn't necessarily make solution simple. Especially when your present "simple" solution requires hashing tables prior to commit. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. "One World. One Web. One Program." - Microsoft promotional advertisement "Ein Volk, ein Reich, ein Fuhrer!" - Adolf Hitler
Re: best practice lookup table perormance - non hashed file
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 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 = check_sender_access > >hash:/etc/postfix/allowed_senders > > > >mail-addy or domain OK > >... > > > >with 600 entries so far. > > > >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 reject_rhsbl_client. > > -- > Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ > Warning: I wish NOT to receive e-mail advertising to this address. > Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. > 2B|!2B, that's a question! >
Re: best practice lookup table perormance - non hashed file
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 and reject_rhsbl_client. +1 We manage many servers and found using rbldnsd made centralized management much easier for managing our lists. It wasn't terrible to setup. We used a dedicated zone, two dedicated rbldnsd servers, and an rsync cronjob to keep the servers in sync. rbldnsd automatically picks up on changes to zone files and reloads them. It's not as fast as a local lookup table, but it doesn't need to be.
Re: best practice lookup table perormance - non hashed file
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 reject_rhsbl_client. On 25.06.19 14:06, Benny Pedersen wrote: postfix do support cidr rbldnsd supports more than CIDR. so rbldnsd is a bit overkill rbldnsd can be used on more levels than just postfix -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. WinError #9: Out of error messages.
Re: best practice lookup table perormance - non hashed file
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 reject_rhsbl_client. postfix do support cidr so rbldnsd is a bit overkill
Re: best practice lookup table perormance - non hashed file
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: smtpd_sender_restrictions = check_sender_access hash:/etc/postfix/allowed_senders mail-addy or domain OK ... with 600 entries so far. 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 reject_rhsbl_client. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. 2B|!2B, that's a question!
