Hi List, Long time, no mail. Vacations are over and battery cells are now reloaded enough to supply good level of energy to developers for several months. This mail is part of the
I've recently been adding the NSPI Referral protocol to exchange.idl + implementation within libmapi/IMSProvider.c. This protocol only has 2 RPC functions and is used to supply the caller the name of the NSPI server. [MS-OXABREF] says it should be used prior any NSPI connection which is the behavior I've introduced in libmapi. Any connection to the NSPI pipe will be prefixed by a connection to exchange_ds_rfr and a call to RfrGetNewDSA to get the NSPI server. I've also added a --getfqdn option to mapiprofile which will return the fully qualified domain name of the NSPI server corresponding to the mailbox server DN: $ mapiprofile --getfqdn -P exch2k3 /o=First Organization/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=EXCH2K3 is at exch2k3.openchange2003.local I also have a mapiproxy update in the pipe which handles the RFR protocol and will be committed today. It changes the NSPI server returned by RfrGetNewDSA with the local mapiproxy/samba4 realm. This should improve the overall process and avoid any remaining and direct Outlook-Exchange communications. Cheers, Julien. -- 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 devel@openchange.org http://mailman.openchange.org/listinfo/devel
