R
rob_tt08
We have written an Outlook 2003 AddIn that uses the MAPI property
PR_ATTACH_CONTENT_ID (0x3712001F) to distinguish between inline attachments
such as signature images and normal attached files.
This has been working satisfactorily up until now, but when we installed the
AddIn for a new client, we found that it was no longer detecting the
attachments as inline even though the internet headers of some of the
messages show that content-id has a value, so the property should be there as
well. The client is running Outlook over Terminal Services.
However, when we test the same messages on our development machines, the
attachments are correctly identified as inline.
Are there situations in which the property would be removed but still
visible in the headers? How can we reliably distinguish between these two
types of attachments if the content id is not always present?
PR_ATTACH_CONTENT_ID (0x3712001F) to distinguish between inline attachments
such as signature images and normal attached files.
This has been working satisfactorily up until now, but when we installed the
AddIn for a new client, we found that it was no longer detecting the
attachments as inline even though the internet headers of some of the
messages show that content-id has a value, so the property should be there as
well. The client is running Outlook over Terminal Services.
However, when we test the same messages on our development machines, the
attachments are correctly identified as inline.
Are there situations in which the property would be removed but still
visible in the headers? How can we reliably distinguish between these two
types of attachments if the content id is not always present?