Z-Push when using Kopano

• 

  PHP Notice: Use of undefined constant
  • KaBi  

  2
  0
  Votes
  2
  Posts
  19
  Views

  

  Hi @KaBi, @KaBi said in PHP Notice: Use of undefined constant: I edited the line in kopano.php and put ’ around the constant, no notice anymore - is this ok to leave it like this? No, not really. Apparently /etc/gabsync.conf.php was not updated during Z-Push upgrade. Make sure that the upgrades also update the Z-Push config files. Otherwise you may manually add the following files to /etc/gabsync.conf.php // Whether to hide the group Everyone in the synced GAB. define('GAB_SYNC_HIDE_EVERYONE', false); Then remove the changes you made to kopano.php. Manfred
• 

  USE_FULLEMAIL_FOR_LOGIN not working as expected
  • cpzengel  

  6
  0
  Votes
  6
  Posts
  31
  Views

  

  Hi @cpzengel, @cpzengel said in USE_FULLEMAIL_FOR_LOGIN not working as expected: @Manfred said in USE_FULLEMAIL_FOR_LOGIN not working as expected: if your users login using their full email address and not just the username, then you have to set thats the solution, i already find out the question is, why is the same variable in two configs? because autodiscover and Z-Push are two different components which might be installed on different systems or you might want to have different settings, so it doesn’t make sense to have the same config for both. Manfred
• 

  Z-Push in Ubuntu 20.04
  • Gerald  

  3
  1
  Votes
  3
  Posts
  42
  Views

  

  Thanks, I did. Glad the 18.04 package workds
• 

  Outlook 2016 and Outlook 2019 error
  • WalterHof  

  2
  0
  Votes
  2
  Posts
  50
  Views

  

  Hi @WalterHof, @WalterHof said in Outlook 2016 and Outlook 2019 error: The autodiscover of Outlook 2016 worked with Z-Push until recently. Since a few days we observe that the autodiscover of Outlook 2016 writes the same errors in the autodiscover.log as Outlook 2019. Is there any information that Microsoft has changed the autodiscover of Outlook 2016 in the last days with a patch? There was an Outlook update in September, but Microsoft didn’t detail what has changed: https://support.microsoft.com/en-us/help/4484511/september-1-2020-update-for-outlook-2016-kb4484511. How can I make the autodiscover of Outlook 2016 and 2019 compatible with Z-Push? First some information on autodiscover and what is implemented in Z-Push. First of all Z-Push only implements POX (plain old xml) autodiscover because it’s what the mobile devices use. In the autodiscover request there’s AcceptableResponseSchema tag. For ActiveSync accounts its value is “http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006”. For an exchange account its value is “https://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a”. Z-Push only processes the request and returns a valid response if the client requests mobilesync schema. Z-Push doesn’t return a valid response for outlook schema because it’s not an exchange server (see https://docs.microsoft.com/en-us/exchange/client-developer/web-service-reference/pox-autodiscover-response-for-exchange how such a response looks like). So, if the client (a mobile device or Outlook) doesn’t request mobilesync as AcceptableResponseSchema, Z-Push autodiscover won’t work and the user has to configure the account manually. Manfred
• 

  z-push on Debian 10 with php 7.3
  debian 10 php 7.0 php 7.3 t-push upgrade • • WalterHof  

  4
  0
  Votes
  4
  Posts
  20
  Views

  

  Hi @WalterHof, z-push-common has a dependency on php-soap package without specifying its version. As you already had php7.0-soap installed, it was good enough for Z-Push. As you were trying to remove it without installing a newer php-soap version first, Z-Push would be removed as well. Also, this wouldn’t have happened if the php7.0* packages were upgraded to php7.3* packages during the OS upgrade, so that’s the issue you have to look at. Manfred
• 

  Autodiscovery for Outlook 2016
  • Coffee_is_life  

  10
  0
  Votes
  10
  Posts
  68
  Views

  

  I’ve found this post, the matter is closed :-)
