Zimbra 7.2 and posixaccount + samba

[xpla]

PLEASE could someone fix this issue?!

We're quite desperate ...

[rosch]

As Bill already said in an earlier post there is not really anything broken.

Both zimlets have never been officially part of Zimbra.
It is up to the community to maintain them for ZCS 7.2 and above.
I might have a go at it but at the moment I am happy with my little script; so far didn't deceive me.

[xpla]

The script does not work for me at the part of

sudo - su -c ... smbpasswd ...

[rosch]

The script does not work for me [..]

As this thread is about zimlets I'd suggest you send me a private message and I'll help you debug.

EDIT: also, please update your profile with your Zimbra version. Have a look here how to do that.

[NxwJeff]

Hi everyone.

First of all, a message to Zimbra/Vmware. I've been for the most part a very happy customer of Zimbra for the last 3 years now, with 175 licenses. But since Vmware bought Zimbra out, I've seen the product take a huge price hike, and features that made me choose zimbra over other products being dropped. Yeah yeah I know, samba/posixaccount was never officially supported. Except for that very official wiki page of course. But whatever. Anyway, my licenses are expiring this summer, and I'm going to think very hard about moving to some sort of cloud hosting for my emails instead of my server. I'm not a big fan of not having my own servers for stuff, but honestly I'm not going to lose much when the product I use drops features when I upgrade.

Anyway, I think I have fixed the issue with the zimlets. I won't be able to test it on my live server until Tuesday, but it more or less works (at least it loads) on my empty virtual machine here. So basically unzip both zimlets, look for new ZmCsfeCommand() in all .js files. Right under it, there is this:
var params = new Object();
Well, simply add this right underneath:
params.noAuthToken = true;

It looks like the ZmCsfeCommand object now requires some sort of authtoken by default, and the old default behavior has to be specifically initialized.

There are 2 .js files per zimlet that have to be edited, each with multiple instances of the lines. It's a 2 minutes job at worse.

Zip everything back to the .zip file, then undeploy / deploy.

And then let me know if it worked for you guys, I'm not going back to work until tuesday since tomorrow is a day off for France, so I'm interested in knowing if it's fully functional or not!

I'm not planning on supporting the zimlets in any way, and I'll look twice now before upgrading Zimbra. But I'll try to get these zimlets back to working fully because I simply can't do my work anymore without them.

[rosch]

Anyway, I think I have fixed the issue with the zimlets.

Thanks a lot for your time and effort!

And then let me know if it worked for you guys, I'm not going back to work until tuesday since tomorrow is a day off for France, so I'm interested in knowing if it's fully functional or not!

I deployed both and tested a little bit.
The admin page loads, the zimlets are there, and adding a new user works too.
I have not tested anything Windows related though.

I will upload them to the zimlet gallery (samba posix).

Thanks again and enjoy your free Monday

[NxwJeff]

Alright, just installed this on my production server, and everything seems to be working as it should. Glad it was an easy fix, but this will most likely be my last Zimbra upgrade in a very long time (if ever).

[phoenix]

Glad it was an easy fix, but this will most likely be my last Zimbra upgrade in a very long time (if ever).

You'll be missing out on a lot of good features in the next major version.

[rosch]

You'll be missing out on a lot of good features in the next major version.

I agree but if it breaks things like the {samba,posix}-zimlets - although not a part of the official ZCS - then that's a no-go for many people.

[NxwJeff]

You'll be missing out on a lot of good features in the next major version.

Well I'd rather it not drop features, before any new stuff is added. But maybe that's just me being stupid enough to believe that a wiki page marked as "certified documentation " was enough to think that this specific feature was actually something I could safely use. Not so.
Zimbra counting on the community to keep these zimlets updated, when documentations, see Extending Admin UI - Zimbra :: Wiki or even Admin UI Framework Guide - Zimbra :: Wiki, are not even updated, is simply a joke. That wiki page uses code from the samba extension as an example, so any developer who would simply follow it would get code that wouldn't work and have no idea why.
You can't count on the community on one side, and then leave the community without outdated documentations on the other side, that's not the way this works.