Mercurial > dovecot > original-hg > dovecot-1.2
diff dovecot-example.conf @ 2236:43b82a35888d HEAD
Dovecot can now connect to externally running dovecot-auth.
author | Timo Sirainen <tss@iki.fi> |
---|---|
date | Wed, 23 Jun 2004 20:50:43 +0300 |
parents | 58fc6765027c |
children | d2e186f716d8 |
line wrap: on
line diff
--- a/dovecot-example.conf Wed Jun 23 20:48:35 2004 +0300 +++ b/dovecot-example.conf Wed Jun 23 20:50:43 2004 +0300 @@ -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 +# } +# } +#}