locked
[Mapi] server side x64 mapi RRS feed

  • Question

  • Hi,

    actually we had a x86 server solution that makes extensive use of mapi for connecting with an Exchange Server. We use the mapi included in the ExchangeCdo-Mapi setup.

    Now, we plan to port our server to x64 but there isn't a x64 ExchangeCdo-Mapi.

    Which x64 mapi should use now? Is it a goog idea to install Outlook x64 on a server operating system only to get a x64 mapi?

    Regards

    Monday, April 23, 2012 9:03 AM

Answers

  • Hi Scott,

    thank you for your answers.

    I think, we have two options: Exchange Web Services or Outlook x64 Mapi.

    Regards

    Andreas Rossi

    • Marked as answer by AnRo Wednesday, April 25, 2012 7:44 AM
    Wednesday, April 25, 2012 7:44 AM

All replies

  • Hi,

    I've done MAPI development since 1998 and I'm really happy there's an alternative now (in Exchange Web Services).

    What do you use MAPI for.... and you sure you want to stay with an ancient API like that ???

    Regards,


    Scott Quinn | C# developer & messaging specialist (for hire). Contact me at http://au.linkedin.com/in/scottquinn

    Monday, April 23, 2012 11:35 AM
  • That's right.

    But we have a huge amount of code and it might be easier to port it to x64 as to port it to Exchange Web Services. It's a question of time and efford.

    Regards,

    Andreas Rossi

    Monday, April 23, 2012 12:12 PM
  • Hmmm, maybe....

    What does the code do ? Send Email ? Read It ? Extract attachments ? Using multiple accounts ? Handling events ? Custom properties ?

    Regards,


    Scott Quinn | C# developer & messaging specialist (for hire). Contact me at http://au.linkedin.com/in/scottquinn

    Monday, April 23, 2012 2:24 PM
  • Reading and writing contacts in public and personal contact folders, listening on incoming emails reading their smtp-headers and modifing their message class and other mapi properties; for all mailboxes where we have permissions to do that.

    Regards,

    Andreas Rossi

    Monday, April 23, 2012 2:44 PM
  • Hi Andreas,

    You could do most of that now with a routing agent: intercepting email, read / modify / add / remove headers, modify MAPI properties and (while I'm not 100% sure because I've never needed to do it in an agent, probably) change message class - and permissions are not an issue as agents have total control. This would all run ON your Exchange hub itself and there's no need to install Outlook etc.

    The rest (changing contacts) should be straightforward in EWS.

    Anyway, if you want to use MAPI still that's fine - I'm just pointing out some of the options you have nowadays.

    Cheers,


    Scott Quinn | C# developer & messaging specialist (for hire). Contact me at http://au.linkedin.com/in/scottquinn

    Monday, April 23, 2012 3:19 PM
  • Hi Scott,

    thank you for your answers.

    I think, we have two options: Exchange Web Services or Outlook x64 Mapi.

    Regards

    Andreas Rossi

    • Marked as answer by AnRo Wednesday, April 25, 2012 7:44 AM
    Wednesday, April 25, 2012 7:44 AM