[Dovecot] Problem with lmtp director proxy
Angel L. Mateo
amateo at um.es
Mon Jun 18 17:47:09 EEST 2012
El 18/06/12 15:50, Timo Sirainen escribió:
> On 18.6.2012, at 9.52, Angel L. Mateo wrote:
>> El 16/06/12 01:22, Timo Sirainen escribió:
>>> On 13.6.2012, at 20.11, Angel L. Mateo wrote:
>>>> Ok, you were right. I was looking for logs at my log repository, which doesn't receive debug log. Nevertheless, the only auth lines I have found at the ones above, with the proxy_refresh=450. I haven't found any line with a timeout log in the proxies neither the backends
>>> The backend logs don't matter. Director adds the proxy_refresh. You haven't shown in your logs what auth process logs as debug messages. This is what is supposed to happen:
>>>> Jun 16 02:19:11 auth: Debug: master out: PASS 1 user=director proxy proxy_timeout=1000
>> I don't have any log like this.
> Then you don't have auth_debug=yes.
I had this option. Relooking I have found these logs. I didn't see them
before because of the format and because they aren't related with lmtp.
I have them in the form:
Jun 18 12:18:30 myotis41 dovecot: auth: Debug: master out:
>> Jun 18 08:46:18 myotis40 dovecot: lmtp(11276): Debug: auth input: user=<user> proxy proxy_timeout=120 host=126.96.36.199 proxy_refresh=450
>> Is this correct?
Anyway, with the last change (defining the proxy_timeout at the static
passdb definition, default 30 seconds timeout hasn't been applied anymore.
More information about the dovecot