Apparently I need to be added to the PyKolab Developers group to be able to land changes.

Thanks for the review! I tried to arc land the changes but seem to lack permission to do so:

Exception: You do not have permission to push to this repository.
fatal: Could not read from remote repository.

I have abandoned D3190 and submitted the individual commits in D3223, D3226, D3229, D3232, D3235, D3241 and D3244.

Superseded by D3223, D3226, D3229, D3232, D3235, D3241 and D3244.

Fixed - better late than never.

Submitted D3190, which has ended up being sort of... bulky. There are several commits in this differential; does Phabricator offer no option to review these commits individually like Git{Hu,La}b do, without the author having to create a separate differential per commit?

Note that all changes I have made so far should™ be backward-compatible with Python >= 2.6, so they wouldn't necessitate any changes to our existing packaging.

Hmm, does Arcanist offer a way to do fast-forward merges?

Superseded by D2548. Turns out the first commit is no longer needed (and I messed up the diff during rebase).

Superseded by D2542.

The documentation pipeline should really get fixed at some point.

Umm, yeah, the docs are somewhat outdated because the build pipeline appears to be broken (T6055)...

Do Guam's log files, which can commonly be found under /var/log/guam/, provide any helpful clues as to what is going wrong here?

I'm closing this in favour of T6073/T6061, both of which appear to deal with the same issue.

Superseded by commit d2aa0743e462.

Looks good to me.

You need to supply Guam with a valid X.509 certificate (issued by Let's Encrypt, for example) and adapt the tls_config section of /etc/guam/sys.config accordingly.

Guam should be listening on port 993, so please check if the Guam service is up and running.

Worked fine, I could't reproduce the issue. Closing this.

Closing this task then.

Looks good to me.

If you feel courageous enough, I would say it's ready for field testing. Should you encounter any remaining rough edges, please report them so they can be ironed out.

Ouch, good catch!

I believe this was already fixed back in June with https://obs.kolabsys.com/package/rdiff/Kolab:Winterfell/kolab?linkrev=base&rev=37.

Done. Thanks for reporting this!

I'm working on providing Debian 10 packages for Kolab 16.

Oh dear. Thanks for pinpointing the problem!
I've pushed out an urgent hotfix; updated packages should be available in a few minutes.

If only things were that easy. :-/

Good spot, that may very well be the reason. 👍

I can confirm this issue. See here for a workaround: https://git.kolab.org/T4049#60227

Unfortunately I don't have the permissions to delete or edit that page, even with my admin account. Assigning to @vanmeeuwen.

Sorry, I cannot easily downgrade to 1.3.8 to try stuff out on my system.
May I ask which distro you are on and which version of Kolab you're using?

Weird - I cannot seem to reproduce this issue on my Debian Stretch box with up-to-date Kolab 16 packages (roundcubemail 1.4-0~kolab53, roundcubemail-plugins-kolab 3.4-0~kolab57) and the Elastic skin.

A fix has been pushed by @pokorra: https://obs.kolabsys.com/request/show/2366

Duplicate caused by Phabricator dying.

Duplicate caused by Phabricator dying.

Duplicate caused by Phabricator dying.

This change has already found its way into the repository.

\o/

One last item to fix: the link behind the download button.

Confirmed.

The channel mode has been set to +C +r +s, which should put an end to the spamming.