Lets collaborate on Evolution MAPI
Lets collaborate on Evolution MAPI
How best to collaborate than use Public folders. Last couple of weeks Milan has been fixing quite a few things for Public folder mailboxes in Evolution. It works like a charm now with Evolution.
Fetching the public folder list using openchangeclient,
Subscribed Public mailbox folder in Evolution,
With the mailboxes working great, we decided to focus on the Public folder for address book, calendar, memos and tasks.
We assigned this task to Punit Jain, his first feature in Evolution. After 3 – 4 weeks of work, this is what he had to show us all 
The list of public folders being fetched, with the highlighted one being the Task type public folder,
The subscribed Public Task folder being shown under the Tasks component,
So what should all of you do next?
1) Try the new version of evolution-mapi and report feedback so that we get it in shape for 3.0
2) Buy the openchange developers some beer the next time you bump into them. If you look at the kind of changes they have made over the last couple of releases, you would be left completely spellbound. Most of the features that one needs with his Exchange server have already been implemented in openchange. So if you like their work, drop them a word of thanks.
So what next for Evolution MAPI?
Sort the feature list and have the good ones implemented a month before the feature freeze to give us enough time to fix the regressions. Seems like openchange has all these features implemented ages back, now its time Evolution extends all this good work for 3.0 and spread the love to its users
Why is this feature special to us?
Because I and Milan mentored Punit for this feature, and yes it is a good feeling once the mentoring pays off
What’s the status of RPC over HTTP support for evolution v3. Its a very often requested feature and I know of a lot of deployments of exchange now that only use it that way which locks out quite a few possible evolution users of the evo-mapi feature.
Peter
June 24, 2010 at 9:26 pm
Hi,
I wanted to use evolution-mapi to connect to my employer’s Exchange server but it kept failing. I was told it is because it uses NTLM v1 while this is not supported anymore by the server. Is there a version of evolution-mapi using a newer version of NTLM?
Thanks in advance!
Karel
June 25, 2010 at 8:18 am
What version of exchange are you using? It should work fine with all exchange servers and it certainly supports later versions of NTLM. I think you must have another issue.
Peter
June 25, 2010 at 11:39 am
Yes that’s right, as Peter pointed out NTLMSSP Authentication is the default one we use.
Openchange also supports Kerberos authentication. We would add support for it soon in Evolution. In openchange, if Kerberos authentication fails, it still falls back to NTLM
abharath
June 25, 2010 at 2:40 pm
Can you point me to your active bug tracking/developer site? I have a repeatable crash when security is set to ads in smb.conf and I’d like to try against the newest code. Every site I could find online has nothing new posted since 2008 or 2009.
Ian
September 22, 2010 at 4:59 pm