Running E-Mail Duplicate Detection through API

I am importing messages into WorkSite, and I am setting the Message ID. What do I need to do to get the duplicate detection to run, so that I do not end up with multiple files?

Find more posts tagged with

Comments

guido1

are you sure you're setting the imProfileMessageID property value to the MAPI object's PR_INTERNET_MESSAGE_ID property value?

The ID should look something like

[indent]

20060424194714.28714.qmail@web34305.mail.mud.yahoo.com

[/indent]

the value's angular parentheses ("<" and ">") seem to be removed when you drag'n'drop a message to a FileSite folder, so remember to strip these out before you set the property

Migrateduser

Yes, I am setting the property, but I am still getting multiple copies of the messages.

guido1

explain a little what you mean by getting multiple copies

how are you importing the email? and how are you then testing whether it has been added as a unique record?

my code to import emails creates a new IManDocument, populates all the relevant properties, and most importantly sets the imProfileMessageUniqueID attribute. Something like:

// doc will most likely be a new IManDocument object instanced with the CreateDocument method

// PR_INTERNET_MESSAGE_ID is the passed-in unique MAPI key of the message

doc.SetAttributebyId(IManage.imProfileAttributeId.imProfileMessageUniqueID, PR_INTERNET_MESSAGE_ID);

I then add the new IManDocument reference to the target FileSite folder

I can test it's unique by trying to manually drag over the recently imported message to the target folder, and hey presto FileSite warns me it's already there

You could also test by creating a search using an instance of the IManPRofileSearchParameters and setting the imProfileContainerID to the target folder, and the imProfileMessageUniqueID to the PR_INTERNET_MESSAGE_ID of the message.

is this way off track?

guido1

oh, might be obvious but you may want to check that FileSite is actually set up to detect duplicate emails! (check the Import Settings options)

Migrateduser

I am importing the file through the API. What I want is to be able to have an API-based import detect the message, without having to search for the message by the Message ID as a separate step.

If I manually drag and drop the message into the folder using FileSite, the built-in duplicate detection works correctly. The problem is in an API-based import: If I am importing a batch of messages, how do I execute the "duplicate detection" through the API? Is there a special call/setting to do this, or is this feature merely a search for an item with the same Message ID? If that is the case, then I can do it that way, I just thought if there was a nifty call to do this, it might be faster...

guido1

if there's a nifty call then it's not an obvious one

As are you, I am searching the database in advance of the import using the MessageID as a constraint. It's pretty quick

although I've done no definitive benchmarking, the import tool I have will scan about 27,000 documents an hour. In other words it will search for unique messageIDs at about that rate

Importing obviously takes the bulk of the time - I manage an average of 9,000 per hour, but this is dependant on a number of hardware constraints

Migrateduser

Understood. Then if there is no built-in API call (which I assume from the silence from Interwoven, but I guess I'll open a Dev Support issue anyway, just to make sure), why does the duplicate detection in WorkSite restrict itself to just the folder the message is being dragged into? Performance, obviously, but why not a setting to check for duplicates in the entire database...?

jny

The IManExt2.IManEmailDuplicateDetectCmd is used to perform dup-detection, and here's an example in VB:

Dim dms As New ManDMS
Dim sess As IManSession
Dim db As IManDatabase
Dim dupDetectCmd As IManEmailDuplicateDetectCmd
Dim context As ContextItems

Set sess = dms.Sessions.Add("NTDEVSUPPORT")
sess.TrustedLogin

Set db = sess.Databases.ItemByName("DSS1")

Set context = New ContextItems
With context
.Add "DestinationObject", db
.Add "IManExt.Import.MessageID", "ECB66ACC4035AF4CA2E9F6420A12CEFD03FC1E79@exbecg01.Interwoven.com"
End With
Set dupDetectCmd = New IManEmailDuplicateDetectCmd
With dupDetectCmd
.Initialize context
.Update
.Execute
Dim retDoc As IManDocument
Set retDoc = context.Item("IManExt.DuplicateEmail")
MsgBox retDoc.Description
End With

Migrateduser

Thanks. Interesting. I had already implemented a quick search function to search for the Message ID and return an iManDocuments collection for detected duplicate(s).

This command seems to be database-specific, not folder-specific, or can the DestinationObject be other types of items (folder/tab/WorkSpace)? I assume that if the duplicate e-mail is not found,

Set retDoc = context.Item("IManExt.DuplicateEmail")

will throw an error?

jny

The DestinationObject can be a database or a container.

Your assumption is correct: you would need to resume the error to check for the presence of a possible return value.

benteng

IManDocument retDoc = (IManDocument)context.Item("IManExt.DuplicateEmail");

It throws Exception ArgumentException. It seems "IManExt.DuplicateEmail" not exist. AnyIdea? Thanks

jny

the DestinationObject can be a folder, but it must be of NRTFolder type.