OpenEMM Technical Support Forum

Is it still feasible to 'embed' images into mails on OpenEMM 6.2 - ie true OfflineHTML?

Elsewhere on the forums (eg https://forum.openemm.org/post253.html#p253) it appears that an image can be truly enbedded intothe body of the mail - using the image code after the mail boundary marks.

Quote:

4. Look at the source code of your newsletter and you will see an image reference like

Code: Select all
<img src=3D"http://www.openemm.org/fileadmin/images/openemm.gif" width=3D="79" height=3D"79" align=3D"right" />


5. but also the image included in special encoding format at the end:

Code: Select all
---==AGNITASOUTER164240059B2900000B==
Content-Type: image/gif
Content-Transfer-Encoding: base64
Content-Location: http://www.openemm.org/fileadmin/images/openemm.gif

R0lGODlhTwBPAPcAAAAAAAAAMwAAZgAAmQAAzAAA/wAzAAAzMwAzZgAzmQAzzAAz/wBmAABmMwBm
ZgBmmQBmzABm/wCZAACZMwCZZgCZmQCZzACZ/wDMAADMMwDMZgDMmQDMzADM/wD/AAD/MwD/ZgD/
mQD/zAD//zMAADMAMzMAZjMAmTMAzDMA/zMzADMzMzMzZjMzmTMzzDMz etc

Is this format and creation still feasible?

If you select "Offline HTML" as mail format and upload the images via the "graphics components" tab into OpenEMM, the images are automatically inserted into the mail code.

Thanks Martin

Yes - I have successfully achieved this now and viewed true off-line emails in MS Outlook.

The next question is - the method used by OpenEMM is the one described in section 9.2 of the RFC2110 document (http://tools.ietf.org/html/rfc2110#section-4.3) - ie with absoulte URL's.

Can this method be be changed to the 'Content-ID' version?

Part of the problem we have is that we have a large customer base using BlackBerry BIS email service - by trial it appears that this is the only method that allows images to be displayed without downloading - I think that the mail client is seeing the absoute URL, presuming that the format is standard HTML and ignoring the attchmnets.

Is there a simple change in a config file or the FCK Editor?

Thanks

No, a change is not possible right now, because this is rather complicated. But it is an interesting suggestion and we will explore it further (especially since the importance of mobile devices is growing).

BTW, we used Content-ID for our commercial product in the beginning, but it turned out that some webmailers had (have?) problems with this format and this is the reason why we changed to absolute URIs.