[Kolab-devel] Wallace and Invitation Policies

[Thomas Brüderli]

Sergio Talens-Oliag wrote:
> Hello,

Hi Sergio
> 
> I'm working on having a functioning Kolab 3.3 on a Debian server using
> dovecot 2.2.15 (with the upstream metadata support); I'm not using all the
> kolab tools, but what I need is almost working.
> 
> To be able to use the invitation policies module of wallace I've added a
> dovecot driver to pykolab (it's a quick hack, to distribute it the pykolab
> imap drivers will need to be reviewed, as there are some assumptions on
> different places that should be on the cyrus driver but are on the general
> code, i. e. dovecot does not provide the same namespaces that cyrus does, but
> there are some checks that expect three namespaces).
> 
> Anyway, my modified wallace is more or less working, but I have two problems
> right now:
> 
> 1. If I set the invitation policy to 'ACT_SAVE_TO_CALENDAR' (on the LDAP user
> config or as the default policy) the iTip xml file is saved as a message on
> the default calendar mailbox, but it does not appear on the roundcube
> interface (if I use 'ACT_TENTATIVE' it is shown); is this a a bug on the
> roundcube module? if so, has it been detected already or should I send a bug?

The invitations appear in a dedicated calendar "Pending invitations" but
that needs to be enabled in config (/etc/roundcubemail/calendar.inc.php):

  // show virtual invitation calendars (Kolab driver only)
  $config['kolab_invitation_calendars'] = true;

It's been made a configuration option because these virtual calendars
will remain empty if no according invitation policy is set and in such a
case just add to the confusion of users.

FWIW: the list of valid values for the invitation policy configuration
are listed here:
http://docs.kolab.org/architecture-and-design/mta.html#wallace

> 2. I see that no notification is sent if wallace processes an iTip
> invitation... I would like to be able to receive the iTip message
> when wallace processes it (for ACT_SAVE_TO_CALENDAR it would be the original
> message and for ACT_ACCEPT* or ACT_TENTATIVE would be the updated iTip)...
> ¿should I modify wallace to do it or is there some other way of doing it?

The iTip message would be a copy of an event that was already added to
your calendar. When further processing it from the calendar view (e.g.
accept the invitation), we have no means to relate the updated event to
the iTip invitation message in your inbox.

I understand the use case of getting a notification in your inbox about
new invitations but that's actually what iTip was meant for in first
place. Using EVENT_SAVE_TO_FOLDER basically disables the regular iTip
process.

~Thomas