Re: [SOGo] Activesync drains battery

[Martin Simovic]

> On 27 Jan 2015, at 14:50, Martin Simovic  wrote:
> 
> OK - Tested with EAS with following result:
> 
> - iOS8 - RVSP buttons are there. However they are of no use, since event date 
> is always shown as 01:00 hour at 01.01.2001 (just like you say). Event is not 
> shown in right place in calendar either. 
> 
> - Outlook 2013 - RVSP buttons are there. However, Outlook shows a note saying 
> “meeting organiser did not request response to this meeting” and after you 
> accept it correctly appears in Calendar but now response is sent. Haven’t 
> find a way to respond so far (other then to send an email with text “I am 
> coming!”.

** of course I wanted to say here “no response is sent” ** 

> 
> Too bad. I wonder if there is any EAS client that would handle meeting 
> invites properly?
> 
> 
> 
>> On 27 Jan 2015, at 13:23, zero one > <mailto:lis...@outlook.de>> wrote:
>> 
>> I tested it with EAS and RSVP buttons are there. Problem here is, that 
>> always 01.01.2011 is shown as the event date (in the attached ics file the 
>> event date is correct).
>> 
>> Because we have to handle many external invites I switched to EAS.
>> 
>> Besides: I did a lot of testing with other solutions (Kolab, Apple 
>> Calendarserver, Baikal, etc.) - problem is always the same. When using 
>> IMAP/calDAV you never see rsvp buttons. Seems to be an issue of the iOS 
>> client. I talked to apple support and the confirmed this behaviour without 
>> admitting a bug. When using push services of Mac OS X server the problem 
>> does not exist - so Apple won't give it a big attention.
>> 
>> 
>> 
>> From: mar...@netson.sk <mailto:mar...@netson.sk>
>> Date: Tue, 27 Jan 2015 11:59:13 +0100
>> To: users@sogo.nu <mailto:users@sogo.nu>
>> Subject: Re: [SOGo] Activesync drains battery
>> 
>> Hi,
>> 
>> On 26 Jan 2015, at 18:22, zero one > <mailto:lis...@outlook.de>> wrote:
>> 
>> Me too on iOS 8. No rsvp buttons. Invitation comes from external user (via 
>> outlook which is a usual scenario for me). IMAP server is dovecot. Maybe 
>> something related to the IMAP server?
>> 
>> It has nothing to do with IMAP. Did my tests, and you are right - no rvsp 
>> buttons when email is used as transport - this is the case of external 
>> users. For users within same domain / SOGo installation, all works fine. 
>> Haven’t tested with EAS though .. Will give it a shot.
>> 
>> M.
> 

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[Martin Simovic]

OK - Tested with EAS with following result:

- iOS8 - RVSP buttons are there. However they are of no use, since event date 
is always shown as 01:00 hour at 01.01.2001 (just like you say). Event is not 
shown in right place in calendar either. 

- Outlook 2013 - RVSP buttons are there. However, Outlook shows a note saying 
“meeting organiser did not request response to this meeting” and after you 
accept it correctly appears in Calendar but now response is sent. Haven’t find 
a way to respond so far (other then to send an email with text “I am coming!”.

Too bad. I wonder if there is any EAS client that would handle meeting invites 
properly?



> On 27 Jan 2015, at 13:23, zero one  wrote:
> 
> I tested it with EAS and RSVP buttons are there. Problem here is, that always 
> 01.01.2011 is shown as the event date (in the attached ics file the event 
> date is correct).
> 
> Because we have to handle many external invites I switched to EAS.
> 
> Besides: I did a lot of testing with other solutions (Kolab, Apple 
> Calendarserver, Baikal, etc.) - problem is always the same. When using 
> IMAP/calDAV you never see rsvp buttons. Seems to be an issue of the iOS 
> client. I talked to apple support and the confirmed this behaviour without 
> admitting a bug. When using push services of Mac OS X server the problem does 
> not exist - so Apple won't give it a big attention.
> 
> 
> 
> From: mar...@netson.sk
> Date: Tue, 27 Jan 2015 11:59:13 +0100
> To: users@sogo.nu
> Subject: Re: [SOGo] Activesync drains battery
> 
> Hi,
> 
> On 26 Jan 2015, at 18:22, zero one  <mailto:lis...@outlook.de>> wrote:
> 
> Me too on iOS 8. No rsvp buttons. Invitation comes from external user (via 
> outlook which is a usual scenario for me). IMAP server is dovecot. Maybe 
> something related to the IMAP server?
> 
> It has nothing to do with IMAP. Did my tests, and you are right - no rvsp 
> buttons when email is used as transport - this is the case of external users. 
> For users within same domain / SOGo installation, all works fine. Haven’t 
> tested with EAS though .. Will give it a shot.
> 
> M.

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

RE: [SOGo] Activesync drains battery

[zero one]

I tested it with EAS and RSVP buttons are there. Problem here is, that always 
01.01.2011 is shown as the event date (in the attached ics file the event date 
is correct).
Because we have to handle many external invites I switched to EAS.
Besides: I did a lot of testing with other solutions (Kolab, Apple 
Calendarserver, Baikal, etc.) - problem is always the same. When using 
IMAP/calDAV you never see rsvp buttons. Seems to be an issue of the iOS client. 
I talked to apple support and the confirmed this behaviour without admitting a 
bug. When using push services of Mac OS X server the problem does not exist - 
so Apple won't give it a big attention.


From: mar...@netson.sk
Date: Tue, 27 Jan 2015 11:59:13 +0100
To: users@sogo.nu
Subject: Re: [SOGo] Activesync drains battery

Hi,
On 26 Jan 2015, at 18:22, zero one  wrote:Me too on iOS 8. 
No rsvp buttons. Invitation comes from external user (via outlook which is a 
usual scenario for me). IMAP server is dovecot. Maybe something related to the 
IMAP server?
It has nothing to do with IMAP. Did my tests, and you are right - no rvsp 
buttons when email is used as transport - this is the case of external users. 
For users within same domain / SOGo installation, all works fine. Haven’t 
tested with EAS though .. Will give it a shot.
M.-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[Martin Simovic]

Hi,

> On 26 Jan 2015, at 18:22, zero one  wrote:
> 
> Me too on iOS 8. No rsvp buttons. Invitation comes from external user (via 
> outlook which is a usual scenario for me). IMAP server is dovecot. Maybe 
> something related to the IMAP server?

It has nothing to do with IMAP. Did my tests, and you are right - no rvsp 
buttons when email is used as transport - this is the case of external users. 
For users within same domain / SOGo installation, all works fine. Haven’t 
tested with EAS though .. Will give it a shot.

M.-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[Christian Mack]

Hello

IMAP has nothing to do with invitations.
As long as it is delivered to your client.

I had once a user which got invitations in TNEF format from an Outlook user.
That didn't work either.


Kind regards,
Christian Mack

Am 2015-01-26 um 18:22 schrieb zero one:
> Me too on iOS 8. No rsvp buttons. Invitation comes from external user (via 
> outlook which is a usual scenario for me). IMAP server is dovecot. Maybe 
> something related to the IMAP server?
> 
>> Am 26.01.2015 um 16:04 schrieb Martin Simovic :
>>
>>> On 26 Jan 2015, at 08:23, zero one  wrote:
>>>
>>> Yes, I tried the newest nighty build. What I found out is that when using 
>>> IMAP, calDAV you cannot accept meeting invites. I only see a button "add to 
>>> caendar" and with this the organizer won't get a reply after accepting or 
>>> declining. 
>>
>> On iOS?? I can perfectly accept / decline meeting invites on iOS (CalDAV) 
>> and meeting organiser is notified via email and SOGo internal mechanism too. 
>> I use iOS 8
>>


-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [SOGo] Activesync drains battery

[zero one]

Me too on iOS 8. No rsvp buttons. Invitation comes from external user (via 
outlook which is a usual scenario for me). IMAP server is dovecot. Maybe 
something related to the IMAP server?



> Am 26.01.2015 um 16:04 schrieb Martin Simovic :
> 
> 
>> On 26 Jan 2015, at 08:23, zero one  wrote:
>> 
>> Yes, I tried the newest nighty build. What I found out is that when using 
>> IMAP, calDAV you cannot accept meeting invites. I only see a button "add to 
>> caendar" and with this the organizer won't get a reply after accepting or 
>> declining. 
> 
> On iOS?? I can perfectly accept / decline meeting invites on iOS (CalDAV) and 
> meeting organiser is notified via email and SOGo internal mechanism too. I 
> use iOS 8
> 
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[Martin Simovic]

> On 26 Jan 2015, at 08:23, zero one  wrote:
> 
> Yes, I tried the newest nighty build. What I found out is that when using 
> IMAP, calDAV you cannot accept meeting invites. I only see a button "add to 
> caendar" and with this the organizer won't get a reply after accepting or 
> declining. 

On iOS?? I can perfectly accept / decline meeting invites on iOS (CalDAV) and 
meeting organiser is notified via email and SOGo internal mechanism too. I use 
iOS 8

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[Christian Mack]

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  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

Re: [SOGo] Activesync drains battery

[zero one]

Yes, I tried the newest nighty build. What I found out is that when using IMAP, 
calDAV you cannot accept meeting invites. I only see a button "add to caendar" 
and with this the organizer won't get a reply after accepting or declining. 

With activesync I see the rsvp buttons. Here the problem is that all meeting 
invitations are shown with the same date (January 1st 2001). 



> Am 23.01.2015 um 19:19 schrieb Martin Simovic :
> 
> 
>> On 23 Jan 2015, at 16:15, zero one  wrote:
>> 
>> Problem with z-push is the way it handles meeting invitations - I discovered 
>> several problems with this:
>> 
>> a) outgoing invites are not sent correctly (empty mail instead of ics 
>> attachment)
>> b) incoming invites can't be accepted or declined (no RSVP buttons)
>> 
>> There is a fork of z-push called Z-Push-Contrib on github where these stuff 
>> may be resolved in the future.
>> 
>> In addition I discovered similar problems with sogo when using IMAP/calDAV 
>> combo. There seems to be some problems with iOS as well.
> 
> I haven’t noticed any problems using CalDAV on iOS. There were some issues in 
> the past, but these have been resolved (e.g. 
> http://www.sogo.nu/bugs/view.php?id=2978) - have you tried recent builds?
> 
> Regards
> Martin
> 
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[Martin Simovic]

> On 23 Jan 2015, at 16:15, zero one  wrote:
> 
> Problem with z-push is the way it handles meeting invitations - I discovered 
> several problems with this:
> 
> a) outgoing invites are not sent correctly (empty mail instead of ics 
> attachment)
> b) incoming invites can't be accepted or declined (no RSVP buttons)
> 
> There is a fork of z-push called Z-Push-Contrib on github where these stuff 
> may be resolved in the future.
> 
> In addition I discovered similar problems with sogo when using IMAP/calDAV 
> combo. There seems to be some problems with iOS as well.

