Zimbra Forums

Still happening on Release 8.8.6.GA.1906.UBUNTU14.64 UBUNTU14_64 NETWORK edition

The solution is "don't upgrade"!! Seems 8.8 was an "in hurry" release - Zimbra was used to be somekind of a "stable" product - this is going away the door also - not only the support (being miserable and irresponsive)

Seems no one is - this is crap and irresponsible support - don't be surprised of paying customers abandoning zimbra

using FQDN works, I don't have access to port 8443 port is closed on every systems I checked (only port 8080 works) Not here. https is broken after upgrade on ubuntu 14.04 from a working 8.7.11, always getting "ERR_EMPTY_RESPONSE" on chrome i.e. on logs: nginx.log: *26 client closed connec...

Not here. https is broken after upgrade on ubuntu 14.04 from a working 8.7.11, always getting "ERR_EMPTY_RESPONSE" on chrome i.e. on logs: nginx.log: *26 client closed connection while waiting for request, client: x.x.x.x, server: 0.0.0.0:443 Upgrade from 8.7 to 8.8 on Ubuntu smooth as sil...

Yes we have a support case on this since April!! They seem to have already reproduce as they already said "It looks like server side issue" on support e-mails ... and I've sent them additional logs as asked and I'm waiting.. You're right bugs seem to be ignored, this is sad - in this case ...

Still happening on Zimbra 8.8.4_BETA_1216 (build 20171130050632) - tested at https://universal.zimbra.io

Still happening on Zimbra 8.8.4_BETA_1191 (build 20171114060134)

It now connect ok with Nexcloud 12, But I can't upload files to the cloud, getting an "Unknown status code" - seems on zimbra side from mailbox.log SoapEngine - Only BatchRequest does not have a handler mapped to it. Request: /service/soap/BatchRequest, does not have a handler, log for fut...

maybe you are missing this:

zmprov ms mail.xxxx.xxx zimbraMtaSmtpSaslPasswordMaps lmdb:/opt/zimbra/common/conf/relay_password

just put in there your route
postmap /opt/zimbra/common/conf/bysender

and auth
postmap /opt/zimbra/common/conf/relay_password