On 13. Jul 2025, at 13.14, Genes Lists via dovecot <dovecot@dovecot.org> wrote:
> (iv) All worked smoothly aside from pigeonhole sieve. I encountered 2 > issues there. > > (a) non-root users need access to the certificate chain in order > to be able to run "sievec". Quirky but easy enough to work around. Which setting was it complaining about? ssl_client_* settings? or ssl_server_cert? > I have not been able to reproduce the core dump in non-production. > So the core dump seems to require having more clients perhaps and > remains an outstanding issue. > > Aki - any thoughts on the 'doveadm reload' crash? [1] > > [1] > https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/CFH55DNKPQAUBM2N7FKB6X7CK4M46KKH/ Hmm. Very strange. Seems to happen only when logging to syslog. Then it happens after running "doveadm reload" twice. I don't understand why it happens though. Seems to be some kind of memory corruption but of course it doesn't happen when running with valgrind. Need to try to debug further tomorrow. Answering some more comments in the thread also: Benny: > postfix never did incompatibel upgrade configs, never as ever, so why did > dovecot try this now ? v1.x config lasted for 8 years. v2.x config lasted for 15 years. It was getting kludgy enough that it was finally time to change it. > positive here it could add doveconf 2.3 config reader in dovecot 2.4, so 2.4 > understands both 2.3 and 2.4, this will hold back any questions how to > upgrade just like it have never being a problem with postfix, if postfix did > something like this i would propperly be still running postfix version 1.0 :=) There are unfortunately some differences between v2.3 and v2.4 that simple automatic config conversion wouldn't be possible in all situations. Especially settings coming from userdb lookups work a bit differently now. Andreas: > There is nothing comparable I can simply buy from OX for a few EUR per month > per organization, isn't it? (sorry for the direct CC at Aki, but I want to > make sure this question is not read over) Currently nothing I'm aware of. The main trouble is people paying for Dovecot would expect some kind of support, especially for difficult questions, which would then go all the way to development team to figure out, and take time out of development. In theory we could of course grow the development team, but that's a lot of trouble as well. _______________________________________________ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
