I can confirm this. There are at least two issues here:

1. allday flag for exceptions is forced to be the same as main event. This can be fixed with this:

-- a/plugins/libkolab/lib/kolab_format_event.php
+++ b/plugins/libkolab/lib/kolab_format_event.php
@@ -291,7 +291,9 @@ class kolab_format_event extends kolab_format_xcal
         }

@vanmeeuwen, So we have a case with no delegation, but with a shared folder where user (with write rights) deletes an event. Considering my comment here https://git.kolab.org/T1357#27566 and the next one, what would you propose? Note that we first have to solve this independently from what wallace does, i.e. define what iTip messages are sent and when, should we use SENT-BY field, etc. Then how wallace would handle that is another story.

Any news for this issue?

Promoted to Bifrost#T18595.

This works for me. So, it may be some timing issue. Note that these notifications are not "instant", they are "pulled" in one minute intervals (timer starts when the page is loaded).

If you're in the File section of the web client, invitations about being invited to a collaborative session show up.

What File dialog? Could you be more precise? The notifications should be displayed in all Roundcube windows. That's how it worked.

This ticket can be closed. It was a combination of packages/releases that didn't played together.

Looks like this bug only happens in the old version. The most recent plugins package from Winterfell doesn't have this issue

I foun the broken commit rRPK1f88231db9fd0edca6e5b09c38e150216d760341. Fixed.

These "untranslated" messages come form wallace. We need to take care the solution works also for environments where invitation policy is not used at all or is used in various other modes.

Played around with Delegation and Shared Folder to test the behaviour of both functions.

Well, collabora devs implemented features that allowed to implement Kolab toolbar as described in [1] (an as on the screenshot). Still, we didn't really decide that it's a better approach. It was simpler to implement.

Could you update this task with the results of the discussions you have had with Collabora devs? Thanks!

Yes, for now lets just settle on CloudSuite.

Looks like my IMAP infrastructure doesn't support METADATA or ANNOTATEMORE... I think this is why we are using database_driver

Yes I am using database_driver. I don't remember why...

Do I understand correctly that you use database driver?

Current implementation gives prio to Collabora.

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

Done.

Tested and indeed there's a problem with this scenario. When handling an iTip we search for the event only in folders in personal and shared namespace. Here we have a folder in other user namespace. So, in [8] as well as in [6] the event cannot be found.

There were some related changes in git, some not packaged yet. I'll test git-master, to see if any of these issues can be still reproduced.

Groups with email address specified will not be expanded with their members.

Better fix submitted in D242. Waiting for approval

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.

The configuration options should already make their way into the $config member of the Yubikey class. They are read in kolab_2fa::get_driver(), passed through Kolab2FA\Driver\Base::factory() all the way to Kolab2FA\Driver\Base::init() where they are merged with $this->config. It's to be investigated why the following line in Base.php doesn't work as expected:

$this->config = array_merge($this->config, $config);

Thank you for the information. We will review it and dig a little deeper into this issue (shared folder vs. delegation).

Actually RFC5546 specifies a special case of acting on behalf of an organizer. So, I suppose we could assume that having write rights to calendar is such a case. Can't we?

Currently fixed, but the ticket will be open until we unify document_editor_api.

I didn't test yet, but then I think the described behaviour is not exactly as expected. I.e. if UserB is not the organizer I do not expect attendees (nor organizer) to be informed. We should not send cancellation emails with UserB's as a sender. Or maybe we should? That's problematic.

@machniak I am not using identities or delegation, it just a simple shared folder.

@Robert_Selk are you using delegation feature or simple ACL modification? Or in other words, does UserB have identities with UserA's addresses? I'm asking just to be sure I test the same scenario.

Tested it with Rouundcube Plugins 3.2.15-4.1.el6.kolab_14.

Just adding the problem for the record:

Oops, sorry...
Version: roundcubemail-plugins-kolab-3.3-1.10.el7.kolab_16.noarch

pykolab version is irrelevant. This is roundcubemail-plugins-kolab issue.

As nobody can reproduce this (also not ESG) we close this task

We are still unable to reproduce this.

Excellent (indeed it is..).

It is implemented also in KE14 for a long time. I didn't close this task, because converting to plain text is not the same as supporting HTML.

@machniak - Can this me backported to KE14 - please.

I found another issue in invitation acceptation related to the fact that there's more than one delegation involved here. It causes that if Carol accepts invitation in the name of Bob it is not saved to Bob's calendar, but Alice's copy of the event is updated.

I confirm this partially. "Remove from my calendar" button indeed removes the event from Carol's folder not from Bob's. So, step 8. is confirmed. However, I do not confirm missing CANCEL notification to Carol. The mail is being sent for me.

Adding the "kolab_auth_admin_rights" enables everybody to use/login/enter roundcube as an other user and disables any other restriction made before.
So the mentioned configuration will just open the functuionality to everyone and not restrict anything. If thsi is as you say a config issue, than please tell me where I can find the documentation of any of those helpdesk things to be configured with all the opetions and coincidents they have.

Closing this as a config issue.