• 

  [Samsung BUG] Z-Push does not synchronise birthday entries if the contacts birthday was before 1980?
  • AnotherAndy  

  11
  0
  Votes
  11
  Posts
  159
  Views

  

  Yesterday I had a Samsung S10e device for testing with me. I added my z-push Account and unfortunately here I got the same issue. No birthday entires for “older” people are shown. On my Outlook 365, in the Webapp and even on Windows 10 Email - all connceted via Z-Push - the Birthday events are shown… and Samsung never replied to my “Bug” in the calender Looks like I am the only on with that issue. I can live with it because I nearly every day use Desktop Clients, so the birthday popups are shown. so this message was more FYI br Andreas
• 

  Can not send emails from iphone
  • Eric  

  4
  0
  Votes
  4
  Posts
  25
  Views

  

  Z-Push 2.4 is very old, consider updating to 2.5.2
• 

  z-push log errors
  • ckruijntjens  

  2
  0
  Votes
  2
  Posts
  18
  Views

  

  Hi @ckruijntjens, there’s already a thread regarding this issue: https://forum.kopano.io/topic/2269/z-push-2-4-5-sync-issue-0xffffffff8004010f. Manfred
• 

  Kopano and outlook Extention Syncronization loop
  • HS-Systeme  

  6
  0
  Votes
  6
  Posts
  31
  Views

  

  @HS-Systeme said in Kopano and outlook Extention Syncronization loop: normaly i cant update other versions as from univention Not true when it comes to Kopano and Z-Push: https://kopano.com/blog/staying-up-to-date-with-kopano-releases-on-ucs/
• 

  [FATAL] [pieter] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
  • pwhooftman  

  15
  0
  Votes
  15
  Posts
  76
  Views

  

  Solved! After switching over from the Synology package MariaDB10 to a docker container Mysql (and a Phpmyadmin container to administer the Mysql database in that container), all syncing has been flawless. Zero errors and warnings since the completion of the initial sync to my mobile and pc’s. So all previous assumptions that the problems had to do with restoring from a previous Koppano install where false. Also, i rule out a cause in my specific setup, because i did a complete Synology DSM re-install prior to trying to install and use Kopano4s with MariaDB10. From the very first install attempts a few months back, but also on that freshly installed DSM, i had strange errors where kopano4s could not connect to the database, or would only create like 17 out of the 29 desired tables, or the package had to be restarted twice before the docker container would not crash. In my opinion, Kopano4s and MariaDB10 is a bad combination.
• 

  Error, mapi_msgstore_openentry() failed: 0xFFFFFFFF80070005
  • righter83  

  2
  0
  Votes
  2
  Posts
  16
  Views

  

  Hi @righter83, I think it’s related to https://forum.kopano.io/topic/2269/z-push-2-4-5-sync-issue-0xffffffff8004010f. Manfred
