Hi Timo, I'm the one who suggested the '-n' option to capture the actual config settings that the running dovecot process was using (ala postfix), and you implemented it very quickly - so thanks for that! Now, I'd like to suggest an enhancement... Many people still do not provide basic things like dovecot version, and there are secondary config files like dovecot-ldap, whose settings are not included in the dovecot -n output. How difficult would it be to add these to the output so that the output would include the running dovecot version, as well as any extra config settings from any other files that are loaded when dovecot starts? It would sure make it easier, both for us troubleshooting on our own, and when asking for help on the list. Many thanks, and terrific job on 1.0! Now all dovecot lacks is full support for IMAP ACLs/shared folders, and support for single-instance storage, and it will have no real competition... -- Best regards, Charles
On Thu, 2007-04-26 at 08:11 -0400, Charles Marcus wrote:> Many people still do not provide basic things like dovecot version, and > there are secondary config files like dovecot-ldap, whose settings are > not included in the dovecot -n output. > > How difficult would it be to add these to the output so that the output > would include the running dovecot version,I guess this could be added. Maybe: # v1.0.0: /usr/local/etc/dovecot.conf> as well as any extra config > settings from any other files that are loaded when dovecot starts?Yes, this would be a really nice feature, but probably too kludgy feature before the config handling rewrite in v2.0. -------------- 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/20070511/b6ac8438/attachment.bin>
>> Many people still do not provide basic things like dovecot version, and >> there are secondary config files like dovecot-ldap, whose settings are >> not included in the dovecot -n output. >> >> How difficult would it be to add these to the output so that the output >> would include the running dovecot version,> I guess this could be added. Maybe: > > # v1.0.0: /usr/local/etc/dovecot.confWorks for me... :)>> as well as any extra config >> settings from any other files that are loaded when dovecot starts?> Yes, this would be a really nice feature, but probably too kludgy > feature before the config handling rewrite in v2.0.Cool - I'll keep it on my list to watch for, and remind later when you're getting closer to 2.0 in case you forget... Thanks! -- Best regards, Charles