On Sat, 2010-09-25 at 15:23 +0200, Axel Luttgens wrote:
Let's say one has a SQL table with following fields for John Doe:
login: u0007 password: {SHA1}... mailhome: /path/to/joeshome email: john.doe@example.com
To log in, for internal policy reasons, John MUST make use of his userid "u0007". So, in the password_query, one would need something like:
... WHERE login = '%u' ...
On the other hand, for receiving mail thru say, LMTP, one would need something like this in the user_query:
... WHERE email = '%Lu' ...
You could make it so that password_query changes the username to email by selecting "email AS user" and then user_query has only the email='% Lu'. Or you could make your user_query have "where (email='%Lu' or user='%u').
I can't manage to devise a way to systematically refer to users thru their login, nor to avoid such messages:
prefetch(u0007): passdb didn't return userd entries, trying the next userdb
This seems like a different problem to me..