]
nathan dennis commented on JBSEAM-4841:
---------------------------------------
JBSEAM-4630 ... im not sure how i missed it.
disregard this ...
Mail MIME Attachment IS NOT TO SPEC
-----------------------------------
Key: JBSEAM-4841
URL:
https://issues.jboss.org/browse/JBSEAM-4841
Project: Seam 2
Issue Type: Bug
Components: Mail
Affects Versions: 2.2.0.GA
Environment: Centos 5.x, Centos 6.x, Jboss 5.1.0, Thunderbird 5.x, Thunderbird
6.x
Reporter: nathan dennis
Assignee: Pete Muir
Labels: MIME, RFC2387, attachement, mail, stucture
Message containing attachments not intended to be displayed inline are being formatted
incorrectly. The current MIME type is not to spec RFC2387.
(
http://www.ietf.org/rfc/rfc2387.txt) As a result, mail clients that have chosen to
strictly follow the spec will no longer correctly handle non inline attachments generated
with seam mail.
i believe this is related to JBSEAM-3906. However that work around listed there will
create more problems than it will fix. (i actually tried that workaround on my own before
i even visited the forum for help.) on closer inspection, it will attach ALL attachments
using the inherited parent MIME type mixed which will cause all of your inline content to
not be formatted.
ei...
<m:attachment
value="/img.png"
contentType="image/jpeg"
fileName="header.jpg"
status="headerPhoto"
disposition="inline" />
<img src="cid:#{headerPhoto.contentId}" />
will no long work. i actually started rewriting some of UIBody.java only to realize i
needed to read and study more before i wrote a patch.
below is a sample message.
Message-ID: <1992253538.401315329484805.JavaMail.jboss@node1>
Subject: Online Credit Application
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_65_749177026.1315329484754"
X-Priority: 5
Priority: Non-urgent
Importance: low
X-Sent-From: Node1
Date: Tue, 6 Sep 2011 13:18:04 -0400 (EDT)
------=_Part_65_749177026.1315329484754
Content-Type: multipart/related; (***********************PROBLEM IS HERE and
inherited below*********************)
boundary="----=_Part_66_721653621.1315329484804"
------=_Part_66_721653621.1315329484804
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
------=_Part_66_721653621.1315329484804
Content-Type: application/pdf; name=XXXXXXXXXXX.pdf
Content-Transfer-Encoding: base64
Content-ID: <aeamddeazitbtngdcsln>
Content-Disposition: attachment; filename=XXXXXXXXXXX.pdf
JVBERi0xLjQKJeLjz9MKMyAwIG9iaiA8PC9MZW5ndGggMTY0My9GaWx0ZXIvRmxhdGVEZWNvZGU+
PnN0cmVhbQp4nJVY227bNhi+91MQ2MVSoGEkijrtZkucZHWRUxsPRYfe0BITc5FFl5KbeE/TR91P
yk5s+aeTIUhgh/z+85HfByfjQRjTMCUZS2gWkXE5CMhhEoaUM/vlbDz4NPjufhn5CGd/DkLyOGCM
xiTNGU0TEscBiTgNUmLk4HbjOM1okrvjEDlO8oAyd5pllOf90zShYeQHhzmNQ3ccJzRh/eMgppx7
0XGa0yh1x6D17nESUz/rmOeUrY4xcATmTPxoEDzI/WgQPGBeNE8ZzbLO4oyGvH8cZzQL/egQHOJO
--
This message is automatically generated by JIRA.
For more information on JIRA, see: