[dovecot-cvs] dovecot dovecot-example.conf,1.98,1.99

[cras at procontrol.fi]

Update of /home/cvs/dovecot
In directory talvi:/tmp/cvs-serv5259

Modified Files:
	dovecot-example.conf 
Log Message:
Dovecot can now connect to externally running dovecot-auth.



Index: dovecot-example.conf
===================================================================
RCS file: /home/cvs/dovecot/dovecot-example.conf,v
retrieving revision 1.98
retrieving revision 1.99
diff -u -d -r1.98 -r1.99
--- dovecot-example.conf	23 Jun 2004 15:00:24 -0000	1.98
+++ dovecot-example.conf	23 Jun 2004 17:50:43 -0000	1.99
@@ -484,3 +484,43 @@
 #  passdb = passwd-file /etc/passwd.imap
 #  user = dovecot-auth
 #}
+
+# It's possible to export the authentication interface to other programs,
+# for example SMTP server which supports talking to Dovecot. Client socket
+# handles the actual authentication - you give it a username and password
+# and it returns OK or failure. So it's pretty safe to allow anyone access to
+# it. Master socket is used to a) query if given client was successfully
+# authenticated, b) userdb lookups.
+
+# listener sockets will be created by Dovecot's master process using the
+# settings given inside the auth section
+#auth default_with_listener {
+#  mechanisms = plain
+#  passdb = passwd
+#  userdb = pam
+#  socket listen {
+#    master {
+#      path = /var/run/dovecot/auth-master
+#      #mode = 0600
+#      # Default user/group is the one who started dovecot-auth (root)
+#      #user = 
+#      #group = 
+#    }
+#    client {
+#      path = /var/run/dovecot-auth-client
+#      mode = 0660
+#    }
+#  }
+#}
+
+# connect sockets are assumed to be already running, Dovecot's master
+# process only tries to connect to them. They don't need any other settings
+# than path for the master socket, as the configuration is done elsewhere.
+# Note that the client sockets must exist in login_dir.
+#auth external {
+#  socket connect {
+#    master {
+#      path = /var/run/dovecot/auth-master
+#    }
+#  }
+#}