[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[iaik-jce] creating multipart/mixed messages with smime body parts



HI,
Has anyone considered the problem of inserting s/mime encrypted or signed
content as bodyparts in a larger multipart/mixed message.

I have a method which creates s/mime encrypted mimeparts and I want to
place this as a body part inside a bigger multipart/mixed message. To do
this, I'm calling the getheaders() and getContent() methods on the
encrypted mimepart to retrieve the content and headers; and plan to use
setHeaders() and setContent() to set the bodypart. BUt
getContent() doesn't return the base64 encoded content and instead
the encryptedContent datacontenthandler tries to retrieve the actual
content which was encrypted.

Does anyone have any ideas abt. how to approach this issue. How can you
get the base64 encoded encrypted content out of the message.or even better
How do you insert smime mimepart as bodyparts inside a bigger mime
message?

thanks in advance
-bharath



--
Mailinglist-archive at
http://jcewww.iaik.at/mailarchive/iaik-jce/jcethreads.html

To unsubscribe send an email to listserv@iaik.at with the folowing content:
UNSUBSCRIBE iaik-jce


***************************************************************************
*                                                                         *
* IAIK S/MIME Mapper Security Info                                        *
* ===================================                                     *
*                                                                         *
* for message:                                                            *
*   From: Bharath Vutukuru <bvutukur@ise.gmu.edu>                         *
*   Date: Fri, 6 Oct 2000 17:46:51 -0400 (EDT)                            *
*   Subject: [iaik-jce] creating multipart/mixed messages with smime body parts*
*                                                                         *
* Message S/MIME properties:                                              *
*                                                                         *
*   Encrypted using:    not encrypted                                     *
*                                                                         *
*   Digitally signed:   no                                                *
*   Signature valid:    n/a                                               *
*   Signature trusted   n/a                                               *
*                                                                         *
*                                                                         *
* Compliance with policy for email addresses *:                           *
*                                                                         *
*   Encryption:         OK (None or better required)                      *
*                                                                         *
*   Digital Signature:  OK (digital signature not required)               *
*                                                                         *
***************************************************************************