当前位置: 首页>>代码示例>>C#>>正文


C# MailMessage.AddRecipient方法代码示例

本文整理汇总了C#中MailMessage.AddRecipient方法的典型用法代码示例。如果您正苦于以下问题:C# MailMessage.AddRecipient方法的具体用法?C# MailMessage.AddRecipient怎么用?C# MailMessage.AddRecipient使用的例子?那么恭喜您, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在MailMessage的用法示例。


在下文中一共展示了MailMessage.AddRecipient方法的1个代码示例,这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞,您的评价将有助于系统推荐出更棒的C#代码示例。

示例1: ProcessMailMessage

        private void ProcessMailMessage(IMessage msg, MailMessage outMsg)
        {
            //Copy some of the more important headers
            outMsg.From = MailMessage.CreateEmailAddress(MapiUtils.GetStringProperty(msg, Tags.PR_SENDER_EMAIL_ADDRESS),
                MapiUtils.GetStringProperty(msg, Tags.PR_SENDER_NAME));
            if (MapiUtils.GetStringProperty(msg, Tags.ptagSentRepresentingName) != null) {
                outMsg.ReplyTo = MailMessage.CreateEmailAddress(MapiUtils.GetStringProperty(msg, Tags.ptagSentRepresentingEmailAddr),
                    MapiUtils.GetStringProperty(msg, Tags.ptagSentRepresentingName));
            }
            outMsg.Subject = MapiUtils.GetStringProperty(msg, Tags.PR_SUBJECT);

            IMAPITable recipientsTable = null;
            msg.GetRecipientTable(0, out recipientsTable);
            using (recipientsTable) {

                MAPI33.MapiTypes.Value[,] rows;
                recipientsTable.SetColumns(new Tags[] {Tags.PR_RECIPIENT_TYPE, Tags.PR_EMAIL_ADDRESS, Tags.PR_DISPLAY_NAME},
                    IMAPITable.FLAGS.Default);

                for( ;recipientsTable.QueryRows(1, 0, out rows) == Error.Success && rows.Length > 0; ) {
                    MAPI33.WellKnownValues.PR_RECIPIENT_TYPE recipType = (MAPI33.WellKnownValues.PR_RECIPIENT_TYPE)((MapiInt32)rows[0,0]).Value;
                    String emailAddr = null;
                    String emailName = null;

                    if (rows[0, 1] is MapiString) {
                        emailAddr = ((MapiString)rows[0, 1]).Value;
                    }

                    if (rows[0, 2] is MapiString) {
                        emailName = ((MapiString)rows[0, 2]).Value;
                    }

                    AddressType type = AddressType.To;

                    switch (recipType) {
                        case MAPI33.WellKnownValues.PR_RECIPIENT_TYPE.To:
                            type = AddressType.To;
                            break;

                        case MAPI33.WellKnownValues.PR_RECIPIENT_TYPE.Cc:
                            type = AddressType.Cc;
                            break;

                        case MAPI33.WellKnownValues.PR_RECIPIENT_TYPE.Bcc:
                            type = AddressType.Bcc;
                            break;
                    }

                    outMsg.AddRecipient(emailAddr, emailName, type);
                }
            }

            //Set the body.  There can be a plain Body, which is the plain text version of the message,
            //as well as an HtmlBody, which includes rich text formatting via HTML.
            //
            //This is complicated by the fact that, in MAPI, there are three possible sources
            //of the body: PR_BODY (plain text body), PR_BODY_HTML (HTML body), and PR_RTF_COMPRESSED
            //(RTF body).  Based on empirical observation, there is nearly always a PR_BODY, which is not surprising
            //as every HTML mail client I've ever encountered sends multi-part MIME messages with a plain text version
            //as well as HTML.  PR_BODY_HTML *seems* to be the HTML version of the message as specified by the sender,
            //and may not be present in plain text messages.
            //
            //It only gets complicated with PR_RTF_COMPRESSED (or just PR_RTF for short).  Often, HTML messages
            //don't have a PR_HTML at all, but rather a PR_RTF that has a bunch of RTF tags wrapped around the original
            //HTML of the message.  All messages I've seen have a PR_RTF, however only messages which were originally
            //received as HTML and subsequently transmogrified into RTF include the \@fromhtml RTF tag.
            //
            //Thus, the existence of this \@fromhtml tag is a roundabout way of determining if a message came from
            //the sender as HTML or text (ignoring for now the third possiblity; an older Exchange client using RTF).
            //
            //Therefore, when setting BodyHtml, we first check if PR_RTF includes this \@fromhtml (that's what
            //MapiUtils.BodyRtfToHtml does, among other things).  If it doesn't, BodyHtml is set to null.  If it
            //does, PR_BODY_HTML is checked first, and used to populate BodyHtml if it's non-null.  Failing that, the
            //unwrapped HTML from PR_RTF is used.  So:
            //
            // Body: Always PR_BODY
            // HtmlBody: PR_BODY_HTML if PR_BODY_HTML is non-null and PR_RTF includes the \@fromhtml tag
            //           The HTML embedded in PR_RTF if PR_BODY_HTML is null and PR_RTF includes \@fromhtml
            //           Else null.
            String propVal = null;
            if ((propVal = MapiUtils.GetLongStringProperty(msg, Tags.PR_BODY)) != null) {
                outMsg.Body = propVal;
            }

            //Check for HTML embedded in PR_RTF
            byte[] rtf = MapiUtils.GetBodyRtf(msg);
            if (rtf != null) {
                outMsg.HtmlBody = MapiUtils.BodyRtfToHtml(rtf);
                if (outMsg.HtmlBody != null) {
                    //There's HTML.  use PR_HTML if it's there, else stick w/ what we have
                    if ((propVal = MapiUtils.GetLongStringProperty(msg, Tags.PR_BODY_HTML)) != null) {
                        outMsg.HtmlBody = propVal;
                    }
                }
            }

            //Copy the attachments
            CopyAttachments(msg, outMsg);

            //Output all of the MAPI properties as extended headers, just in case they are needed later
//.........这里部分代码省略.........
开发者ID:anelson,项目名称:mapi_to_maildir,代码行数:101,代码来源:MaildirWriter.cs


注:本文中的MailMessage.AddRecipient方法示例由纯净天空整理自Github/MSDocs等开源代码及文档管理平台,相关代码片段筛选自各路编程大神贡献的开源项目,源码版权归原作者所有,传播和使用请参考对应项目的License;未经允许,请勿转载。