good morning @remcov,
for the timeout, there schould be some lines in z-push-conf.php:
// Maximum response time
// Mobiles implement different timeouts to their TCP/IP connections. Android devices for example
// have a hard timeout of 30 seconds. If the server is not able to answer a request within this timeframe,
// the answer will not be recieved and the device will send a new one overloading the server.
// There are three categories
// - Short timeout - server has up within 30 seconds - is automatically applied for not categorized types
// - Medium timeout - server has up to 90 seconds to respond
// - Long timeout - server has up to 4 minutes to respond
// If a timeout is almost reached the server will break and sent the results it has until this
// point. You can add DeviceType strings to the categories.
// In general longer timeouts are better, because more data can be streamed at once.
define('SYNC_TIMEOUT_MEDIUM_DEVICETYPES', "SAMSUNGGTI");
define('SYNC_TIMEOUT_LONG_DEVICETYPES', "iPod, iPad, iPhone, WP, WindowsOutlook");
make sure that WindowsOutlook is listed in long_devicetypes and as you can see in the log “Outlook” should be present too
(03/04/2018 20:19:59 [ 3296] [ INFO] [vincent@domein2.nl] cmd=‘Ping’ memory=‘2.44 MiB/2.00 MiB’ time=‘90.10s’ devType=‘Outlook’ devId=‘1ca749486aa9aebd’ getUser=‘vincent@domein2.nl\vincent@domein2.nl’ from=‘52.232.100.50’ idle=‘90s’ version=‘2.3.8+0’ method=‘POST’ httpcode=‘200’)
for the error with buffer cant be deleted, i got no clue, maybe an upgrade from 2.3.8 to z-push 2.3.9 will solve this. - you can try to complete resync the device and / or delete everything from phone/ourlook and from z-push
z-push-admin -a remove -u <username> -d <deviceID>
deviceid can be obtained by
z-push-admin -a list -u <username>
than run
z-push-admin -a clearloop
z-push-admin -a fixstates
and connect the device as a new device
the error in server.log, i need further information:
is kopano linked with activeDirectory
if yes, in /etc/kopano/ldap.cfg should be somethhing like:
# Optional, default = uid
# Active directory: sAMAccountName
# LDAP: uid
ldap_loginname_attribute = sAMAccountName
what does “id <username>” say, does it get your userinfo?
does it refere to uid or sAMAccountName? - check with ldapsearch (package openldap-clients) for uid and sAMAcountName
what does kopano-admin --details <username> say? does it get all properties?
//the loop detection is quite normal
for the spooler.log, check the log settings in spooler.cfg and incrase it to 5 (info) - and log_method = file
in the past i got a similar error, refering to postfix as it wont delete sended items from queue
check this behaviour aswell (if you are using postfix :) )
postqueue -p
regards,
coffee_is_life