• 

  Autodiscover seems to be broken
  • MS-FSTLN  

  5
  0
  Votes
  5
  Posts
  57
  Views

  

  Hi Manfred, thanks again for your help. And I’m sorry for the late reply. I checked my nginx config files again. I made a huge mistake when combining the webapp and z-push configuration because my webserver listens only to one domain. So the php-fpm configuration was wrong inside the combined configuration file. After fixing this AutoDiscovery and ActiveSync works both fine. For those few who need exactly this or a similar configuration, here are the modifications I made (even if those are not ideal): Add the following lines to the end your webapp configuration: location /Microsoft-Server-ActiveSync { # If you're using PHP-FPM uncomment the following lines. include fastcgi_params; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param REQUEST_URI $1; fastcgi_param PHP_FLAG "magic_quotes_gpc=off \n register_globals=off \n magic_quotes_runtime=off \n short_open_tag=on"; fastcgi_param PHP_VALUE "post_max_size=20M \n upload_max_filesize=20M \n max_execution_time=3660"; fastcgi_param HTTP_PROXY ""; # Mitigate https://httpoxy.org/ vulnerabilities fastcgi_read_timeout 3660; # Z-Push Ping might run 3600s, but to be safe alias /usr/share/z-push/index.php; access_log /var/log/nginx/z-push-access.log; error_log /var/log/nginx/z-push-error.log; # Attachments ca 15MB max (since binary data needs to be base64 encoded in mine, which results in in about 33% overhead) client_max_body_size 20m; client_body_buffer_size 128k; # Select one of the fastcgi_pass values or adapt to your configuration include snippets/z-push-php.conf; } location /AutoDiscover/AutoDiscover.xml { # If you're using PHP-FPM uncomment the following lines. include fastcgi_params; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param REQUEST_URI $1; fastcgi_param PHP_FLAG "magic_quotes_gpc=off \n register_globals=off \n magic_quotes_runtime=off \n short_open_tag=on"; fastcgi_param PHP_VALUE "post_max_size=20M \n upload_max_filesize=20M \n max_execution_time=3660"; include snippets/z-push-autodiscover.conf; include snippets/z-push-php.conf; } location /Autodiscover/Autodiscover.xml { # If you're using PHP-FPM uncomment the following lines. include fastcgi_params; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param REQUEST_URI $1; fastcgi_param PHP_FLAG "magic_quotes_gpc=off \n register_globals=off \n magic_quotes_runtime=off \n short_open_tag=on"; fastcgi_param PHP_VALUE "post_max_size=20M \n upload_max_filesize=20M \n max_execution_time=3660"; fastcgi_param HTTP_PROXY ""; # Mitigate https://httpoxy.org/ vulnerabilities fastcgi_read_timeout 3660; # Z-Push Ping might run 3600s, but to be safe include snippets/z-push-autodiscover.conf; include snippets/z-push-php.conf; } location /autodiscover/autodiscover.xml { # If you're using PHP-FPM uncomment the following lines. include fastcgi_params; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param REQUEST_URI $1; fastcgi_param PHP_FLAG "magic_quotes_gpc=off \n register_globals=off \n magic_quotes_runtime=off \n short_open_tag=on"; fastcgi_param PHP_VALUE "post_max_size=20M \n upload_max_filesize=20M \n max_execution_time=3660"; fastcgi_param HTTP_PROXY ""; # Mitigate https://httpoxy.org/ vulnerabilities fastcgi_read_timeout 3660; # Z-Push Ping might run 3600s, but to be safe include snippets/z-push-autodiscover.conf; include snippets/z-push-php.conf; } And don’t forget to configure your php-fpm settings in /etc/nginx/snippets/z-push-php.conf …I heared that some modules don’t work if you forget this… And thanks again to @Manfred for the help
• 

  Kopano gab not visible in outlook 2016
  • WalterHof  

  5
  0
  Votes
  5
  Posts
  36
  Views

  

  KOE 2.1 should have resolved the issue with the gab because of signatures: https://documentation.kopano.io/kopano_changelog/koe.html#kopano-ol-extension-2-1-20-final
• 

  kopano gab not visiable in outlook 2019
  • ckruijntjens  

  19
  0
  Votes
  19
  Posts
  75
  Views

  

  Hi @ckruijntjens, today I got feedback from a colleague using Office 2019 and Outlook over ActiveSync with KOE. He said that GAB works fine for him. Manfred
• 

  second source ldap for adressbook
  • segro  

  14
  0
  Votes
  14
  Posts
  829
  Views

  

  If I get you right, you want to use something like a meta-ldap: a single ldap server which combines the results of multiple other ldap servers. Check out https://github.com/kgalal/meta-ldap (never tested, first google hit, maybe there are more meta-ldaps). Cheers Peter
• 

  Event deletion not propagating?
  • imm  

  7
  0
  Votes
  7
  Posts
  38
  Views

  

  Hi @imm, yes, recreating from scratch and testing if it still happens would be helpful. Manfred
• 

  AD groups used as address lists not visible in Outlook 2016
  • WalterHof  

  1
  0
  Votes
  1
  Posts
  11
  Views

  No one has replied

• 

  This topic is deleted!
  • ckruijntjens  

  1
  0
  Votes
  1
  Posts
  11
  Views

  No one has replied

• 

  Z-Push Kopano mit Jolla Sailfish Phone
  • davodego  

  15
  0
  Votes
  15
  Posts
  400
  Views

  

  Hello, I have made a workaround for this issue. A systemd timer check every 5 minutes if the idle connection on port 443 is established. If not, the EAS-Sailfish Service is restarted. See https://github.com/davodego/connection_check for the files. Maybe it helps. Sailfish isn’t able to repair this bug.