Header image on our outgoing email is ruined when secured

Unanswered Question
Oct 21st, 2009
User Badges:

Our outgoing e-mail all gets a company header image. It's a 650 x 66 gif image that is applied to all outgoing messages right before hitting the ironport.

This header image goes out fine unsecured, but if we secure the message we run into a problem.

When I view the secure e-mail in CRES, I get a broken image link, and the image URL is changed to: cid:[email protected].44

Although in the secure e-mail there is an attachment called short_header.gif. If I click on this attachment I see the header image open in a new browser window.

This is NOT what we want. We want the short_header.gif to be in the body of the message, like company letterhead. We were told prior to purchasing this appliance that this was possible. This is why we didn't go with Tumbleweed for secure e-mail, because that stripped the image and sent it as an attachment.

Any idea's how to get this working?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
mychrislo_ironport Thu, 10/22/2009 - 10:33
User Badges:

I dont have CRES or PostX.

The RFC 2392 do state the URI scheme to be CID:XXXXXX.


Maybe it will help when you embed your image and use

and your attachment also use


Then ironport may not attempt to do the conversion by itself....(if it does...)

Hope it helps.
keithsauer507 Thu, 10/22/2009 - 14:51
User Badges:

We are sending out the cid: matched to the content-id.

For example, the content id header before the data is:

Content-Type: image/gif; name="short header.gif"
Content-Transfer-Encoding: base64
Content-ID: <200910229463981>
Content-Disposition: inline; filename="short header.gif"

and the image tag where we refrence this is embedded as:

This DOES work, but once we encrypt the message this breaks for some stupid reason. The CID isn't altered. It just shows short header.gif as an attachment and a broken image link at the top of the screen.

Any ideas?

keithsauer507 Fri, 10/23/2009 - 14:44
User Badges:

I opened a support case regarding this issue. Here's the response I got:

The IronPort's encryption engine currently does not support rendering of self-contained inline image attachments.

Adding this functionality is currently under consideration for a future release of AsyncOS. This feature request is logged as request number 50064. I will be adding you to the requesters for this feature request.


This Discussion