Re: Postfix SMTP client: dealing with multiline EHLO response?

2019-06-25 Thread Viktor Dukhovni
Based on the details provided so far, I think you should turn the foozle-knob until the whatsit level drops. :-) > On Jun 25, 2019, at 11:09 PM, Warren Toomey wrote: > > One of my list members has his own SMTP server. He's configured it to return > a large multiline response to the initial EHLO

Postfix SMTP client: dealing with multiline EHLO response?

2019-06-25 Thread Warren Toomey
Hi all, first post on the list and I've spent some time searching the docs for an answer. One of my list members has his own SMTP server. He's configured it to return a large multiline response to the initial EHLO from a client. Apparently when my Postfix installation connects to him, it sits

Re: The Prefix Whois milter, with Postfix On FreeBSD?

2019-06-25 Thread David Mehler
Hello, Thanks, that did it. Thanks. Dave. On 6/25/19, Wietse Venema wrote: > David Mehler: >> Hello, >> >> Here is the complete run. >> >> Thanks. >> Dave. >> root@mail:~/pwhois_milter_1.4#make >> gmake[1]: Entering directory '/root/pwhois_milter_1.4' >> cc -pthread -Ofast -ggdb3 -Wall

Re: best practice lookup table perormance - non hashed file

2019-06-25 Thread Matus UHLAR - fantomas
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

Re: The Prefix Whois milter, with Postfix On FreeBSD?

2019-06-25 Thread Wietse Venema
David Mehler: > Hello, > > Here is the complete run. > > Thanks. > Dave. > root@mail:~/pwhois_milter_1.4#make > gmake[1]: Entering directory '/root/pwhois_milter_1.4' > cc -pthread -Ofast -ggdb3 -Wall -Wextra pwhois_milter.c -c > -I/usr/include -I/usr/local/include -o pwhois_milter.o > cc

Re: best practice lookup table perormance - non hashed file

2019-06-25 Thread Stefan Bauer
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

Re: The Prefix Whois milter, with Postfix On FreeBSD?

2019-06-25 Thread David Mehler
Hello, Here is the complete run. Thanks. Dave. root@mail:~/pwhois_milter_1.4#make gmake[1]: Entering directory '/root/pwhois_milter_1.4' cc -pthread -Ofast -ggdb3 -Wall -Wextra pwhois_milter.c -c -I/usr/include -I/usr/local/include -o pwhois_milter.o cc -pthread pwhois_milter.o -o pwhois_milter

Re: The Prefix Whois milter, with Postfix On FreeBSD?

2019-06-25 Thread Wietse Venema
David Mehler: > Hello, > > Has anyone got the Prefix Whois milter going with Postfix on a FreeBSD > system? I'm having compilation difficulties. If anyone has this going > please let me know. What is the error message?

The Prefix Whois milter, with Postfix On FreeBSD?

2019-06-25 Thread David Mehler
Hello, Has anyone got the Prefix Whois milter going with Postfix on a FreeBSD system? I'm having compilation difficulties. If anyone has this going please let me know. Thanks. Dave.

Re: Problem setting a TLS verified connection

2019-06-25 Thread sral...@gmail.com
Finally it start working No idea what was happening or what expect to receive the other server. It just start working but not idea which was the problem :( Thank you very much for your help. El 21/6/19 a las 23:07, Viktor Dukhovni escribió: On Thu, Jun 20, 2019 at 12:43:22PM +0200, David

Re: best practice lookup table perormance - non hashed file

2019-06-25 Thread Blake Hudson
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

Re: best practice lookup table perormance - non hashed file

2019-06-25 Thread Matus UHLAR - fantomas
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

Re: best practice lookup table perormance - non hashed file

2019-06-25 Thread Benny Pedersen
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

Re: Receiving mail from a host without a valid rDNS

2019-06-25 Thread Matus UHLAR - fantomas
On 24.06.19 08:04, @lbutlr wrote: I have a mail host that I want to receive mail from that dies not have a valid rDNS (it recently moved and their ISP is comcast and it seems to be taking a stupidly long time). Anyway, I first tried this: check_sender_access

Re: best practice lookup table perormance - non hashed file

2019-06-25 Thread Matus UHLAR - fantomas
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:

Re: Receiving mail from a host without a valid rDNS

2019-06-25 Thread joao
"Wietse Venema" – 25 de Junho de 2019 às 07:56 > @lbutlr: > > On 24 Jun 2019, at 08:56, Wietse Venema wrote: > > > elete reject_unknown_client_hostname, or add > > > > > > check_client_access inline:{1.2.3.4:ok} > > Should be: > > check_client_access inline:{1.2.3.4=ok} > > Argh. > >

Re: Receiving mail from a host without a valid rDNS

2019-06-25 Thread Wietse Venema
@lbutlr: > On 24 Jun 2019, at 08:56, Wietse Venema wrote: > > elete reject_unknown_client_hostname, or add > > > >check_client_access inline:{1.2.3.4:ok} Should be: check_client_access inline:{1.2.3.4=ok} Argh. Wietse