Hi Maxxer, I have used the beta4 version of the script, and it works great to get and deploy a new certificate. All I needed to do was temporarily open port 80 on the firewall. However, if I run the command /path-to/certbot-zimbra-0.4.0-beta/certbot_zimbra.sh -n a second time, I get a menu - presuma...

Release 68 of the z-push zimbra backend has been uploaded to SourceForge https://sourceforge.net/projects/zimbrabackend/ As always - please read the full Release Notes before upgrading Changes Made To Revision 68: - Rename BackendSearchZimbra constructor for PHP 7+ compatability - Add third paramete...

We had this happen unexpectedly a number of months ago. We had to follow the troubleshooting steps on the Microsoft Live Postmaster site to get unblocked. It was a largely automated process.

https://postmaster.live.com/pm/troubleshooting.aspx

Nginx is mandatory for the admin console now?

Right... but, I had never selected the check box for "proxy enabled" for the admin console, and in the old version the link in the webmail client was therefore set to 7071, whereas in the upraded version the checkbox is still not selected but the link in the webmail is set to 9071

Hi I am testing the upgrade process from 8.7 to 8.8 and for some reason in the upgrade process the port number in the Webmail client for the Admin Console link gets switched from the normal :7071 to :9071 - and as a result it fails to connect. If I manually change the port number in the new Admin Co...

There is a completely open SOAP API - https://wiki.zimbra.com/wiki/SOAP_API_R ... with_ZCS_8 - but you may be re-inventing the wheel
What is the use case?
How many users are you talking about?

Hello I'm testing Z Push. Z I'm getting an error like below, unfortunately. What can be the problem ? Can you help? WBXMLException: Internal Server Error - code: 0 ser-agent: 'Android-SAMSUNG-SMCCCCX/101.700' Request could not be processed correctly due to a WBXMLException. Please report this. Typi...

Release 67 of the z-push zimbra backend has been uploaded to SourceForge <https://sourceforge.net/projects/zimbrabackend/> As always - please read the full Release Notes before upgrading Changes Made To Revision 67: - Allow for iPxx device meeting modification request with shadow data - Changed ZIMB...

You can also likely fix it, and still get the emails by adding MAILTO=anAccountThatExists@your.domain MAILFROM=anAccountThatExists@your.domain as the first 2 lines of the zimbra crontab. This will send the email from the MAILFROM account to the MAILTO account. They should be inserted before the line...