How to get a generic mailitem ConversationID appearance for the same email thread from different users

I am developing an OUTLOOK 2010 add-on in C #. This addin will create conversation based actions. For example, one user creates a new email, others reply, forward or CC, treat this email chain as one conversion stream. Email messages have the same mailItem.ConversationID. Based on this conversationID, my program generated an activity and associated the talkid with the activity that can be seen in every message in this email chain. Everything works fine on my machine (I reply, go ahead, cc in the same email thread, it gets the same conversation id). However, when another custom email address triggers my actions with the program, it generates a different ConverstationID (the same email chain).

My question is: 1.ConversationID only works on local? As with the same email network on different user machines, is the conversation ID different? 2.Is there a universal mailitem conversation id for one email thread if the user is using the same version of OUTLOOK?

var mailItem = this.OutlookItem as OutlookNS.MailItem;


        if (mailItem.ConversationID != null )
        {
            OutlookHelper.Conversation_Index = mailItem.ConversationIndex;
            OutlookHelper.Conversation_Topic = mailItem.ConversationTopic;
            OutlookHelper.Current_ConversationID = mailItem.ConversationID;
            CreateActivity(mailItem.ConversationTopic,mailItem.ConversationID);
        }

      

I've already tried EntryID, this attribute keeps changing.

+3


source to share


1 answer


I figured it out myself. All emails in the same email chain have the same first 44-bit ConversationIndex. Each time a new responder replies to this email, the ConversationIndex will add a new 44-character ballast string. This is a universal identification applied to a user using a differet machine. But when the subject of this email is changed, new 44 charaters ConversationIndex will be created. ConversationID only works on LAN to track email messages in the same email chain.



+1


source







All Articles