I haven’t noticed any problems using CalDAV on iOS. There were some issues in 
the past, but these have been resolved (e.g. 
http://www.sogo.nu/bugs/view.php?id=2978 
) - have you tried recent builds?

Regards
Martin

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

RE: [SOGo] Activesync drains battery

[zero one]

Problem with z-push is the way it handles meeting invitations - I discovered 
several problems with this:
a) outgoing invites are not sent correctly (empty mail instead of ics 
attachment)b) incoming invites can't be accepted or declined (no RSVP buttons)
There is a fork of z-push called Z-Push-Contrib on github where these stuff may 
be resolved in the future.
In addition I discovered similar problems with sogo when using IMAP/calDAV 
combo. There seems to be some problems with iOS as well.

To: users@sogo.nu
From: dbro...@mdah.state.ms.us
Date: Fri, 23 Jan 2015 07:30:58 -0600
Subject: Re: [SOGo] Activesync drains battery

On Friday, January 23, 2015 06:50 AM CST, Martin Simovic  
wrote:
  On 23 Jan 2015, at 10:01, Petr Mandelík  wrote: 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. Indeed. Push *should* work without impact on battery life, unfortunately 
not with SOGo ATM. 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. Ah, thanks.  3) 
EAS brings very significant advantage to common users...easy setup.And nothing 
more than that I am afraid. From any other perspective and performance impact 
on client/server IMAP/CalDAV/CardDAV combo is far superior, at least for the 
time being. RegardsMartin.
It isn't just the "simple setup" that makes it useful for certain users. In our 
case we can only have port 80 and 443 open to the internet. So IMAP is a no go. 
Activesync is a great solution for this. However I have never had good luck 
with the sogo implementation of it. We have been using zpush on a separate 
server successfully since nearly the beginning of using sogo though. I just 
wish I could get it to work with calendars and contacts easily. Email is 
flawless.

  -- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[Donny Brooks]

