Re: Configuring master password when using pam/openldap [was: "running alternate dovecot instances on the same server"]

2022-06-21 Thread Chris Hoogendyk
So this is resolved. Turns out that getting rid of the "result_success = continue" fixed it. Which is odd, because I thought from the documentation that that was required. Anyway. Fixed. On 6/20/22 2:53 PM, Chris Hoogendyk wrote: Hoping that someone can help with this. It's a critical projec

Re: Configuring master password when using pam/openldap [was: "running alternate dovecot instances on the same server"]

2022-06-21 Thread Chris Hoogendyk
Hoping that someone can help with this. It's a critical project that requires getting the master password to work. I've managed to get the logging at maximum level and what I'm seeing is the following. Testing with: chrisho@marlin:~$ telnet localhost 143 Trying 127.0.0.1... Connected

Doveadm http requests - payload size

2022-06-21 Thread Tony Hartmann - WebBoty
Hello Team, We are running dovecot version (2.3.7.2 (3c910f64b)) on ubuntu 20.04. Using the doveadm tool via http api we can create emails and move them accordingly to the draft folder by sending http requests via cURL from another server. We can even attach files. However once we create a htt

dovecot and openssl3

2022-06-21 Thread A. Schulze
Hello, I tried to build dovecot-2.3.19.1 with openssl-3.0.2 "make test" failed. Good, the test-suite found a problem! I found similar reports and patches: - https://sources.debian.org/src/dovecot/1%3A2.3.19%2Bdfsg1-1/debian/patches/Support-openssl-3.0.patch/ - https://bugzilla.redhat.com/show_b

Re: v2.3.19.1 released

2022-06-21 Thread Timo Sirainen
Also, nowadays Lua would be a better way to do custom authentication and we're more careful not to break that. > On 21. Jun 2022, at 13.47, Timo Sirainen wrote: > > Oh, I think your problem is that you've implemented a separate dict-server. > And looks like we forgot to mention in v2.3.17 rele

Re: v2.3.19.1 released

2022-06-21 Thread Timo Sirainen
Oh, I think your problem is that you've implemented a separate dict-server. And looks like we forgot to mention in v2.3.17 release notes that the dict protocol had to be changed due to some improvements. Your dict server should verify that the VERSION line's major version number is as expected,