dovecot - Jun 2004 - configuration

I've noticed that there are some parameters mentioned in the docs that 
aren't identified therein (ie: login_process_per_use).

Is there a more generic set of docs that can identify what each of the 
parameters and what they do, or at least something that will allow me a 
simple how to to avoid embarrasing situations.

I supposed I should only settle for ssl based connections (imaps/pops) 
but I will be open to digest-md5 if I could.

I'm also curious to see how I can use pgsql authentication with dovecot. 
  I think this would be great to work with since I'm basing all my 
postfix settings around postgresql as well.  But for now I'm not sure 
how to use postfix authentication with the file directories I'll need to 
use for the maildirs (and procmail!).

On Tue, 2004-06-08 at 03:06, Tom Allison wrote:
> I supposed I should only settle for ssl based connections (imaps/pops) 
> but I will be open to digest-md5 if I could.
If SSL is already enabled, the only gain from DIGEST-MD5 or CRAM-MD5 is
that server never actually sees the plaintext password. So it's mostly
useful if you use the same password in multiple places and don't really
trust your server.
> I'm also curious to see how I can use pgsql authentication with
dovecot.
I guess you already saw
http://wiki.dovecot.org/moin.cgi/DovecotPostgresql ? That explains how I
configured them.
>   I think this would be great to work with since I'm basing all my 
> postfix settings around postgresql as well.  But for now I'm not sure 
> how to use postfix authentication with the file directories I'll need
to
> use for the maildirs (and procmail!).
File directories?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20040610/4448bd25/attachment-0001.bin>