I am having problems sending a .jpg embedded into an email. If the message is sent internally, the picture works fine. However, if I send it anywhere else, it comes in as an attachment rather than embedded into the body of the email.
Is there anything I can do about this on my end? Or is it just the email clients that I am sending to?
Any help would be greatly appreciated.
Subject: Sending an email with an embedded .jpg
Edit your current location.
Mail tab, field “Format for messages addressed to internet addresses:” is probably currently set to “Notes Rich Text Format”.
Set it to “MIME Format”.
Chris Linfoot
Subject: RE: Sending an email with an embedded .jpg
Thanks for your response. Unfortuanately, It is already in Mime format. I did some playing around with it and what I figured out was, if it is in rich text, then it comes as a straight up attachment> But if it’s in mime then I get a red x where the picture should be and an unkown attachment below with the .jpg.
Subject: RE: Sending an email with an embedded .jpg
Well, yes. If you use Notes rich text, then the CD to MIME conversion at the server will convert in-line images into attachments. But if you use MIME then the image will be sent in-line in a multipart/related wrapper with
tags in the HTML part, the cid tags being references to the in-line images in the same multipart/related wrapper.
In the latter case, if the images are displayed at the receiving MUA as red crosses (broken images) then either
-
the receiving MUA has been configured not to display in-line images OR
-
there is some agent somewhere between your Notes client and the receiving MUA that is breaking the MIME in some way (adding a disclaimer often breaks MIME, or there may be an agent which is deliberately stripping in-line images for some reason) OR
-
the receiving MUA is broken in some way
You can verify this by looking at the raw message source as delivered to the remote MUA (how you do this varies depending upon what that MUA is, but in Outlook Express it is in the message properties box, details tab under a button labelled “message source”).
HTH
Chris Linfoot