K
Krishna
I am developing an "encryption type" plug-in to Outlook 2003 using
C# based on Outlook Object Model.
I am having trouble when the email has an inline image, i.e. when an
image is pasted into the email message body. I understand that the
image is referenced with a CID and it is actually transmitted as an
attachment.
Here is my problem.
On the receiving side, when does outlook actually remove the image from
attachment and place it inline in the email message.
When I place my decryption code in mail-item open event-handler, the
image is not shown and instead a red-cross mark is shown. All I do is
in the mail-item open event-handler; I read the received email body,
decrypt it and set the HTMLBody to the decrypted data. But, if I close
the inspector and let outlook open the same decrypted message; I get
back the email with the inline image. (I am not doing any encryption to
the attachment.)
Are there any flags that I should set in addition to setting the
HTMLBody of the mail-item in the receiving side.
Any help/suggestion is greatly appreciated.
Thanks,
Krishna.
C# based on Outlook Object Model.
I am having trouble when the email has an inline image, i.e. when an
image is pasted into the email message body. I understand that the
image is referenced with a CID and it is actually transmitted as an
attachment.
Here is my problem.
On the receiving side, when does outlook actually remove the image from
attachment and place it inline in the email message.
When I place my decryption code in mail-item open event-handler, the
image is not shown and instead a red-cross mark is shown. All I do is
in the mail-item open event-handler; I read the received email body,
decrypt it and set the HTMLBody to the decrypted data. But, if I close
the inspector and let outlook open the same decrypted message; I get
back the email with the inline image. (I am not doing any encryption to
the attachment.)
Are there any flags that I should set in addition to setting the
HTMLBody of the mail-item in the receiving side.
Any help/suggestion is greatly appreciated.
Thanks,
Krishna.