none
How to implement a C# appplication that send email to Exchange MAPI which no Outlook is installed RRS feed

  • Question

  • As captioned. Any suggestion is much appreciated.
    • Moved by Leo Liu - MSFT Monday, February 20, 2012 3:44 AM Moved for better support. (From:Visual C# General)
    Friday, February 17, 2012 9:59 AM

Answers

  • Hi likamwah,
    I realize that your question was moved to this forum. However, this forum is for software developers who are using the Open Specification documentation to assist them in developing systems, services, and applications that are interoperable with Microsoft products. The Open Specifications can be found at: http://msdn.microsoft.com/en-us/library/cc203350(PROT.10).aspx. Since your post does not appear to be related to the Open Specification documentation set we would appreciate it if you could try to post your question in a more relevant forum.

    Exchange Development

    Thank you.


    Josh Curry (jcurry) | Escalation Engineer | Open Specifications Support Team

    Monday, February 20, 2012 4:09 PM
    Moderator

All replies

  • You should probably look into using the Exchange Web Services api, if that's what you're interested in doing.

    Friday, February 17, 2012 6:00 PM
  • http://msdn.microsoft.com/library/system.net.mail.aspx

    Paulo Morgado


    Thanks for the prompt response, however, our customer implemented the Exchange Server only in their internal network, and smtp and pop3 port are closed in the Exchange Server side, only MAPI connections are allowed in their network, so we have no choice but must implement the MAPI connection in our project to connect to the Exchange Server, then, SMTPclient seem not appropriate in this case. 
    • Edited by likamwah Monday, February 20, 2012 1:47 AM
    Monday, February 20, 2012 1:46 AM
  • It might help if you can provide more specifics on the requirements. For example, is the intended sender on a Windows platform? Which version(s)? Do you have specific requirements for C# / .NET? What do you need to send (in terms of email content)? Single sender with a service account? Can you install Outlook? Can you use an open source solution? Do you ever need to receive?

    These things might help to provide a response that is more useful to you.

    Brad

    Monday, February 20, 2012 6:26 AM
  • Hi likamwah,
    I realize that your question was moved to this forum. However, this forum is for software developers who are using the Open Specification documentation to assist them in developing systems, services, and applications that are interoperable with Microsoft products. The Open Specifications can be found at: http://msdn.microsoft.com/en-us/library/cc203350(PROT.10).aspx. Since your post does not appear to be related to the Open Specification documentation set we would appreciate it if you could try to post your question in a more relevant forum.

    Exchange Development

    Thank you.


    Josh Curry (jcurry) | Escalation Engineer | Open Specifications Support Team

    Monday, February 20, 2012 4:09 PM
    Moderator
  • It might help if you can provide more specifics on the requirements. For example, is the intended sender on a Windows platform? Which version(s)? Do you have specific requirements for C# / .NET? What do you need to send (in terms of email content)? Single sender with a service account? Can you install Outlook? Can you use an open source solution? Do you ever need to receive?

    These things might help to provide a response that is more useful to you.

    Brad

    Hi Brad,

    Thanks for your response, I briefly describe the spec/requirement of the program here: -

    i)   It is a .Net project developed by C#;

    ii)  The program is running under win32 environment (actually, it is under Windows XP x86 environment);

    iii)  The program sending email via a MS Exchange Server only serve for the internal LAN;

    iv)  The SMTP transport hub is disabled in the designed Exchange Server and only communicate with the email client via MAPI;

    v)   The content of the email will be plain text with attachment of Excel file or pdf file;

    vi)   It is a single sender with a single account that is already existed in the Exchange Server/Domain;

    vii)   The customer agreed to install Outlook in the client PC but not prefer;

    viii)   The program need not to receive email from the Exchange Server, only sending email is fine.

    ix)   Open source is fine if it can fulfil the above said criterion and can sending email via the Exchange Server by MAPI.

    Hope these points can help. Thanks in advanced.

    KW

    Tuesday, February 21, 2012 7:02 AM
  • I don't know of anything that already does this (except Outlook Interop). There is a .NET library in the Microsoft test suites, but it isn't set up for production, and you'd still need to do some coding.

    Brad

    Tuesday, February 21, 2012 9:06 AM