yes, it shows a summary what is configured, but not that there is a problem with one of the settings; only the 'restart' of the dovecot service generates a error in the logfile which point you to the problem, a 'reload' sets the configured value but does not generate a error; also not when clients want to connect via imap - you see in the logs only that the client trys to connect several times until it hits the 'mail_max_userip_connections' and the imap processes hang until you kill them hard manually;
On 15.05.2010 21:05, Charles Marcus wrote:
On 2010-05-15 2:54 PM, Joelly Alexander wrote:
found the error - i had a typo in dovecot.conf
lock_method: fnctl should be lock_method: fcntl
dovecot reload does not show a problem, only a stop/start generated the entry in the logfile....
two days for a stupid typo....
dovecot -n should also show the problem...