[horde] Activesync not closing connections

[Andreas Mauser]

----- Nachricht von Simon Brereton <simon.buongiorno at gmail.com> ---------
   Datum: Mon, 18 Mar 2013 14:34:58 +0100
     Von: Simon Brereton <simon.buongiorno at gmail.com>
Betreff: Re: [horde] Activesync not closing connections
      An: Tom Seeley <horde at tomseeley.co.uk>
      Cc: "horde at lists.horde.org" <horde at lists.horde.org>


> On 18 March 2013 10:08, Tom Seeley <horde at tomseeley.co.uk> wrote:
>> Hi,
>>
>> I had been using Activesync relatively successfully for several weeks, but
>> recently (I'm afraid I'm not sure exactly when), I seem to have sprung some
>> sort of leak.
>>
>> The observed behaviour is that Dovecot locks me out of my account because I
>> have exceeded "mail_max_userip_connections", which is set to 10 by default.
>> Dovecot isn't lying, what appears to be happening is that my AS client
>> (Samsung galaxy s2) is making requests that aren't closing.  Very quickly
>> after starting apache I see something like this:
>>
>> # netstat -an |grep 192.168.0.221
>> tcp        0     52 10.0.0.1:22               192.168.0.221:58347
>> ESTABLISHED
>> tcp       24      0 ::ffff:10.0.0.1:443       ::ffff:192.168.0.221:38544
>> CLOSE_WAIT
>> tcp       24      0 ::ffff:10.0.0.1:443       ::ffff:192.168.0.221:35204
>> CLOSE_WAIT
>> tcp        0      0 ::ffff:10.0.0.1:443       ::ffff:192.168.0.221:58502
>> ESTABLISHED
>> tcp       24      0 ::ffff:10.0.0.1:443       ::ffff:192.168.0.221:55443
>> CLOSE_WAIT
>> tcp       24      0 ::ffff:10.0.0.1:443       ::ffff:192.168.0.221:38506
>> CLOSE_WAIT
>> tcp       24      0 ::ffff:10.0.0.1:443       ::ffff:192.168.0.221:42254
>> CLOSE_WAIT
>> tcp       24      0 ::ffff:10.0.0.1:443       ::ffff:192.168.0.221:42254
>> CLOSE_WAIT
>> tcp       24      0 ::ffff:10.0.0.1:443       ::ffff:192.168.0.221:42254
>> CLOSE_WAIT
>> tcp       24      0 ::ffff:10.0.0.1:443       ::ffff:192.168.0.221:42254
>> CLOSE_WAIT
>> tcp       24      0 ::ffff:10.0.0.1:443       ::ffff:192.168.0.221:42254
>> CLOSE_WAIT
>>
>> After the above no more logins into horde are possible to my account+IP.
>>
>> My understanding of TCP would lead me to suggest that the client has
>> requested a close of the connection and the server has yet to release the
>> socket.
>>
>> As a workaround I have resorted to changing my phone to a 5 min sync (ie
>> turning off push) to maintain functionality.
>
> Funnily enough I've been running into this problem myself.  I put it
> down to the fact that I now have two devices that use activeSync on
> the same account and so I bumper my mail_max_userip to 20 for now and
> that seems to have fixed the issue (but I only did it this morning, so
> we will see).  I was prompted to do this because I have increasingly
> been told by one device or the other that the sign-in failed (Samsung
> Galaxy S3) or the password wasn't correct (iPhone 4s).

The same happened here, I also increased that number.

Also I found that with my Samsung S3mini and my girls iPhone5 the best  
setting in Horde is Activesync v12.0.

Still dont know why 12.1 does not work flawlessly for us.
Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5014 bytes
Desc: S/MIME Signatur
URL: <http://lists.horde.org/archives/horde/attachments/20130318/17c0c0e4/attachment.bin>