Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As you are aware, everything passed as email message has to be textualized. </p> <ul> <li>You must create an email with a multipart/mime message.</li> <li>If you're adding a physical image, the image must be base 64 encoded and assigned a Content-ID (cid). If it's an URL, then the <code>&lt;img /&gt;</code> tag is sufficient (the url of the image must be linked to a Source ID).</li> </ul> <p>A Typical email example will look like this:</p> <pre><code>From: foo1atbar.net To: foo2atbar.net Subject: A simple example Mime-Version: 1.0 Content-Type: multipart/related; boundary="boundary-example"; type="text/html" --boundary-example Content-Type: text/html; charset="US-ASCII" ... text of the HTML document, which might contain a URI referencing a resource in another body part, for example through a statement such as: &lt;IMG SRC="cid:foo4atfoo1atbar.net" ALT="IETF logo"&gt; --boundary-example Content-Location: CID:somethingatelse ; this header is disregarded Content-ID: &lt;foo4atfoo1atbar.net&gt; Content-Type: IMAGE/GIF Content-Transfer-Encoding: BASE64 R0lGODlhGAGgAPEAAP/////ZRaCgoAAAACH+PUNv cHlyaWdodCAoQykgMTk5LiBVbmF1dGhvcml6ZWQgZHV wbGljYXRpb24gcHJvaGliaXRlZC4A etc... --boundary-example-- </code></pre> <p>As you can see, the <code>Content-ID: &lt;foo4atfoo1atbar.net&gt;</code> ID is matched to the <code>&lt;IMG&gt;</code> at <code>SRC="cid:foo4atfoo1atbar.net"</code>. That way, the client browser will render your image as a content and not as an attachement.</p> <p>Hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload