I don’t have any issues that can be attributed to this log, and it is good to know there is no need to worry. It does make curious though what those flag changes could be if there are absolutely no changes in the mailbox.

Ok, so I changed in /etc/z-push/imap.conf.php

define('IMAP_EXCLUDED_FOLDERS', 'dovecot.sieve|Archiv|Mailing');

to

define('IMAP_EXCLUDED_FOLDERS', 'dovecot.sieve');

or

define('IMAP_EXCLUDED_FOLDERS', '');

Obviously, z-push.log is much larger now, as it (within a second) works through all folders. But after that second, nothing happens, then I get an error on my phone that e-mails could not be received, as the connection with the server has failed. And minutes later, there is the old error in the log again:

08/12/2017 18:42:51 [ 3138] [FATAL] [user@domain.com] Fatal error: /usr/share/z-push/backend/imap/imap.php:2344 - Allowed memory size of 1073741824 bytes exhausted (tried to allocate 4096 bytes) (1)

Other symptoms are also the same, i.e. long running dovecot-imap (high CPU consumption) and apache2 (high memory consumption) threads on the machine.

Unfortunately I can’t see anything wrong with the log. The device never sends any changed/new data to the server, it just starts from scratch.
Please check if in the profile settings you only activate contacts (disable mail, calendar, tasks and notes).

Do you have any other phone available you could test with?
Not sure how else to help, there is nothing in the log.

You could try to cat a log from the android device (adb logcat). Perhaps we get an indication what’s going on.

Yes, all depends on client settings and on number of devices per user (more devices, more blocking possibility),; I changed zimbra default account block settings to more suitable values and I’ll set personalized values on the mailboxes with many devices.
Thank you.

Another possibility is to use LDAP authentication on the z-push apache server. This would prevent z-push from interacting with the zimbra webmail for all unauthenticated sessions. You can add fail2ban, or similar method to greylist/blacklist ip addresses that are repeatedly getting bad logons - you can see the discussion here - https://forum.kopano.io/topic/682/z-push-behind-basic-authentication/10

@rpalla You still have not answered my questions about any errors that might be appearing in the log files.

Hello @powercommy ,

we had some server troubles over the weekend with the system hosting the atlassian stack for z-hub.io. The system is now back online. You can find our contribution guidelines at https://wiki.z-hub.io/display/ZP/Development+guidelines

You really should not be running anything as old as zimbra 8.0.7 - there are so many security fixes and bug fixes that have gone into zimbra since then.

How many clients are syncing to the server?

Running into an out-of-memory error is definitely a good indication why there is nothing shown in Outlook.
We’ve just implemented a ticket that works better for Outlook and prevents these errors, unfortunately it’s not yet merged (into Z-Push 2.4).

There are two immediate solution:

increase the php memory limit in your php.ini to 256 or 512 MB (restart apache afterwards)
and/or reduce the amount of SYNC_MAX_ITEMS in your z-push config file. 100 should be a good starting point.

Cheers,
Sebastian

@Manfred : Desktop Clients worked fine

Maybe I had some typo error or I don’t know what went wrong in the past. I changed the IMAP_OPTIONS back to /ssl and it works.

Emails are also synced to the client now, the only thing I am struggling with is carddav and caldav with owncloud. But I need to invent first, so I can mark this thread as solved.

Andy

Reading more carefully the log, I noticed

Zimbra->Logon(): FATAL: Zimbra Backend Requires PHP-CURL

I was missing php-curl.
So

apt install php-curl phpenmod curl systemctl apache2 reload

Hrrm, I know about as much about PHP as I do about playing the Antagonistic Undecagonstring two-handed… so sure, why not! :-)

Is this still an issue?

Please let us know which z-push you are using, and if it is the zimbra backend please le me know the release number

It’s been about a month now, has been running flawlessly here since the last set of changes, and I’ve created a pull request as a consequence… no code changes since roughly a month ago.

After digging around the code some the obvious (and “most-correct”) way to do this is to enhance the IMAP php library so that when it is sent an “open” it checks for the capability and, if present and the environment variable with the remote IP is set (which it will be if it was called an upstream “thing” that sets it, such as a web server) it then sends that stanza down after the password is accepted.

This would cause the IMAP php module to log it to Dovecot (or any other compatible IMAP server) for all users of it, not just Z-push, and it requires no code changes in the Z-push codebase itself. I run FreeBSD and haven’t dug into the php development community at all, so while I can certainly grab the FreeBSD port and do it in there that doesn’t help anyone except possibly FreeBSD users if I sent the patch back into their system, and it’s subject to rot there over time. The “right” approach to go after this is in the php upstream of course; I’ll stick a note in my “list of things to look at”, but I can’t commit to a when I’ll get to it.