[jboss-user] [JBoss Seam] - Re: inline image email attachment

Thu Jan 24 18:22:58 EST 2008

I have now tried with Seam 2.0.1.CR1 with the same results.

here is what is happening (i'll include all this stuff in the JIRA ticket as well):

  | Header...
  | Content-Type: multipart/mixed; boundary="outer-boundary"
  |  
  | --outer-boundary
  | Content-Type: image/gif; charset=ISO-8859-1; name=logo.gif
  | Content-Transfer-Encoding: base64
  | Content-ID: <image-content-id>
  | Content-Disposition: inline; filename=logo.gif
  | 
  | BASE64=ENCODED=IMAGE=DATA==
  | --outer-boundary
  | Content-Type: multipart/alternative; boundary="inner-boundary"
  | Content-Disposition: inline
  | 
  | --inner-boundary
  | Content-Type: text/plain; charset=ISO-8859-1
  | Content-Transfer-Encoding: 7bit
  | Content-Disposition: inline
  | 
  | my plain text
  | --inner-boundary
  | Content-Type: text/html; charset=ISO-8859-1
  | Content-Transfer-Encoding: 7bit
  | Content-Disposition: inline
  | <html>
  | 	<body>
  | 		my html text<br />
  | 		<img src="cid:image-content-id" />
  | 	</body>	
  | </html>
  | --inner-boundary--
  | 
  | --outer-boundary--
  | 

and here is how it looks like the boundaries/content types need to be set up:

  | Header...
  | Content-Type: multipart/alternative; boundary="outer-boundary"
  |  
  | --outer-boundary
  | Content-Type: text/plain; charset=ISO-8859-1
  | Content-Transfer-Encoding: 7bit
  | 
  | my plain text
  | --outer-boundary
  | Content-Type: multipart/related;
  |  boundary="inner-boundary"
  | 
  | --inner-boundary
  | Content-Type: text/html; charset=ISO-8859-1
  | Content-Transfer-Encoding: 7bit
  | <html>
  | 	<body>
  | 		my html text<br />
  | 		<img src="cid:image-content-id" />
  | 	</body>	
  | </html>
  | --inner-boundary
  | Content-Type: image/gif; name="logo.gif"
  | Content-Transfer-Encoding: base64
  | Content-ID: <image-content-id>
  | Content-Disposition: inline; filename="logo.gif"
  | 
  | BASE64=ENCODED=IMAGE=DATA==
  | --inner-boundary--
  | 
  | --outer-boundary--
  | 

it's a bit hard to read so i'll summarize:
- it looks like Content-Disposition: inline; is on every content declaration, i don't know if this matters
- in order to have proper inline html image content it looks like both the file and the content it's being included in is required to be part of Content-Type: multipart/related; http://tools.ietf.org/html/rfc2387

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123257#4123257

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123257