On 28. Jan 2025, at 0.35, Mike Panev via dovecot <dovecot@dovecot.org> wrote:
Timo Sirainen wrote:
Our documentation is written using github pull requests, so anybody can easily do changes as little or as much as wanted. https://github.com/dovecot/documentation/
I know, but I assumed only a limited (pre-approved) list of contributors can commit patches,
Anyone can create pull requests, but only a few people can actually merge them.
that't why to be honest, I never cared to do a research on your "contribing policy"... which is *presumably* also documented somewhere :-)
Well, we have a https://doc.dovecot.org/2.4.0/license.html page, but I guess we don't more clearly document contributions. Maybe because there haven't really been many lately. But since there is nothing, I think it means simply you keep the copyright but accept that it's licensed with this license.
Yes, either that or I think fields { noauthenticate = yes } would also work.
I thought noauthenticate refers only to passdb's? To my understanding the effect of this is to just apply any passdb extra fields - notably, even if the password doesn't match - and then do the actual authentication in the following passdbs.
Right, I somehow kept thinking about passdbs only.
Then it would need to be inside protocol lmtp {} or otherwise IMAP auths without domains would fail.
Great, yet another new thing for me - never thought that user/passdb's can be inside filter sections! Does the filtering preserve the cascading order?
Updated documentation for that: https://github.com/dovecot/documentation/pull/1151
That is, does this work (pseudo code):
passdb passwd-file-without-domains protocol lmtp { userdb drop-domain-for-valid-domains } userdb same-passwd-file-as-passdb
This should work, because protocol lmtp-specific userdb is run before the global one. Regardless of in which order they are in config file.