Page 2 of 2

Re: No review and cannot open office files directly after upgrade to 7.3

Posted: Mon Jul 24, 2017 9:30 am
by foxval
jorgedlcruz wrote:Hi guys,
With the move to Node Web kit framework, some functionality is different, this is one of them.
It's a known issue and we will keep working to resolve it.

Best regards


Hello !
Very annoying bug, and no fix... yet it's july.
Will it be fixed?
7.2 worked just fine (but there is no option to disable update reminder), uers who updated ZD complain...

Re: No review and cannot open office files directly after upgrade to 7.3

Posted: Thu Jul 27, 2017 11:26 am
by PriteshGajjar
We are release 7.3.1 with this fix in first week of August.

Behaviour would be as below:
- You click on attachment link (file name link), it will download first and then automatically open with most appropriate application chosen by OS.
- If you click "Download", it will simply download that file. (no open)
- If you want to see downloaded file there is an option of "Downloads" on home screen.

Re: No review and cannot open office files directly after upgrade to 7.3

Posted: Fri Jul 28, 2017 3:48 am
by bhwong
Anyone facing an issue whereby users of Zimbra Desktop can no longer login to their web client unless they switch from advanced to standard mode?

Zimbra Support suspect this:

We have checked provided log files and found continuous DoS alerts for IP "x.x.x.x" where from user xxx connecting 'Zimbra Desktop'.
DoS filter throttles connection requests when client sending large number of requests over a very short period of time.

Please see the following DoS alerts for user xxx, and user must be facing slowness due to dos filter throttling.
Could you please whitelist incoming IP "x.x.x.x" and then check slowness behavior on webclient and Zimbra Desktop.

Re: No review and cannot open office files directly after upgrade to 7.3

Posted: Mon Jul 31, 2017 2:13 pm
by budy
The only times, we do see these problems is, when a user has changed their passowrd in our AD and some client - this hasn't actually to be ZD, tries to login with the old one, e.g. macOS' calendar agent… (this is a bugger one!)

However, what I'd never do is to perform any kind of IP whitelisting for any network where user machines are running…! Call me a paranoid, but in this case whitelisting should not be done. Rather experiment with the DoS values and find some, that work in your environment, but don't allow any host to pound onto your Zimbra setup without limits.

Cheers,
budy