I had the same problem with my iPhone. Today I spent some time trying to find optimal setup of SOGoMaximumPingInterval, SOGoMaximumSyncInterval and SOGoInternalSyncInterval. I started from the suggestion and tried a lot of combinations. I think that drain of batteries is not primarily a question of setting these parameters. Finally I used following setup
SOGoMaximumPingInterval = 300; SOGoMaximumSyncInterval = 3; SOGoInternalSyncInterval = 3; Everything works well and the TCP/IP traffic between my iPhone and sogo server follows the actions on my iPhone, receiving and sending emails, marking them read/unread atc. I register packets close to SOGoMaximumPingInterval or in longer interval if there are no new emails or other actions. If I open Thunderbird everything works still well until I try to change something in Thunderbird (i.e.to reading new emails, marking emails unread or moving emails among folders). After such actions suddenly the traffic on port 443 between iPhone and sogo server will significantly increase which is logical as iPhone needs to be synced. I register packets each second corresponding to "POST" messages in sogo.log. But the frequency will not slow down until I close Thunderbird. It happens only if Thunderbird runs on a machine behind of the same NAT server like iPhone. So the packets are coming to sogo server from the same IP address. If I close Thunderbird the traffic will come steady soon. In case of having iPhone and Thunderbird running on different networks the traffic is normal following the action on both devices. If I use web GUI instead of Thunderbird and do the same actions this never happens either. I am able to reproduce the problem any time. So the problem seems to be isolated somewhere in the communication between Thunderbird and sogo server which will cause neverending syncing between iPhone (and probably any other device connected through EAS) and sogo server. Hopefully it will help developers to resolve the problem. Regards PM Úterý, 13 Leden, 2015 22:31 CET, Ludovic Marcotte <[email protected]> napsal: > On 13/01/2015 16:12, Kai-Uwe Rommel wrote: > > On page 50 of the SOGo manual those three parameters are listed. > > But there is only a brief explanation and there is no recommendation > > that the defaults should be changed and if so, which values would > > be appropriate. > It depends on many factors - like the number of EAS clients you have, > the resources available on your SOGo server, etc. > > How do you suggest to set these parameters? > If you set SOGoMaximumPingInterval and SOGoMaximumSyncInterval to 300 (5 > mins), one of your sogod process will be busy for a maximum of 5 > minutes. If you set SOGoInternalSyncInterval to 30, an internal check > will happen for changes every 30 seconds within the 5 minutes. > > Start with that and see where you get to. > > -- > Ludovic Marcotte > [email protected] :: +1.514.755.3630 :: http://inverse.ca > Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence > (http://packetfence.org) > > -- > [email protected] > https://inverse.ca/sogo/lists -- [email protected] https://inverse.ca/sogo/lists
