Ah lol. This one is transparent here. But now I got it, thanks to your screenshot!

0_1512381708026_Unbenannt.png

Hello @rworobel ,

if its just about Kopano, then the update will likely be done within a few minutes.

@petsie said in Running on Devuan:

Is it possible, that the packages for Debian 9 are broken at the moment?

Yes, the 8.4.90.908 packages have an error in this regard. A fix is in https://jira.kopano.io/browse/KC-887 and those will be online in a few minutes.

@petsie said in Running on Devuan:

btw: Is there a Git repository including packaging scripts anywhere?

all that is public can be found in https://stash.kopano.io/projects/KC/repos/kopanocore/browse/installer

Voting for it too. Looking for the same. Home/non-profit license just with access to repository and no support.

@plzk-de said in S/MIME issue with outlook 2013 - where are pub certs stored?:

As my outlook has not a single addressbook entry but stil can encrypt outgoing mails, the public certs must coming from somewhere.

I don’t see where I was saying contradicting things. To my knowledge Outlook is storing public keys in the contacts, if you don’t have contacts then it indeed must me coming from somewhere else, but that is more of an Outlook topic, than a Kopano one.

I use MailScanner, plus clamav, plus spamassassin, plus relaydelay (grey listing), plus pyzor and a few others more.

And therefore handle all the incoming and outgoing email directly without an external smart host.

It does require a bit of work, but the advantage is that it is all in house and once you get it right it is in your full control.

@mrmanor said in Anyone using FreeIPA for LDAP authentication?:

May bee the Kopano people ( @fbartels ?) would like to include it somewhere on the Kopano site.

I’m afraid that if we include it in our official documentation people will expect us to maintain such an integration as well (even if we would put an all caps disclaimer about it). I have meanwhile checked with our support staff and so far we have had zero request for FreeIPA from our customers.

But lets focus on something more positive. For the Schema and potential GUI integration I would recommend to start a small git repository. The easiest is to host such a repository at Github, but I can also provide a repository on our community Bitbucket (stash.z-hub.io). To share the news about the existence of your project we could easily include it in https://stash.z-hub.io/projects/COM/repos/projects-and-resources/browse as well.

Hi @shcshc ,

great to hear that you found a solution. I’ve seen your updates along the way, but did not have any time yet to really thing about possible solutions.

Edit: in case you decide to make your project publicly available you could also add a link to it to https://stash.z-hub.io/projects/COM/repos/projects-and-resources/browse, so that other can more easily find it.

Hi @khung ,

I mean you could also wait for a wider dowstream adoption. The Debian guys are already quite busy (and we’ll be in the next Debian version) and openSuse has packages as well.

See https://wiki.debian.org/Groupware/Kopano and https://kopano.com/kopano-opensuse-yes-open/

Hi @smguenther ,
i could think if the ldap configuration. but maybe a remote session will be needed.

Hi @tms ,

you should be able to remove the program itself from the control panel. Removing schemas that have been once installed is a pain in any given ldap (without cleaning up all used attributes) therefore the schema will not be removed by the uninstaller.

@fbartels Great, thanks a lot!

Just to continue a bit, -in case you’re also running opendkim- these were the config changes that were updated and the selections I made:

spamassassin: local.cf -> N iptables before.rules -> N 50unattetended-upgrades -> Y logind.conf -> N sysctl.conf -> Y apache2.conf -> N default-ssl.conf -> N samba -> Y moduli -> Y sshd_config -> N jail.conf -> Y security2.conf -> Y /default/opendkim -> Y (!) opendkim.conf -> Y (!) apache.conf -> Y (!)

The (!) means changes were needed. Opendkim is now running chrooted so change to the sockets were made. The one thing that was a bit of a headache is that you need to re-compile the systemd init script by running “/lib/opendkim/opendkim.service.generate”, otherwise all change related to the socket settings in /etc/default/opendkim and /etc/opendkim.conf were ignored.

@fbartels
perfect :)

rg
Christian

@umgfoin
Thank you very much!
I´m running the script for the first time right now and I´ll post again when it´s done and I´ve checked the results.