0

这个问题发生在我们的一位客户身上，我无法使用相同版本的 Outlook 进行复制。我和我的客户正在使用安装了 Outlook 2016 的 Office 365。当他通过 Outlook Redemption（用于 Outlook 集成的第三方程序）在我们的程序中发送电子邮件时，邮件卡在他的发件箱中。

如果他双击消息（因此它会在 Outlook 中弹出），他可以点击发送按钮，它将成功发送。如果他们使用旧版本的 Outlook (2010)，这不是问题。我当时将它们升级到了最新版本的 Outlook Redmeption（2016 年 5 月 7 日发布），尽管看起来它们几天前刚刚发布了新版本。我会尽快尝试，但更改日志没有提到邮件卡在发件箱中。

我还注意到，他发件箱中的电子邮件似乎带有“草稿”符号，而在我的发件箱中，它们上有“发送”符号。这似乎很重要，但我不确定我能做些什么。

此外，点击发送/接收所有文件夹也无济于事。

我的代码如下。感谢您提供任何帮助。

        public static bool SendMessage(Recipients recipients, string[] addressListReplyTo, string subject, string body, string[] attachments, bool requestReadReceipt, Log log, bool isHtmlBody = false)
    {
        RDOSession session = null;
        RDOMail mail;
        RDOFolder folder;
        bool result = true;

        session = GetSessionAndLogon(log);
        if (session == null)
            return false;

        folder = session.GetDefaultFolder(rdoDefaultFolders.olFolderOutbox);
        mail = folder.Items.Add();
        if (isHtmlBody)
            mail.HTMLBody = body;
        else
            mail.Body = body;
        mail.Subject = subject;
        mail.ReadReceiptRequested = requestReadReceipt;
        foreach (string attachment in attachments)
        {
            if (attachment != "")
                mail.Attachments.Add(attachment);
        }
        foreach (string address in addressListReplyTo)
        {
            if (address != "")
                mail.ReplyRecipients.Add(address);
        }
        foreach (string address in recipients.To)
        {
            if (address != "")
                mail.Recipients.Add(address).Type = 1;
        }
        foreach (string address in recipients.Cc)
        {
            if (address != "")
                mail.Recipients.Add(address).Type = 2;
        }
        foreach (string address in recipients.Bcc)
        {
            if (address != "")
                mail.Recipients.Add(address).Type = 3;
        }

        foreach (RDORecipient recipient in mail.Recipients)
        {
            if (!OutlookMailEngine64.existsName(recipient.Name, session, log == null ? null : log))
                result = false;
        }
        if (result)
        {
            try
            {
                mail.Send();
                result = true;
            }
            catch (System.Runtime.InteropServices.COMException ex)
            {
                string message = "Error while sending email: " + ex.Message;
                if (log != null)
                    log.Message(message);
                if (OutlookMailEngine64.DiagnosticMode)
                    MessageBox.Show(message);
                throw new EmailLibraryException(EmailLibraryException.ErrorType.InvalidRecipient, "One or more recipients are invalid (use OutlookMailEngine64.ValidateAddresses first)", ex);
            }
        }
        if (session.LoggedOn)
            session.Logoff();

        return result;
    }
4

2 回答 2

1

德米特里通过电子邮件与我合作。我的解决方案是将 RDO 换成 SafeMailItem 对象。这是我的方法的更新版本，因此您可以看到更改：

private static bool SendSafeMessage(Recipients recipients, string[] addressListReplyTo, string subject, string body, string[] attachments, bool requestReadReceipt, Log log, bool isHtmlBody = false)
    {
        //This method was added because sometimes messages were getting stuck in the Outlook Outbox and this seems to solve that
        bool result = true;

        Microsoft.Office.Interop.Outlook.Application application = new Microsoft.Office.Interop.Outlook.Application();
        Microsoft.Office.Interop.Outlook.NameSpace namespaceMAPI = application.GetNamespace("MAPI");
        namespaceMAPI.Logon();
        RDOSession session = null;
        session = GetSessionAndLogon(log); //TODO: I'm creating a 2nd session here which is wasteful

        SafeMailItem safeMail = Redemption.RedemptionLoader.new_SafeMailItem();
        Microsoft.Office.Interop.Outlook.MailItem outlookMailItem = (Microsoft.Office.Interop.Outlook.MailItem)application.CreateItem(Microsoft.Office.Interop.Outlook.OlItemType.olMailItem);
        safeMail.Item = outlookMailItem;

        if (isHtmlBody)
            outlookMailItem.HTMLBody = body;
        else
            safeMail.Body = body;
        outlookMailItem.Subject = subject;
        outlookMailItem.ReadReceiptRequested = requestReadReceipt;
        foreach (string attachment in attachments)
        {
            if (attachment != "")
                safeMail.Attachments.Add(attachment);
        }
        foreach (string address in addressListReplyTo)
        {
            if (address != "")
                safeMail.ReplyRecipients.Add(address);
        }
        foreach (string address in recipients.To)
        {
            if (address != "")
                safeMail.Recipients.Add(address).Type = 1;
        }
        foreach (string address in recipients.Cc)
        {
            if (address != "")
                safeMail.Recipients.Add(address).Type = 2;
        }
        foreach (string address in recipients.Bcc)
        {
            if (address != "")
                safeMail.Recipients.Add(address).Type = 3;
        }

        foreach (Microsoft.Office.Interop.Outlook.Recipient recipient in outlookMailItem.Recipients)
        {
            if (!OutlookMailEngine64.existsName(recipient.Name, session, log == null ? null : log))
                result = false;
        }
        if (result)
        {
            try
            {
                safeMail.Send();
                result = true;
            }
            catch (System.Runtime.InteropServices.COMException ex)
            {
                string message = "Error while sending email: " + ex.Message;
                if (log != null)
                    log.Message(message);
                if (OutlookMailEngine64.DiagnosticMode)
                    MessageBox.Show(message);
                throw new EmailLibraryException(EmailLibraryException.ErrorType.InvalidRecipient, "One or more recipients are invalid (use OutlookMailEngine64.ValidateAddresses first)", ex);
            }
        }

        if (session.LoggedOn)
            session.Logoff();

        namespaceMAPI.Logoff();

        return result;
    }
于 2017-02-07T19:11:09.017 回答
1

请记住，消息提交是异步的，除非您使用在线 Exchange 存储（其中存储和传输提供程序紧密耦合），否则它不会自动触发。

Namespace.SendAndReceive您可以通过调用Outlook 对象模型来强制发送/接收 。

于 2017-01-17T00:55:12.607 回答