/usr/share/z-push/backend/caldav/caldav.php:841 - ZP-1571
/usr/share/z-push/include/mimeDecode.php:865 - ZP-1579
BackendIMAP->delete_calendar_dav(): event not found, we will end with zombie events - a mail with a cancelation of an event was found, the calendar entry has most likely never existed, so this is to be expected…

These are new to me:
/usr/share/z-push/lib/core/streamer.php:309 strlen() expects parameter 1 to be string, array given (2)
/usr/share/z-push/include/z_RFC822.php:182 trim() expects parameter 1 to be string, array given (2)

I have some open tickets there on a variety of issues I want to improve Z-Push.
But I am no professional developer and I am doing this mostly in my free time.

@bob4os

no error message, just the info that the connection was closed…

Jun 13 13:31:22 imap(maedball)<1392295><MuoAEaTE3r0AAAAAAAAAAAAAAAAAAAAB>: Info: Connection closed (No commands sent) in=0 out=400 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jun 13 13:31:24 imap-login: Info: Login: user=<maedball>, method=PLAIN, rip=::1, lip=::1, mpid=1392755, TLS, session=<nkutFKTEuL4AAAAAAAAAAAAAAAAAAAAB>

Did you enable GAL via SEARCH_PROVIDER in the main config.php?
This will limit search to contacts only, serverside mail search will not work properly anymore.

I’m using the combined backend with CardDAV and added some lines there to include the SearchLDAP backend, but it is a hack I’m not happy with…

Are you interested in using both? Maybe I can work out a proper solution to this.

@manfred
I finally got a few hours to debug through this. Bottom line is

ContentParameters class has a deletesasmoves property with a default “unset” value of true. This is never used anywhere in the z-push-develop source tree as far as I can see. So passing that property in the ContentParameters object to the backend functions is of zero value.

SyncParameters class has a deletesasmoves property with a default “unset” value of false. This is updated based on the presence of the DeletesAsMoves flag in the incoming sync collection. It is subsequently used to decide between calling ImportMessageMove or ImportMessageDeletion - so if backend->DeleteMessage gets called it is because the SyncCollection dictated that. So, the basic code logic is correct - and the ticket ZP-1604 should be closed on that basis.

However, there is one remaining issue - the default “unset” value of deletesasmoves in SyncParameters is set to false. This is incorrect according to the specification which states

“If the client wants to permanently delete items, the request MUST include the DeletesAsMoves element with a value of 0 (FALSE). A value of 1 (TRUE), which is the default, indicates that any deleted items are moved to the Deleted Items folder. The default is assumed when the DeletesAsMoves element is either empty or not present.”

I will open a separate ticket for that.

@manfred yes. Unfortunately that didn’t work. I decided to turn all safety and security options off and have unencrypted traffic for now until I can make it work in general but so far I am running in more issues in the backends, this time caldav. see here: Cal Dav Sync error

So the include/z_caldav.php code does not work to determine the calendars on the Synology either. I made the following changes, which I think should work generically, to fix the problem:

628,631c628,630 < // not sure why this is here but doesn't seem to work and doesn't find principal/skip it < // if ( !isset($calendar_urls[$href]) ) { < // continue; < // } --- > if ( !isset($calendar_urls[$href]) ) { > continue; > } 634d632 < $flag = true; 647,649d644 < case 'DAV::principal': < $flag = false; < break; 652,655c647,648 < if ( $flag == true) { < $calendar->id = rtrim(str_replace($this->calendar_home_set[0], "", $calendar->url), "/"); < $calendars[] = $calendar; < } --- > $calendar->id = rtrim(str_replace($this->calendar_home_set[0], "", $calendar->url), "/"); > $calendars[] = $calendar;

For anyone interested: I created an ansible playbook that involves setting up Z-push as multi-tenancy here

@cjm51213 Sorry, I never noticed your post.

If you log into the Zimbra admin, and go to Configure->Domains-><your domain>

You will see the 3 settings.
Public service hostname
Public service protocol
Public service port

These are what z-push picks up from the user session when it first connects - as in a multi-server environment it is important to connect to the actual MTA that hosts the user’s account. It overrides whatever you have set in your ZIMBRA_URL with a url constructed from these values.

It sounds like you may have changed the zimbra proxy settings during your “move” which can cause this issue.

The reason that the folder list gets populated is that is is also returned in the payload from the initial login request. The reason no other data gets populated is that a connection cannot be made to the overridden ZIMBRA_URL (as described above)

I suggest you check out the zimbra wiki proxy page to check if you have configured your proxy correctly. https://wiki.zimbra.com/wiki/Enabling_Zimbra_Proxy_and_memcached

Pull request got merged, Z-Push release 2.6.3 will most likely contain the fix.

I don’t know if it is still relevant, but as far as I know, ActiveSync protocol does not support sharing calendars.

SabreDAV is able to share calendars - as you already know.

