working together in global folders with mail address
-
Hi @ansib,
the easiest way (especially since this also makes sure that these emails are replied with the correct outgoing address) is to work with shared/inactive mailboxes and give users (or groups) access to these inboxes.
Another alternative is to have these mails delivered into the public folder (there are multiple ways to do so, once is a momentarily defunct script for the dagent, which will be resolved for 8.7.1). The public folder is a single additional inbox that all users have automatically opened in their webapp. here you then still need/can set acl to define who can see and modify these folders.
-
Hi @fbartels,
thank you for the fast reply.Do you mean with shared/inactive mailboxes a normal user profile, but disabled?
I think this solution is the best one.Unfortunately i can not find any information in the documentation how to disable a profile, do you know where i can find this?
-
@ansib said in working together in global folders with mail address:
Do you mean with shared/inactive mailboxes a normal user profile, but disabled?
yes, you could describe it like this.
Sure enough this seems basic enough that no one ever bothered to explicitly document this. If you are using the ldap backend you just need to add ´kopanoSharedStoreOnly: 1
´ to the account. For the db plugin its flag you can pass when creating/modifying the user. -
-
Hi @fbartels
i have one more questions regarding the shared store. I was able to set this attribute via univentionFreeAttributes to automatically disable a user mailbox in my ldap tree. But in the LDAP Attributes there is no attribute to configure the permissions via LDAP. Is it possbible or does i have to reenable the mailbox every time to login and set permissions for a new user/group? -
@ansib When you’re on univention you will want to use the udm to make your store a shared one:
To set permissions on such a store you should make a user admin (same dropdown). he can then open the store and set permissions accordingly.
-
@fbartels sry i forget to provide an important information. I have a standalone installation of kopano on a virtual machine and i am not using the univention installation by kopano. i am only configuring the ldap via univention. that is the reason why i have to use the univentionFreeAttributes to map the kopano ldap attributes. i will try the userAdmin Attribute.
-
I have to ask (since I am the maintainer of the Univention app):
@ansib said in working together in global folders with mail address:
I have a standalone installation of kopano on a virtual machine and i am not using the univention installation by kopano.
Why?
(I am currently in talk with a partner who wants to go a similar route for a bigger installation, since he wants to use components like Nginx that are not easily achievable on ucs, but for a regular installation I do not see that much of a benefit in doing so)
-
We want to split our systems, so Univention is used only as Active Directory and not as both (Mail Server and AD). Another reason is, that we need the knowhow to administer a standalone Kopano Installation (for example, if a customer has no univention server). Third reason is, that we get faster updates via the packages and last but not least, we can use Kopano Meet, which is actually not avalaible for univention. Unhappily it is a lot of adminstration to get kopano work.
-
@ansib that is reasoning that I can at least partly follow. The update should not be a problem, since our repos can be used as well (see https://kopano.com/blog/staying-up-to-date-with-kopano-releases-on-ucs/).
With already mentioned partner I am currently discussing the possibility of decoupling the integration package from locally installed packages (which will be needed anyways when at some time in the future kopano should run dockerised on ucs).
Let me know if you would be interested in collaborating on this functionality as well.
-
@fbartels said in working together in global folders with mail address:
The update should not be a problem, since our repos can be used as well (see https://kopano.com/blog/staying-up-to-date-with-kopano-releases-on-ucs/)
I wasn’t aware, that this is possible. I am interested in collaboration, because in future we also want to replace our Open-Xchange installation on Univention (thats for our customers) and the virtual machine with kopano is for ourself.
-
@ansib said in working together in global folders with mail address:
I wasn’t aware, that this is possible
I guess if you don’t install the app this is something that can be easily overlooked. Not only or software is open source, but actually all the apps we provide for Univention (and the integration package for Kopano itself) are open source as well.
You can find the source code at https://stash.z-hub.io/projects/K4U
Internally we are using OBS to build packages, I have mirrored the build job to https://build.opensuse.org/package/show/home:zfbartels/kopano4ucs in case you want to inspect this as well. -
@fbartels said in working together in global folders with mail address:
I guess if you don’t install the app this is something that can be easily overlooked.
Yeah that is right. Actually we can not install it, because we have OpenXchange running in Univention and we are migrating our mail server to kopano.
By the way: Shared Mailboxes and setting via admin is now working fine :)
another questions: is it possible to commit bugs from here to the developer, because we have some trouble with the files plugin (see my post or should i post it in the support via the partner portal)?
-
@ansib this is a community forum, so if you depend on answers its always best to open up a support case.
