On 2010-05-22 4:35 AM, Timo Sirainen wrote:
> On 20.5.2010, at 21.59, Charles Marcus wrote:
>> Hmmm... postfix handles this by simply letting the last one 'win', which
>> seems like a reasonable way to handle that.
>>
>> Any chance 2.0 could work the same way? This way I could keep all of my
>> se
On 20.5.2010, at 21.59, Charles Marcus wrote:
>>> 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)...
>
>> This is unfortunately difficult. The config
On 2010-05-20 1:58 PM, Timo Sirainen wrote:
> On 16.5.2010, at 19.54, Charles Marcus wrote:
> v2.0 dovecot -n shows if lock_method was typoed. Also I find it
> strange that reloading a config wouldn't show the error.
Cool...
>> I also think it would be a good idea to report the line# in the
>> co
On 16.5.2010, at 19.54, Charles Marcus wrote:
> Timo? Shouldn't dovecot -n produce a similar warning/error for all
> invalid/typo'd settings?
v2.0 dovecot -n shows if lock_method was typoed. Also I find it strange that
reloading a config wouldn't show the error.
> I also think it would be a goo
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
> pr
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 clien
Joelly Alexander put forth on 5/15/2010 1:54 PM:
>
> 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
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
dovec
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
thanks!
On 15.05.2010 11:58, Stan Hoeppner wrote:
Joelly Alexande
Joelly Alexander put forth on 5/15/2010 4:22 AM:
> the server and the client are on the same layer2 network and there is no
> hard- or software or anything else installed on the server what prevents
> traffic between them;
> i just figured out that it has to do with the nfs portion;
> while incomin
Joelly Alexander put forth on 5/14/2010 2:18 PM:
> hi,
>
> dovecot from the debian lenny backports does not successfully accept
> incomming imap or imaps connections;
> when the client connect i can see the clients ip address in an
> imap-process but the client cannot succesfully connect and retri
hi,
dovecot from the debian lenny backports does not successfully accept
incomming imap or imaps connections;
when the client connect i can see the clients ip address in an
imap-process but the client cannot succesfully connect and retries this
several times where an new imap-process is bound
12 matches
Mail list logo
