Hi,

As far as I know, NSPI server implementation is not a priority currently for 
Open Change project.
Nevertheless, we currently need that functionality and as far I am on this, I 
decided to start a discussion about current state of this particular module and 
what should be done in near future.


So, first of all, here are some observations I have on current state:

0. Test scenario is:
        - M1: Open Change + Samba 4 running under Ubuntu 9.04 (either as 
Exchange server, as proxy or as Primary domain controller with Exchange 
extensions)
        - M2: PPSD mail server (EMSMDB interface implemented) running under 
CentOS 5.3 - this is our implementation of Exchange server under Linux but it 
need Active Directory
        - M3: Outlook client running under Win XP Pro

1. NSPI implementation works fine in proxy mode.

2. NSPI server mode works partially when provisioned with Open Change provision 
script. At least in my case I had difficulties to create mail profile from Win 
XP machine - mapiproxy just looped forever in a bunch of calls.

3. NSPI server mode doesn't work, when an Exchange like provisioning is 
performed.
        - To be more clear, in this scenario M1 machine is acting as Primary 
domain controller serving Active Directory with Exchange provisioning applied, 
and M2 machine is acting as a data store
        - after all, we manage to run in this configuration but after few 
patches, which I wish to discuss futher in the list.

Based on the above, I want to discuss with all involved about how do you intend 
to support NSPI interface implementation?
Current implementation works exclusively against Open Change provisioning 
(which should mimic the Exchange provisioning but is not) and also only in 
scenarios when Active Directory and mail store are on the same physical machine?

I would wish a more generic implementation so that more people to be using it 
in different scenarios :)
And after all, according to MS docs, NSPI interface is supposed to be 
implemented by Domain Controller - it is not bound physically with Exchange 
server.
Any thoughts?


Will continue with sending all patches we had to make in order for mapiproxy to 
be able to support profile creation and mail reading from native Outlook client.

BR,

Kamen Mazdrashki
Software Engineer
Software Development

[email protected]
CISCO SYSTEMS BULGARIA EOOD
18 Macedonia Blvd. Sofia 1606
Bulgaria
Cisco home page
 

Think before you print.



_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel

Reply via email to