On 2010-05-16 5:34 AM, Joelly Alexander wrote: > On 15.05.2010 21:05, Charles Marcus wrote: >> On 2010-05-15 2:54 PM, Joelly Alexander wrote: >>> two days for a stupid typo....
>> dovecot -n should also show the problem... > yes, it shows a summary what is configured, but not that there is a > problem with one of the settings; Hmmm... it was my understanding that, like postfix, dovecot -n would warn on *all* syntax errors, which I would classify a typo like this as... But I just checked... if it is spelled properly, this setting doesn't show up in doveoct -n output at all, which suggests that lock_method = fcntl is the default - *but*, if it is spelled *improperly*, it *does* show up, and with the incorrect spelling... A quick test with another setting does produce the desired warning/error - I changed the protocols line to inaps, and: myhost : Sun May 16, 13:49:16 : /etc # dovecot -n # 1.2.11: /etc/dovecot/dovecot.conf Error: Invalid protocols given in configuration file Fatal: Invalid configuration in /etc/dovecot/dovecot.conf myhost : Sun May 16, 13:49:18 : /etc # Timo? Shouldn't dovecot -n produce a similar warning/error for all invalid/typo'd settings? I also think it would be a good idea to report the line# in the config file where the error resides (can make it much easier to find the setting in a large, heavily commented config file)... -- Best regards, Charles
