--- a/doc/dovecot-ldap.conf	Sat Dec 10 21:44:45 2005 +0200
+++ b/doc/dovecot-ldap.conf	Sat Dec 10 22:36:18 2005 +0200
@@ -53,6 +53,12 @@
 #  password: Password, may optionally start with {type}, eg. {crypt}
 #pass_attrs = uid=user,userPassword=password
 
+# If you wish to avoid two LDAP lookups (passdb + userdb), you can use
+# userdb prefetch instead of userdb ldap in dovecot.conf. In that case you'll
+# also have to include user_attrs in pass_attrs field prefixed with "userdb_"
+# string. For example:
+#pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid
+
 # Filter for password lookups
 #pass_filter = (&(objectClass=posixAccount)(uid=%u))
 

--- a/doc/dovecot-sql.conf	Sat Dec 10 21:44:45 2005 +0200
+++ b/doc/dovecot-sql.conf	Sat Dec 10 22:36:18 2005 +0200
@@ -95,3 +95,9 @@
 #   user_query = SELECT home, 501 AS uid, 501 AS gid FROM users WHERE userid = '%u'
 #
 #user_query = SELECT home, uid, gid FROM users WHERE userid = '%u'
+
+# If you wish to avoid two SQL lookups (passdb + userdb), you can use
+# userdb prefetch instead of userdb sql in dovecot.conf. In that case you'll
+# also have to return userdb fields in password_query prefixed with "userdb_"
+# string. For example:
+#password_query = SELECT userid as user, password, home as userdb_home, uid as userdb_uid, gid as userdb_gid FROM users WHERE userid = '%u'

--- a/dovecot-example.conf	Sat Dec 10 21:44:45 2005 +0200
+++ b/dovecot-example.conf	Sat Dec 10 22:36:18 2005 +0200
@@ -729,7 +729,8 @@
 
   # "prefetch" user database means that the passdb already provided the
   # needed information and there's no need to do a separate userdb lookup.
-  # This can be made to work with SQL and LDAP databases.
+  # This can be made to work with SQL and LDAP databases, see their example
+  # configuration files for more information how to do it.
   # http://wiki.dovecot.org/AuthSpecials
   #userdb prefetch {
   #}