Hum ... I guess I've pushed the reply button too quickly ;-)
In fact, we'll need to apply a patch to keep mapiproxy working properly
in regard to Outlook and association groups:
- mapiproxy initiates 2 distinct connections (proxying):
1 with the client
1 with the remote server
The existing hack also helped to transfer/use the assoc_group_id defined
by the client (when altering the context in client-mapiproxy conn) to
the mapiproxy - remote server connection.
In my opinion, the fix should be pretty easy (quick glance). I may be
missing the point - long time I didn't modify this code but ...
Rather than dealing with the previously exposed assoc_group_id, we
should dig with the assoc_group structure, locate the current id or
lookup handle location and return associated id, then pass/set it for
the remote connection.
On Wed, 2009-11-18 at 12:47 +0100, Julien Kerihuel wrote:
> Hi Brad,
>
> Changes looks OK.
>
> All changes meant to be applied obviously require some testing - as
> usual - and we need to check whether libmapiadmin and mapiproxy keep
> working.
>
> Regarding the dcesrv association group ID, the uint32_t assoc_group_id
> was introduced to prevent mapiproxy / samba4 from dropping Outlook
> connections when the client is altering the existing dcerpc context to
> have run several separated ExchangeRPC communication over the same
> initial connection.
>
> From the gitweb patch, it looks like this mechanism is now handled
> internally by Samba4 - which is a very good thing. The
> dcesrv_assoc_group_id was just a quick hack designed to work-around the
> issue we faced.
>
> However before applying the patch you propose, we need to do some
> mapiproxy/Outlook testing to ensure it doesn't break existing
> reliability - and if it does find the appropriate work-around.
>
> Cheers,
> Julien.
>
> On Wed, 2009-11-18 at 17:11 +1100, Brad Hards wrote:
> > On Wednesday 18 November 2009 16:37:28 Brad Hards wrote:
> > > BH: I clearly have no idea about this. It looks like context no longer has
> > > assoc_group_id, but I can't find the change or the fix.
> > Looks like this is the applicable change, but I'm still not sure of the fix:
> > http://gitweb.samba.org/?p=samba.git;a=commitdiff;h=69cb91a2eb2c3853663a61c2ed8f38e8fdde0964
> >
> > Brad
> > _______________________________________________
> > devel mailing list
> > [email protected]
> > http://mailman.openchange.org/listinfo/devel
> _______________________________________________
> devel mailing list
> [email protected]
> http://mailman.openchange.org/listinfo/devel
--
Julien Kerihuel
[email protected]
OpenChange Project Manager
GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
