--- a/dovecot-example.conf	Wed Dec 29 18:28:31 2004 +0200
+++ b/dovecot-example.conf	Wed Dec 29 19:02:47 2004 +0200
@@ -92,6 +92,7 @@
 # User to use for the login process. Create a completely new user for this,
 # and don't use it anywhere else. The user must also belong to a group where
 # only it has access, it's used to control access for authentication process.
+# Note that this user is NOT used to access mails.
 #login_user = dovecot
 
 # Set max. process size in megabytes. If you don't use
@@ -534,7 +535,8 @@
   #   plain digest-md5 cram-md5 apop anonymous
   mechanisms = plain
 
-  # Where user database is kept:
+  # User database specifies where mails are located and what user/group IDs
+  # own them. For single-UID configuration use "static".
   #   passwd: /etc/passwd or similiar, using getpwnam()
   #   passwd-file <path>: passwd-like file with specified location
   #   static uid=<uid> gid=<gid> home=<dir template>: static settings
@@ -543,7 +545,7 @@
   #   sql <config path>: SQL database, see doc/dovecot-sql.conf
   userdb = passwd
 
-  # Where password database is kept:
+  # Password database specifies only the passwords for users.
   #   passwd: /etc/passwd or similiar, using getpwnam()
   #   shadow: /etc/shadow or similiar, using getspnam()
   #   pam [<service> | *]: PAM authentication
@@ -558,7 +560,8 @@
   # password databases, nothing else. Only shadow and pam authentication
   # requires roots, so use something else if possible. Note that passwd
   # authentication with BSDs internally accesses shadow files, which also
-  # requires roots.
+  # requires roots. Note that this user is NOT used to access mails.
+  # That user is specified by userdb above.
   user = root
 
   # Directory where to chroot the process. Most authentication backends don't