Zimbra Forums

We were victim of this when it came out. We updated our system to 8.7.11_P10 on Apr 06.

After activity in this thread I checked our system and found new random char files created 09:58, Apr 25.

Not good. And this is on a updated and cleaned system!

Is this release been un-released?

The download pages now show 8.7.11 (and 8.8 still in beta)
https://www.zimbra.org/download/zimbra-collaboration

Confusing for end users and no information regarding this...

Hi,

We have many shared calendars in our organization.

How can i get a list of users with access to one shared calendar. In the GUI I can see the members but I can't copy this list (several hundred users in some shares).

Can this be done from terminal?

doing the upgrade from 8.7.11 FOSS (Centos 7.3) to 8.8.4 the problem is still there I just finished the same test, 8.7.11 to 8.8.4, and I confirm that the problem remains. The "workarond" below still works (even without the zimbraVirtualIPAddress part). $ zmprov md bxxxol.se zimbraVirtual...

Have either of you tried the fix that's mention in the thread and the bug report? If you refer to me, so yes. See my posts in the other thread: https://forums.zimbra.org/viewtopic.php?f=15&t=62695#p278628 And I repeat my statement: "I really think this should be investigated further and fi...

Same problem here:
viewtopic.php?f=15&t=62695

OK, the problem most likely rise when hostname is not the same as the name used to access the webmail (very common scenario I guess. somehost.domain.com vs mail.domain.com). This solved it for me: $ zmprov md bxxxol.se zimbraVirtualHostname mail.bxxxol.se zimbraVirtualIPAddress 192.168.1.12 $ libexe...

Some additional findings: If I access the webmail by the hostname it works, but if I access by the generic alias I get the empty response: postoffice.bxxxol.se => OK mail.bxxxol.se => FAIL postoffice.bxxxol.se is the fqdn of the server. mail.bxxxol.se is a DNS alias to postoffice.bxxxol.se (CNAME) T...

I do not really understand the discussion in that thread.

Can modify something now to verify and/or fix this issue?
Can something be checked before update to not trigger this problem?

This feels like a show-stopper for upgrads, or is it only affecting some configurations/systems?

Same issue here:
viewtopic.php?f=13&t=62696