I've now removed the package from my system - let's see what happens.
We most likely can't "Conflict" roundcube with this package - other Debian packages might still need it.
Thanks for the vendoring hint. We might want to hint admins during upgrades that it might be possible/useful to remove old packages.

The debian package seems to work when editing sieve filters.

Thanks - I've added it to my "must fix list" when upgrading...

Can you explain "Smarty issue fixed by hand" in detail? What's the issue and how did you fix it?

I'm still on Debian 10 - a new test-install on Debian 12 throws errors when logging in to kolab-webadmin. Didn't investigate further...

Hello gpunk,

I'm running Nextcloud 17 and connected Kolab 16 (both on Debian 10) via webdav.
In my Folder tree I have:

I've updated my kolab installation from Debian 9 to 10. All in all nothing major. Highlights:

I've seen in OBS that we now build packages for Debian 10.
What's your opinion: Is it probably ready to upgrade my instance?
The only package failing to build is chwala - where I could possiby use the old package...

According to https://obs.kolabsys.com/project/show/Kolab:Winterfell
RHEL_8 and Debian_10.0 have been added to Winterfell.
So my most pressing wishes have been granted :-)

On my system wallace has been updated to 0.8.13-0~kolab2 and restarts seem to work now. I'l have an eye on it. If other people can confirm the fix we can close the ticket.

My python is Python 2.7.13 from the debian packages:

I've tried reading the wallace source but didn't see an easy fix. For now I use a cron job
with the following script to fix wallace up:

Current Winterfell seems to have it fixed:

Winterfell seems to use newest boot now:

That's far easier than I thought. We already use save_file_content for special condition.
Let's just do that instead of sending the "Location:"-header too. This patch replaces
to one above. Would that work?

The wiki seem not to be available for me, but the following infos might help with autoconfig:
https://tools.ietf.org/html/rfc6186
https://developer.mozilla.org/de/docs/Mozilla/Thunderbird/Autokonfiguration
https://blog.plitc.eu/2013/dns-srv-imap-autodiscover-record-zur-outlook-einrichtung/

Yes, that'll load the file into memory - no problem for my users, because our files are small.

Yes, I agree it's not a software bug, but I propose to add some documentation about delegation to
https://docs.kolab.org/administrator-guide/using-the-kolab-web-administration-panel.html#users-administration
[which is empty right now]. Something like:

My users still like the classic skin, but use only mail.
Anyway, we must not break people's setup, so we either need to modify the user settings
when upgrading or alert the admin and help him fix his system.
So we need to do more than just removing the skin.

Thanks - it works for me.

I started to package endroid-qrcode for Debian and saw that there is a new upstream release 1.6.5 available. The changelog has:

You recommended to remove the $config definition from plugins/kolab_2fa/lib/Kolab2FA/Driver/Yubikey,php, but that hunk is missing,
Otherwise looks good to me.

That looks basically like a subset of privacyidea or lintop (and possibly) others.
Do we really want to travel that path?

A test with TOTP was successful.

Hm, there seems to be some confusion between method (driver to use) and id (yubikey:<hexcode>). the plugin tried to load config['kolab_2fa_yubikey:<hexcode>'] which obvously fails. The following patch (against Winterfell) seems to fix it for me - but I didn't test HOTP or TOTP token. And already added yubikeys had to be removed and readded.

From what I see Debian/testing (stretch) contains a newer phantomjs:

CentOS 7 runs a targeted SE Linux policy, which seems to work with minimal changes.
Please, let's fix what might be missing (until now it was easy...) instead of disabling
SELinux completely.

Please see one of my mails - I did everything the guides asked for - but still failed.
So my guess is that the guide needs some updates too.

Getting OTP would be wonderful. I do own a Yubikey Edge, which is configured for OATH-HOTP and Challenge-Response HMAC-SHA1 (and U2F). I do use Challenge-Response for offline things like keepass, LUKS or Laptop-Login.