But:
With DAViCal you are able to add a “binding” (like an alias) to a shared calendar into your calendar homeset.
I think it is RFC5842 and SabreDAV does not seem to support it.
(https://sabre.io/dav/standards-support/)

Z-Push does not detect shared calendars without binding them to your homeset right now.

Hi @Manfred,

never mind. Decision have been made to ditch this project. However, thanks for taking care.

Hi @1san,

are there any addressbooks at all? Is the carddav backend configured correctly?

Manfred

@zgokan Can you show a screenshot of composing the email in zimbra.

Also, can you confirm you have configured the zimbra backend to load - it will not auto-load like other Kopano supplied backends

in config.php (usually linked to /etc/z-push/z-push.conf.php you should have

// the backend data provider define('BACKEND_PROVIDER', 'BackendZimbra');

How large is the image?

Have you checked your z-push.log file and your web server log files to see if there are errors?

You could generate a log file for the affected user showing a full cycle, starting with a Ping, send a new message that will cause the issue, you will see the Sync to export the message to the device, followed by another Ping.

Make sure you set the loglevel to at least debug for the special log file, and you add the same userid as is configured on the device - either a full email address or a username

define('LOGUSERLEVEL', LOGLEVEL_DEBUG); $specialLogUsers = array(); $specialLogUsers[] = 'user@domain'; OR $specialLogUsers[] = 'user';

This should create an extra log file called user_domain.log or user.log

Please share that log file

@Manfred OK. Thanks. I will implement a workaround for now.

HI @orlovnv,

@orlovnv said in 2 device one user sync problem:

z-push latest stable, combinedBackend Problem only with tasks when I create one on the nextcloud it doesn’t syncs to phone, I think the same problem when I create on one phone and it doesn’t sync to another

Please provide the exact version of Z-Push you are using. “latest stable” is not an exact version. In debian/Ubuntu repositories the latest stable is 2.4.5, in z-push.org repositories it’s 2.5.2, so if you just write “latest stable” it’s ambiguous. The version is logged in z-push.log at INFO level at the end of every request.

08/08/2020 14:46:57 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCardDAV' with 10 08/08/2020 14:46:57 [ 350] [DEBUG] [tasks] BackendCardDAV->ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:47:05 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink(30) 08/08/2020 14:47:05 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendIMAP' with 10 08/08/2020 14:47:05 [17272] [DEBUG] [tasks] BackendIMAP>ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:47:07 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink(30) 08/08/2020 14:47:07 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendIMAP' with 10 08/08/2020 14:47:07 [ 350] [DEBUG] [tasks] BackendIMAP>ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:47:15 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCalDAV' with 10 08/08/2020 14:47:17 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCalDAV' with 10 08/08/2020 14:47:24 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCardDAV' with 10 08/08/2020 14:47:24 [17272] [DEBUG] [tasks] BackendCardDAV->ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:47:26 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCardDAV' with 10 08/08/2020 14:47:26 [ 350] [DEBUG] [tasks] BackendCardDAV->ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:47:34 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink(30) 08/08/2020 14:47:34 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendIMAP' with 10 08/08/2020 14:47:34 [17272] [DEBUG] [tasks] BackendIMAP>ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:47:36 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink(30) 08/08/2020 14:47:36 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendIMAP' with 10 08/08/2020 14:47:36 [ 350] [DEBUG] [tasks] BackendIMAP>ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:47:44 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCalDAV' with 10 08/08/2020 14:47:46 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCalDAV' with 10 08/08/2020 14:47:53 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCardDAV' with 10 08/08/2020 14:47:53 [17272] [DEBUG] [tasks] BackendCardDAV->ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:47:55 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCardDAV' with 10 08/08/2020 14:47:55 [ 350] [DEBUG] [tasks] BackendCardDAV->ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:48:03 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink(30) 08/08/2020 14:48:03 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendIMAP' with 10 08/08/2020 14:48:03 [17272] [DEBUG] [tasks] BackendIMAP>ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:48:05 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink(30) 08/08/2020 14:48:05 [ 350] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendIMAP' with 10 08/08/2020 14:48:05 [ 350] [DEBUG] [tasks] BackendIMAP>ChangesSink - Not initialized ChangesSink, sleep and exit 08/08/2020 14:48:13 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCalDAV' with 10 08/08/2020 14:48:13 [17272] [DEBUG] [tasks] BackendCalDAV->ChangesSink - Changes detected 08/08/2020 14:48:13 [17272] [DEBUG] [tasks] BackendCombined->ChangesSink - Calling in 'BackendCardDAV' with 10 08/08/2020 14:48:13 [17272] [DEBUG] [tasks] BackendCardDAV->ChangesSink - Not initialized ChangesSink, sleep and exitcode_text

This log is not helpful at all. Felix posted a link which explains how to enable WBXML log.

so when I add task via web of next cloud task doesn’t sync to phone, but if I then add task in phone it sync to server and then appear task in phone which I add via web.
if I check task as done that one which I add via web appears again in phone and that which I add in phone disappear in server too.
sorry for my bad English

It looks like the backend doesn’t detect task changes in nextcloud. It’s not possible to tell why without logs and knowing your configuration.

Manfred