Hi Christian,
Thanks for the help. Information below.
John
On 19/02/2016 09:07, Christian Mack wrote:
Hello
Am 19.02.2016 um 00:14 schrieb Chris:
It's probably one of three things:
1. Your android phone is defaulting to pull down only new unread mails, or
Possible, but not normal behaviour.
My thoughts as well. I use the same phone with other ActiveSync hosts
with no problem. I have set it up exactly the same in each case.
2. Sogo is defaulting to activesync only new unread mails to your
android phone, or
No, it always delivers all emails to the phone.
Perhaps sogo thinks, that this phone already did get those emails.
In order to rule that out, you would have to purge all ActiveSync
informations for that client and start a new sync.
What are your settings in sogo.conf for
SOGoMaximumPingInterval
SOGoMaximumSyncInterval
SOGoInternalSyncInterval
SOGoMaximumSyncWindowSize
SOGoMaximumSyncResponseSize
WOWatchDogRequestTimeout
SxVMemLimit
Which timeout is set in the ProxyPass directive in your apache
configuration for the ActiveSync part?
I suspect, that the synchronization is interrupted either by apache or
by the watchdog.
Or you have set up a very slow synchronisation, which will take ages to
complete.
My settings are:
SOGoMaximumPingInterval = 354;
SOGoMaximumSyncInterval = 354;
SOGoInternalSyncInterval = 30;
WOWatchDogRequestTimeout = 10;
SOGoMaximumSyncResponseSize = 512;
SOGoMaximumSyncWindowSize = 256;
SxVMemLimit = 512;
The proxypass timeout is 360:
ProxyPass /Microsoft-Server-ActiveSync \
http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync \
retry=60 connectiontimeout=5 timeout=360
3. Dovecot is defaulting to take whatever commands SOGo is giving it
during the activesync protocol conversation and interpret those commands
to mean only to serve up only the new unread mails.
Those are normal IMAP commands, also used in the web interface.
As that works, no problem here either.
Kind regards,
Christian Mack
On 2/18/2016 5:36 PM, John Underwood wrote:
Thanks for the information. Looking at a Imap dump from Sogo it's
clear that the X-GUID extension is alive and well, just not
advertising itself).
So it looks like the strange synchronisation behaviour is due to some
other aspect of the setup. Does anyone have any other ideas? I haven't
seen any other similar posts on this list for similar problems so I'm
rather baffled.
On 18/02/2016 22:04, Chris wrote:
On Dovecot imap server 2.2.8 and newer, X-GUID should be used by SOGo
2.2.11 and newer. ANNOTATE is the old outdated standard still used
by Cyrus imap server.
See this resolved bug from Dec 2014:
http://sogo.nu/bugs/view.php?id=3018
Also see more about dovecot and x-guid:
http://www.dovecot.org/list/dovecot/2014-September/097907.html
On 2/18/2016 4:11 PM, John Underwood wrote:
I have a small server setup which is working very well with the
exception of EAS on android devices (I haven't tried iOS devices).
The setup is as follows:
- Centos 7
- dovecot 2.2.10
- samba authentication using Sernet samba 4.2
- apache 2.4.6
- SOGo 3.0.1 (previously on 2.3.x with the same symptoms).
Thunderbird clients work fine
The web front end works fine (version 2 and now version 3).
When I first sync an android phone with the server using ActiveSync,
it flashes up "Syncing x/5500" emails. It then syncs about 10-15 and
no more. Contacts and calendars sync fine.
Subsequently the phone will collect e-mail automatically as it
arrives providing it hasn't already been read using Thunderbird. If
an e-mail /has/ already been read using Thunderbird it doesn't sync
to the phone at all.
Looking through the installation guide (p5), I note that the IMAP
server needs the ACL, UIDPLUS, QRESYNC, ANNOTATE (or X-GUID)
extensions. I have the first three but I can't find any reference to
the ANNOTATE or X-GUID extensions in the dovecot documentation.
Could this be the problem?
Any help would be much appreciated!
--
[email protected]
https://inverse.ca/sogo/lists
