[Kolab-devel] Wallace and Invitation Policies

Sergio Talens-Oliag sto at iti.es
Mon Jan 12 16:33:45 CET 2015


Hello,

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?

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?

Thanks in advance,

  Sergio.

-- 
Sergio Talens-Oliag <sto at iti.es>               <http://www.iti.es/>
Key fingerprint = FF77 A16B 9D09 FC7B 6656 CFAD 261D E19A 578A 36F2


More information about the devel mailing list