Re: TLV problem after updating to 2.1.14

2020-04-12 Thread Hativ
Am Sonntag, den 12.04.2020, 18:19 +0200 schrieb Willy Tarreau: > Hello Hativ, > On Sun, Apr 12, 2020 at 09:49:02AM +0200, Hativ wrote: > > Hello Willy, > > > Hativ, if I send you a patch to test next week, is it possible > > > togiveit a try on your si

Re: TLV problem after updating to 2.1.14

2020-04-12 Thread Hativ
Hello Willy, > Hativ, if I send you a patch to test next week, is it possible to > give > it a try on your side ? I'm interested in knowing if a clean "LOCAL" > connection works fine with Dovecot. If so then in parallel we can > file > a report on Dovecot to m

Re: TLV problem after updating to 2.1.14

2020-04-04 Thread Hativ
Hello Willy, > Hativ, if I send you a patch to test next week, is it possible to > give > it a try on your side ? I'm interested in knowing if a clean "LOCAL" > connection works fine with Dovecot. If so then in parallel we can > file > a report on Dovecot to m

Re: TLV problem after updating to 2.1.14

2020-04-04 Thread Hativ
the cause of this? Something wrong with the commit or is Dovecot wrong? -- Greetings Hativ Am Freitag, den 03.04.2020, 11:27 +0200 schrieb Tim Düsterhus: > Hativ, > Am 03.04.20 um 00:38 schrieb Hativ: > > Any ideas what's wrong? > > I would assume that this patch changed the behav

TLV problem after updating to 2.1.14

2020-04-02 Thread Hativ
check resolvers dns send-proxy-v2 backup > timeout connect 5s > timeout client 30m > timeout server 30m When commenting out these lines it's up again: > option tcp-check > tcp-check connect port 993 send-proxy ssl > tcp-check expect string * OK Any ideas what's wrong? -- Greetings Hativ