Hi, Yes, that makes sense, of course. I guess I'm confused as to how all the different queries are used.
So, iterate_query is required which, as far as I understand, in turn uses userdb query in order to look up UID, GID and mail location, but I defined those globally, so can I not skip the userdb query and have iterate_query just fall back to the global values somehow? Listing commands fail if I don't define a userdb query, so to make it work I use a query that returns some irrelevant field, and the commands indicate the global values, as expected. If yes, do I still need the userdb query for LMTP, while using prefetch? The page on prefetch says that "a valid userdb" is still required when using LDA or LMTP. A static userdb should still be a valid one, I reckon. Also, the static userdb section mentions that LDA "of course doesn't work with static userdb because there is no list of users", but that "normally static userdb handles this by doing a passdb lookup instead". I don't know whether this would be something that would apply to LMTP, as well, nor what "normally" means, exactly. I also have not been able to find any information regarding what data LMTP needs the userdb query to return. _______________________________________________ dovecot mailing list -- [email protected] To unsubscribe send an email to [email protected]
