Identifying inline attachments rob_tt08 12/3/2008 5:14:04 AM 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?

Re: Identifying inline attachments "Dmitry Streblechenko" <dmitry[ at ]dimastr.com> 12/3/2008 7:20:26 AM Do you also test if the PR_ATTACH_LOCATION is set? Did you ask your client to install OutlookSpy or MFCMAPI to see what attachment properties are? -- Dmitry Streblechenko (MVP) http://www.dimastr.com/ OutlookSpy - Outlook, CDO and MAPI Developer Tool - "rob_tt08" <robtt08[ at ]discussions.microsoft.com> wrote in message news:F341C55B-B0DC-4EDF-8FB0-2762097B0BF2[ at ]microsoft.com... [Quoted Text] > 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?

Re: Identifying inline attachments rob_tt08 12/15/2008 2:24:01 AM Dmitry, Apologies for not responding sooner, but I have been working on something else and only just got back to this issue. I have not installed Outlook Spy on the client machine, but I was able to determine using a small custom utility that PR_ATTACH_CONTENT_ID is accessible in ANSI format, just not unicode (0x3712001E instead of 0x3712001F). After making this change to the code it once again functioned correctly on both the client site and our own servers. Thank you for your assistance. "Dmitry Streblechenko" wrote: [Quoted Text] > Do you also test if the PR_ATTACH_LOCATION is set? > Did you ask your client to install OutlookSpy or MFCMAPI to see what > attachment properties are? > > -- > Dmitry Streblechenko (MVP) > http://www.dimastr.com/ > OutlookSpy - Outlook, CDO > and MAPI Developer Tool > - > "rob_tt08" <robtt08[ at ]discussions.microsoft.com> wrote in message > news:F341C55B-B0DC-4EDF-8FB0-2762097B0BF2[ at ]microsoft.com... > > 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? > > >