On Friday, January 23, 2015 06:50 AM CST, Martin Simovic  
wrote:
  On 23 Jan 2015, at 10:01, Petr Mandelík  wrote: 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. Indeed. Push *should* work without impact on battery life, unfortunately 
not with SOGo ATM. 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. Ah, thanks.  3) 
EAS brings very significant advantage to common users...easy setup.And nothing 
more than that I am afraid. From any other perspective and performance impact 
on client/server IMAP/CalDAV/CardDAV combo is far superior, at least for the 
time being. RegardsMartin.
It isn't just the "simple setup" that makes it useful for certain users. In our 
case we can only have port 80 and 443 open to the internet. So IMAP is a no go. 
Activesync is a great solution for this. However I have never had good luck 
with the sogo implementation of it. We have been using zpush on a separate 
server successfully since nearly the beginning of using sogo though. I just 
wish I could get it to work with calendars and contacts easily. Email is 
flawless.

 
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[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  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





-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[Martin Simovic]

> On 23 Jan 2015, at 10:01, Petr Mandelík  wrote:
> 
> 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.

Indeed. Push *should* work without impact on battery life, unfortunately not 
with SOGo ATM.

> 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.

Ah, thanks. 

> 3) EAS brings very significant advantage to common users...easy setup.

And nothing more than that I am afraid. From any other perspective and 
performance impact on client/server IMAP/CalDAV/CardDAV combo is far superior, 
at least for the time being.

