On Thu, 2006-03-02 at 11:49 +, Steve Loughran wrote:
> Looks like xop+xml is not a valid mime type. There is a bug in some of
> suns xsd's that say that + isnt allowed in a mime type, perhaps this is
> the same in software.
It is a valid MIME type:
www.iana.org/assignments/media-types/appli
Thilina Gunarathne wrote:
H...Too bad...
It seems the content-types generated by the two implementations are not
interoperable.. Did you try using SUN Mail in both the client and server
sides.
The relevant Content-Type header valueis;
multipart/related;
boundary=MIMEBoundaryurn:uuid:F02EC
Afkham Azeez wrote:
Hi Folks,
I encountered a somewhat critical situation, where if we use Sun's
JavaMail API implementation, instead of Geronimo's JavaMail API
implementation, parsing of MIME Encoded messages fails. The initial
failure occurs in the javax.mail.internet.ContentType class, where w
H...Too bad...
It seems the content-types generated by the two implementations are not interoperable.. Did you try using SUN Mail in both the client and server sides.
>The relevant Content-Type header valueis;>multipart/related;>boundary=MIMEBoundaryurn:uuid:F02ECC18873CFB73E21141271292
Hi Folks,
I encountered a somewhat critical situation, where if we use Sun's
JavaMail API implementation, instead of Geronimo's JavaMail API
implementation, parsing of MIME Encoded messages fails. The initial
failure occurs in the javax.mail.internet.ContentType class, where we
pass in the Content-
