Timo Sirainen wrote:
Mar 8 13:02:57 vs02 deliver((null)): User request from dovecot-auth
timed out
Oh, that's a new bug. This should fix it:
http://hg.dovecot.org/dovecot-1.1/rev/631fd6f25e41
Works, thanks a lot.
Regards,
Bernhard
On Sat, 2008-03-08 at 13:05 +0100, Bernhard Schmidt wrote:
> Mar 8 13:02:57 vs02 deliver((null)): User request from dovecot-auth
> timed out
Oh, that's a new bug. This should fix it:
http://hg.dovecot.org/dovecot-1.1/rev/631fd6f25e41
signature.asc
Description: This is a digitally signed message
Timo Sirainen <[EMAIL PROTECTED]> wrote:
>> I'm having a really really strange problem. After upgrading from
>> 1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect
>> to the services using IPv4 anymore. dovecot happily binds to the IPv6
>> wildcard socket which should accept IPv
On Mar 8, 2008, at 1:51 PM, Bernhard Schmidt wrote:
I'm having a really really strange problem. After upgrading from
1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect
to the services using IPv4 anymore. dovecot happily binds to the IPv6
wildcard socket which should accept IP
Hi,
I'm having a really really strange problem. After upgrading from
1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect
to the services using IPv4 anymore. dovecot happily binds to the IPv6
wildcard socket which should accept IPv4 connections as well.
[EMAIL PROTECTED]:~# nets
