Windows Service opening a mail box

0
votes

WE had exchange server 2007 mail box.There is windows service which uses MAPI protocol to pull the mails from mailbox.

The mailbox is migrated to exchange server 2013.The windows service started reporting issues like Mapi logon failed.

On checking with messaging team ,they have told that MAPI is no longer supported in exchange server 2013.

It would great if you can advise,if you have faced the problem earlier .

2
.netmapi
This site is for programming questions. We are not here for server tech support. – Marc B
Welcome to StackOverflow! From the tone of your question, it sounds like you may be a sysadmin venturing into the programming world. If so, you may want to pass the issue onto a developer. If, on the other, you're a capable programmer, then cheers, and good luck going forward with a solution! – Lynn Crumbling

2 Answers

0
votes

You're probably going to have to switch to using either IMAP or EWS to talk to your exchange box.

Also, I found this snippet:

All MAPI traffic is RPC-based. Historically, Outlook clients have had two transport methods for RPC traffic available to them: RPC over TCP, and RPC over HTTP (aka Outlook Anywhere). In Exchange 2013, we removed the RPC over TCP option, leaving RPC over HTTP as the only connectivity method. This does not mean RPC is no longer supported. In fact, it is still used (e.g., we still make MAPI/RPC calls), we just encapsulate them in HTTP packets.

So, it stands to reason that your old MAPI-based code could still work if made to use HTTP. Not sure what that would entail, but if it saves you the trouble of converting to a different protocol (read: server config instead of code changes), it could be worth the research time.

One last note: take a look at this MSDN page that discusses MAPI over HTTP.