守卫已经疯了（或者我如何让多个 MAPI 客户端一起运行？）
我有一个独立的程序，我试图将其连接到 MAPI 中，以使用可用的默认系统（大部分是 Outlook）自动发送电子邮件。在大多数情况下，它运行得很好，一切都很好。但是，过了一段时间，Outlook 将开始对我的程序访问 MAPI 系统的行为感到不满，并开始拒绝显示任何内容，直到所有 MAPI 用户（我的程序和 Outlook）关闭并重新打开。我现阶段的最佳猜测是，我在登录 MAPI 系统时没有使用正确的标志集，但我不明白为什么。我当前的设置是 MAPI_ALLOW_OTHERS、MAPI_EXTENDED 和 MAPI_USE_DEFAULT。谁能建议一种不同的组合，让 Outlook 继续忽略我，并安抚警卫？谢谢。
I have a standalone program that I am trying to hook into MAPI to send emails automatically using the default system (Outlook for the most part) available. For the most part, it works quite well, and everything sends fine. However, after a while, Outlook will start to flip out about my program's accessing the MAPI system, and will start to refuse to show anything until all MAPI users (my program and Outlook) are closed and re-opened. My best guess at this stage is that I'm not using a proper set of flags when logging in to the MAPI system, though I can't see why. My current set is MAPI_ALLOW_OTHERS, MAPI_EXTENDED, and MAPI_USE_DEFAULT. Can anyone suggest a different combination that lets Outlook continue to ignore me, and keep the guard placated? Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不久前经历过类似的情况，并且能够通过从单个入口集中所有扩展 MAPI 调用来解决该问题，并添加一个队列以确保在任何时间点仅发生应用程序中的一个 MAPI 事件。
I experienced something similar a while back and was able to work around it by centralizing all of my extended MAPI calls from a single point of entry, and added a queue to insure that only one MAPI event from my application was occurring at any point in time.