Regards
Martin.

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[zero one]

I fully agree. Yesterday Thomas supported me and found out some things that 
cause these endless loops and that need to be fixed. Meanwhile I was advices to 
set up the account as activesync but don't set it to push but to pull (15 
minutes). This seem to work. Hope that we will soon get a fix ...



> Am 23.01.2015 um 12:28 schrieb Petr Mandelík :
> 
> 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
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[Petr Mandelík]

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

Re: [SOGo] Activesync drains battery

[mourik jan heupink]

On 01/22/2015 06:00 PM, Davide Bozzelli wrote:

Given the high demand about this topic, could u please publish some
"best practices" about tuning this values ?
Something like "if you have 50 users then set them with these values" or
something like.


Yes, we would also appreciate that. Specially since we knew about 
SOGoMaximumPingInterval

SOGoMaximumSyncInterval
SOGoInternalSyncInterval

but now also other things (apache timeout and WOWatchDogRequestTimeout) 
came up.


Some examples and their results would be appreciated.
--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[zero one]

I cannot confirm 3) 

Especially when you need to send and receive invites to appointments calDAV is 
by far not a good solution. 

As well I have successfully used EAS eg with openXchange (OX) without such a 
huge battery drain. So I assume it can be solved by adjusting some settings. 



> Am 22.01.2015 um 18:07 schrieb Martin Simovic :
> 
> 
> 
>> On 22 Jan 2015, at 16:38, lis...@outlook.de wrote:
>> 
>> Hi,
>> 
>> when using Activesync the battery of my iPhone drains significantly. The log
>> shows a lot of entries with
>> 
>> Change detected, we push the content
>> 
>> tcpdump and verbose logging are showing constantly connections to the IMAP-
>> server. Seems like activesync wakes up the iphone permanently due to alleged
>> changes (which are in fact not there).
>> 
>> 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

Re: [SOGo] Activesync drains battery

[Martin Simovic]

> On 22 Jan 2015, at 16:38, lis...@outlook.de wrote:
> 
> Hi,
> 
> when using Activesync the battery of my iPhone drains significantly. The log
> shows a lot of entries with
> 
> Change detected, we push the content
> 
> tcpdump and verbose logging are showing constantly connections to the IMAP-
> server. Seems like activesync wakes up the iphone permanently due to alleged
> changes (which are in fact not there).
> 
> 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

Re: [SOGo] Activesync drains battery

[Davide Bozzelli]

Given the high demand about this topic, could u please publish some 
"best practices" about tuning this values ?
Something like "if you have 50 users then set them with these values" or 
something like.


