Hello Petr Mandelík Then you should perhaps open a bug report at http://www.sogo.nu/bugs/ As you can reproduce this, you could provide logs and other infos for it. With that information, Inverse should be able to pin this bug down.
Kind regards, Christian Mack Am 2015-01-23 um 14:12 schrieb Petr Mandelík: > The workaround works. If sogo endless loop occurs I switch reminders setting > on my iPhone off and again on. After that communication follows > SOGoMaximumPingInterval. It happens regardless on SOGoMaximumPingInterval, > SOGoMaximumSyncInterval and SOGoInternalSyncInterval. Any change in calendar > (at least new event or update) will cause endless loop. > > Pátek, 23 Leden, 2015 10:01 CET, Petr Mandelík <p...@mandelik.com> napsal: > >> 1) Works. But I have another mailbox on MS Exchange server with Push enables >> and it nevers falls in endless loop. Therefore there must be something wrong >> with SOGo. >> 2) It was me who wrote about NAT. Now after many days of testing and many >> other combinations of SOGo parameters I must say the problem with endless >> loop is much more complex and unpredictable. It is just my personal >> empirical observation but definitely there is no direct relation between >> parameters and endless loop. Sometimes it falls to endless loop even after >> another action. For example after adding new entry to calendar on my laptop. >> I think I found following workaround...if I switch off task syncing on my >> iPhone for a while and again switch it on, the communication "heartbeat" >> will slow down and goes back to the limits according SOGo parameters. In my >> opinion there must be something wrong in sogo deamon. Meaning how sogo >> server handles changes and pushing them to EAS device. Nevertheless even the >> setup of my iPhone has an impact on it. Maybe...just my hypothesis...when I >> re-enable syncing of tasks...SOGo will do some kind of initial sync which >> synchronize correct way my iPhone . After this action it works for a while. >> 3) EAS brings very significant advantage to common users...easy setup. >> >> PM >> >> >> >>>> >>>> I tried different iOs devices, different servers (debian, Ubuntu), the >>>> latest >>>> nighty build of SOGo, nginx and apache, all without success. That makes >>>> SOGo >>>> Activesync unusable for me. >>>> >>>> Any ideas concerning the reason? >>> >>> There have been quite a lot of suggestions regarding this on mailing list, >>> try searching the Archives. >>> >>> My advice would be: >>> >>> 1. Disable Push and use Fetch as email retrieval method (every 15 min). >>> This should improve your battery life dramatically >>> 2. There has been someone on mailing list mentioning that if there is >>> another device behind the same NAT taking to your IMAP server (e.g. >>> Thunderbird) at the the same time as your EAS client it’ll fool the server >>> into the endless loop (some can confirm this?) >>> 3. Don’t use EAS on iOS. Since iOS has built in IMAP, CalDAV and CardDAV >>> support I see no reason to use EAS at all (other then ease of initial >>> configuration). You can achieve the same results with separate mail, >>> calendar and contacts account, EAS on iOS does not bring any advantage over >>> that (quite the opposite). >>> >>> Best Regards >>> Martin.-- >>> users@sogo.nu >>> https://inverse.ca/sogo/lists >> >> >> >> >> >> -- >> users@sogo.nu >> https://inverse.ca/sogo/lists > > > > > -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
