On Thu, 2006-08-10 at 20:33 +0300, Timo Sirainen wrote:
On Thu, 2006-08-10 at 11:23 -0500, Rick Romero wrote:
- POP? It gets compiled in automatically, yet doesn't start. Doesn't bother me, as I'm just using IMAP, but it doesn't seem logical. If POP doesn't start by default, I wouldn't think it would be compiled in by default.
Well, I think compiling and using by default are different things. Compiling everything by default doesn't really hurt anything, but using all of them by default does.
The only reason I suggested selective compiling is to help with the config file. It has so much to it, if you were able to reduce the 'unnecessary' bits based on the configure line, it wouldn't be so overwhelming. Look at the last post where the user had about 12 'real' lines to his config file. My modified one (comments and extra stuff left in there) is 1000 lines. I bet for a 'vpopmail/maildir' setup, it could be under 100 and still be descriptive.
I think most of the parts that can be compiled off don't take all that much space in the config file. Here's the config file split that I was thinking about, probably missing some of the latest changes:
http://dovecot.org/tmp/newconf/
The dovecot-example.conf should also contain some include-directives for the other files.
Oh, I don't know about anyone else, but I like that. Except for safety.conf (which I believe you need the login_user - maybe that's just me), it's pretty obvious what you really need to fill out to fire up dovecot and check it out.
I think the auth part is probably the worst section. It doesn't look so bad on a webpage, but in a terminal it's daunting.
- Maybe if the options were tagged with 'REQUIRED' or something.
- Or how about specifying 'select one passdb and one userdb' at the beginning of auth default { ?
I think just having passdb and userdb is initially confusing as well, but there's not much you can do about that, other that specifically saying what is required.
There's just so much data, and nothing really jumps out at you ;)
Rick