Resources in multi-domain setup. Does it work in Kolab 3.4? (Bug in doc found !)

Cornelius Hald hald at icandy.de
Mon Jun 22 15:50:41 CEST 2015


Hi Franz,

thanks a lot for your input. I've tried various settings for
kolab_invitation_policy but still no luck.

The two versions that I would expect to work are as follows.

# Simply do it for all domains
kolab_invitation_policy = ACT_ACCEPT_IF_NO_CONFLICT, 
                          ALL_UPDATE_AND_NOTIFY

# Explicity list all domains
kolab_invitation_policy = ACT_ACCEPT_IF_NO_CONFLICT:mydom1.de,
                          ACT_ACCEPT_IF_NO_CONFLICT:mydom2.de,
                          ACT_ACCEPT_IF_NO_CONFLICT:mydom3.de,
                          ALL_UPDATE_AND_NOTIFY

Instead of ACT_ACCEPT_IF_NO_CONFLICT I've also tried
EVENT_ACCEPT_IF_NO_CONFLICT but that doesn't seem to make a difference.
I think the part which is not working is ALL_UPDATE_AND_NOTIFY.

After changing the config I've always restarted kolabd and wallace. Is
there something else I need to do?

I'll have a closer look at the logs now and try to figure out what's
wrong. Still, if you have additional ideas they would be very welcome :)

Cheers,
Conny

On Thu, 2015-06-18 at 17:03 +0200, Franz Skale wrote:
> 
> Hi Cornelius,
> i had the same problem, but , after reading the source, this line should
> work. (works for me, inviation automatically updated).
> 
> kolab.conf:
> kolab_invitation_policy = ACT_ACCEPT_IF_NO_CONFLICT:domain1.com,
> ACT_ACCEPT_IF_NO_CONFLICT:domain2.com,
> ACT_ACCEPT_IF_NO_CONFLICT:domain3.com, ALL_UPDATE_AND_NOTIFY
> 
> Try.
> 
> Rgds.
> 
> Franz
> 
> 
> 
> Am 17.06.15 um 22:16 schrieb Cornelius Hald:
> > Hi Franz,
> >
> > sorry for the late reply. I've just applied your patch and it seems to
> > work great! Thanks a lot for that!
> >
> > Now that resource booking works I have a more general question - maybe
> > you know something about that too.
> >
> > If I book a resource I'm getting an automated mail from the resource
> > telling me that the "Participant has accepted". Unfortunately the
> > resources calendar does not get updated automatically but shows
> > "NEED-ACTION".
> >
> > If I open that mail in Roundcube there is a button "Update the
> > perticipant's status". After pressing that button the resources calendar
> > is updated correctly.
> >
> > Do you know a way to automatically update that calendar? It seems to be
> > strange that I have to manually update the calendar if the resource has
> > accepted the invitation already.
> >
> > Thanks!
> > Conny
> >
> >
> >
> > On Di, 2015-06-02 at 21:38 +0200, Franz Skale wrote:
> >>
> >> Hi Cornelius,
> >> watching the bug, it found my tempfix for that problem.
> >> I use the dev repo (development) right now.
> >> My temp fix can be found: (last comment).
> >> https://issues.kolab.org/show_bug.cgi?id=4331
> >>
> >> File /usr/share/pyshared/pykolab/auth/ldap/__init__.py. (function
> >> find_resource)
> >> After patching do:
> >> cd /usr/share/pyshared/pykolab/auth/ldap/
> >> python -m compileall .
> >> Restart wallace and kolabd.
> >>
> >> Try.
> >>
> >> Rgds.
> >>
> >> Franz
> >>
> >> Am 10.05.15 um 11:25 schrieb Franz Skale:
> >>
> >>>
> >>> Hello Daniel,
> >>> thanks for your suggestion.
> >>> It works, and the mail will be passed to wallace.
> >>> This leeds to another problem, regarding the inviation_policy module
> >>> seems not to be multidomain aware.
> >>> But for this particular problem, i will post a new message.
> >>>
> >>> Many Thanks
> >>>
> >>>
> >>> Franz
> >>>  
> >>> Am 09.05.15 um 20:23 schrieb Daniel Hoffend:
> >>>> Hello Felix
> >>>>
> >>>> thanks for your research
> >>>>
> >>>>>  NOTE: DO NOT put quotes around the result format!
> >>>>>
> >>>>>  Kolab upgrade guide:
> >>>>>  https://docs.kolab.org/upgrade-guide/kolab-3.4.html [4]
> >>>>>
> >>>>> Change the result_format to be enclosed by quotes otherwise you
> >>>>> can’t deliver mail messages to shared mailboxes that contains spaces
> >>>>> in the mailbox name. result_format = "shared+%s"
> >>>> It was me who was suggesting putting quotes around the result.
> >>>> The quotes should ensure that the mail will find its correct folder
> >>>> when delivered using lmtp.
> >>>>
> >>>> It's not ment for any other ldap searches to find the next result.
> >>>>
> >>>> I've the strong feeling that your postfix ldap search is just wrong.
> >>>> When looking up for resources the ldap search for shared folders should
> >>>> not return the storage location. In fact the wallace should intercept
> >>>> the resource booking request and process the mail.
> >>>>
> >>>> Fixing your sharedfolder ldap_query should fix your problem:
> >>>>
> >>>> ------------
> >>>> query_filter =
> >>>> (&(|(mail=%s)(alias=%s))(objectclass=kolabsharedfolder)(kolabFolderType=mail))
> >>>> result_attribute = kolabtargetfolder
> >>>> result_format = "shared+%s"
> >>>> ------------
> >>>>
> >>>> Filtering for kolabFolderType=mail will not create a match when
> >>>> you lookup for a resource, cause the resource has
> >>>> kolabFolderType=event.
> >>>>
> >>>>
> > _______________________________________________
> > users mailing list
> > users at lists.kolab.org
> > https://lists.kolab.org/mailman/listinfo/users
> 
> 



More information about the users mailing list