我们的一些应用程序可以很好地处理电子邮件集成的不同方式，在Windows 2000和2003环境中使用mailto: 模拟“发送至...”以及SMTP，现在转向使用Exchange 2010和Outlook 2010的新Windows 2008系统客户端。
我们有一个用例，其中应用程序创建新邮件，设置收件人和主题，添加一个或多个附件，然后在默认邮件客户端中打开它，以便用户在发送之前对其进行编辑。
您知道在新环境中有效的解决方案吗？ 我们应该使用第三方库吗？ 或者是否有一些OLE自动化代码可用，这些代码已知可以使用Outlook.Application工作？
Some of our applications which work fine with different ways of email integration, using mailto:, simulated "Send To...", and SMTP in Windows 2000 and 2003 environments, now move to a new Windows 2008 system with Exchange 2010 and Outlook 2010 clients.
We have one use case where the application creates a new mail, sets recipient(s) and subject, adds one or more attachments and then opens it in the default mail client so it can be edited by the user before sending.
Do you know a solution which works in the new environment? Should we use a third party library? Or is there some OLE automation code available which is known to work, using Outlook.Application?
最满意答案
我们使用Jedi JCL库中jclMapi单元的JclSimpleBringUpSendMailDialog。
我曾经有一个应用程序，我们在这里建立了一个用户选项，以指定他们是否想使用SMTP或MAPI，然后是各种邮件服务器设置，但是Jedi库调用使生活变得如此简单。 如果最终用户在MAPI客户端中设置了所有设置的麻烦，那么他们为什么要在我/我们的软件中再次设置它们。
mailto：// stuff的问题在于它通常不够配置，或者邮件客户端不能以相同/标准的方式处理参数 - 然后用户认为你的软件垃圾而不是相信他们有一个狡猾的邮件客户端。
所以我们只使用MAPI接口。 简单。
We use JclSimpleBringUpSendMailDialog from the jclMapi unit in the Jedi JCL library.
I once had an app where we built in a user option to specify whether they wanted to use SMTP or MAPI and then all sorts of mail server settings but the Jedi library call makes life so much easier. If end users have gone to the trouble of setting up all their settings in a MAPI client then why would they want to set them all up again in my/our software.
The trouble with the mailto:// stuff is that it's often not quite configurable enough or the mail client doesn't handle the parameters in the same/standard way - then users think your software's rubbish rather than believe they have a dodgy mail client.
So we just use the MAPI interface. Easy.
更多推荐
发布评论