It's not intuitive as you might think .

Thx
Il 22/01/15 17:47, Ludovic Marcotte ha scritto:

On 22/01/2015 10:38, lis...@outlook.de wrote:

Any ideas concerning the reason?
Have you tuned your proxy read timeouts in nginx? You had 90 seconds 
from your previous post, which is way too low.


Have you also tuned:

SOGoMaximumPingInterval
SOGoMaximumSyncInterval
SOGoInternalSyncInterval

If not, a sogod process will not keep the EAS connection active for 
more than 10 to 30 seconds - which will force your EAS device to 
re-establish the connection, over and over.


If you increase these values, you must also increase your nginx/Apache 
timeouts because they won't receive a response from sogod for X amount 
of minutes.


If you do that, you must also adjust WOWatchDogRequestTimeout, because 
by default, sogod processes aren't allowed to take more than 10 
minutes to handle a request.




--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[zero one]

Thank you, Ludovic!

Can recommend values? I have in total 2 devices connected via activesync. 


Thanks for your help!


> Am 22.01.2015 um 17:48 schrieb Ludovic Marcotte :
> 
>> On 22/01/2015 10:38, lis...@outlook.de wrote:
>> Any ideas concerning the reason?
> Have you tuned your proxy read timeouts in nginx? You had 90 seconds from 
> your previous post, which is way too low.
> 
> Have you also tuned:
> 
> SOGoMaximumPingInterval
> SOGoMaximumSyncInterval
> SOGoInternalSyncInterval
> 
> If not, a sogod process will not keep the EAS connection active for more than 
> 10 to 30 seconds - which will force your EAS device to re-establish the 
> connection, over and over.
> 
> If you increase these values, you must also increase your nginx/Apache 
> timeouts because they won't receive a response from sogod for X amount of 
> minutes.
> 
> If you do that, you must also adjust WOWatchDogRequestTimeout, because by 
> default, sogod processes aren't allowed to take more than 10 minutes to 
> handle a request.
> 
> -- 
> Ludovic Marcotte
> lmarco...@inverse.ca  ::  +1.514.755.3630  ::  http://inverse.ca
> Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence 
> (http://packetfence.org)
> 
> -- 
> users@sogo.nu
> https://inverse.ca/sogo/lists
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[Ludovic Marcotte]

On 22/01/2015 10:38, lis...@outlook.de wrote:

Any ideas concerning the reason?
Have you tuned your proxy read timeouts in nginx? You had 90 seconds 
from your previous post, which is way too low.


Have you also tuned:

SOGoMaximumPingInterval
SOGoMaximumSyncInterval
SOGoInternalSyncInterval

If not, a sogod process will not keep the EAS connection active for more 
than 10 to 30 seconds - which will force your EAS device to re-establish 
the connection, over and over.


If you increase these values, you must also increase your nginx/Apache 
timeouts because they won't receive a response from sogod for X amount 
of minutes.


If you do that, you must also adjust WOWatchDogRequestTimeout, because 
by default, sogod processes aren't allowed to take more than 10 minutes 
to handle a request.


--
Ludovic Marcotte
lmarco...@inverse.ca  ::  +1.514.755.3630  ::  http://inverse.ca
Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence 
(http://packetfence.org)

--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Activesync drains battery

[André Schild]

Hello,

there has been a thread recently about this topic.
- You have to tune the ActiveSync settings on serverside to match your 
needs.



Am 22.01.2015 um 16:38 schrieb lis...@outlook.de:

Hi,

when using Activesync the battery of my iPhone drains significantly. The log
shows a lot of entries with

Change detected, we push the content

tcpdump and verbose logging are showing constantly connections to the IMAP-
server. Seems like activesync wakes up the iphone permanently due to alleged
changes (which are in fact not there).


- Make sure your IMAP server supports all required features (QRESYNC etc.)

André


--
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Activesync drains battery

[list01]

Hi,

when using Activesync the battery of my iPhone drains significantly. The log
shows a lot of entries with

Change detected, we push the content

tcpdump and verbose logging are showing constantly connections to the IMAP-
server. Seems like activesync wakes up the iphone permanently due to alleged
changes (which are in fact not there).

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?


Thanks!
-- 
users@sogo.nu
https://inverse.ca/sogo/lists