The upstream dovecot-example.conf is essentially: --- $> grep -v '^ *\(#\|$\)' dovecot-example.conf protocol imap { } protocol pop3 { } auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } --- And, because of the builtin defaults, that's essentially the same as: --- auth default { passdb pam { } userdb passwd { } } --- What's nice about this is that people can start with the above simple config file and make the few changes they need for their system. However, Fedora's dovecot-example.conf is: --- $> grep -v '^ *#' /etc/dovecot.conf | grep -v ^$ protocols = imap imaps pop3 pop3s listen = [::] ssl_listen = [::] ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem ssl_key_file = /etc/pki/dovecot/private/dovecot.pem mbox_read_locks = fcntl mbox_write_locks = fcntl protocol imap { } protocol pop3 { } auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } --- It would be much nicer IMHO if we made these changes in the builtin defaults rather than in the example configuration. Attaching an untested patch to do this. Note: - No need to change default ssl_key_file and ssl_cert_file paths - you're building with the correct --with-ssldir - No need to change "ssl_listen" as well as "listen" - "ssl_listen" defaults to the value of "listen" if it's unset - No need to change "mbox_read_locks" - the upstream default is the same
Created attachment 123902 [details] dovecot-1.0.beta2-change-defaults.patch
My problem with this approach is with people who have existing configuration files that point to different places. It is easier to find out if you have the right locations in the default configfile. I suppose your compromise to change the values to what we use now, but leave them commented out, as well as patch the source could be OK though. Still possibly a tad bit confusing, since the certificate changed location... Other than that looks fairly well, small buglet with ssl_key_file: s,certs,private,. I will think about it.