@mkuemmerle

yes I was looking for this information.

Thank you.

Walter

We reverted back to 2.6.2 in the final repo as there are more issues with this release, so it’s highly recommended to downgrade to this version

@mahescho ok, but even if what is logged does not look like an error to you if may provide additional insights here. Or does nothing get logged at all? Since this happens in a web browser there may also be additional hints in the browser console.

Coming back to z-push-admin do these additionally selected folders show there? Can additional folders be added through z-push-admin?

Maybe it would make sense to follow this up with the Kopano support directly, so that someone could have a look at the system directly?

@fbartels I tried your way. Works like a charm. Thanks a lot!

@fbartels ok thanks, i didnt knew how this is implemented

probaply now these clients still try to push something to kopano, though the messages get removed. Maybe something client side needs to change as well for this.

Hi @manfred,

I don’t have a support subscription so that won’t help.
All that was left was to start from scratch so I purged any z-push package from my server and installed z-push again.
And to my big surprise Outlook started to sync without any state errors and completed the full sync after some time.
So, cause unknown but issue resolved.

Thanks for your support!

Best regards,
Boudewijn

@manfred Thanks! I just upgraded to 2.6.2 and everything works fine.
br
Andreas

Hi @raphi59,

@raphi59 said in Z-Push Certificate Based Authentication:

Hello,

I want to configure certificate based authentication for z-push so that only devices with a client certificate from our ca are able to synchronize via activesync.
I tried to set the following option with the ca from a Univention server, but can still synchronize without setting a client certificate.

// When using client certificates, we can check if the login sent matches the owner of the certificate. // This setting specifies the owner parameter in the certificate to look at. define("CERTIFICATE_OWNER_PARAMETER", "SSL_CLIENT_S_DN_CN");

In Z-Push client certificate is optional for authentication. That means that the users without a certificate will be able to login using the correct username and password. If you want to allow only users with certificates, you’ll have to do some code changes.

And if I’m setting a client certificate the client cannot setup the account (I cant see any errors in the z-push logs).

Am I missing a configuration or am I making another misconfiguration?

It’s difficult to say anything without Z-Push/webserver logs. Is the auth user the same as SSL_CLIENT_S_DN_CN value?

Manfred

@fsoelch
Good to know there is a 20.04 repo available now. While updating the repo link from 18.04 to 20.04 I also noticed that the old URL I was using was http and not https - another welcome change I had not adopted.

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

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

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

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

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

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

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

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

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

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.