CamelMultipartSigned derives from CamelMultipart which has interfaces for adding/removing/etc parts.
Jeff On Fri, 2005-03-18 at 00:30 +1300, Matt Brown wrote: > Hi, > > Thanks to some excellent help from NotZed on IRC I'm making good > progress on my e-plugin to handle inline pgp messages. > > Currently it's able to scan a message, and break it up into "parts" (ie, > message text and signature). > > Ideally what I would like to be able to do now, is construct a > camel_multipart_signed structure so that I can pass it directly to > gpg_verify and save on duplicated code. But I can't see how I can do > this atm. camel_multipart_signed only seems to support parsing an > incoming PGP/Mime type message and constructing a PGP/Mime type message > from a peice of plain text to be signed. The functions for adding > arbitrary parts are very obviously not implemented. > > I see a few options here > 1) Update camel_multipart_signed to allow me to add arbitrary parts to > it > 2) Create a new object derived from camel_multipart_signed that allows > arbitrary parts to be added > 3) Duplicate most of the functionality in gpg_verify such that I don't > ned to use a camel_multipart_signed. > > Option 1 seems to be best from my point of view, but I'm assuming there > is a reason why the add part functions were not implemented in the first > place? > > I realise I'm glossing over issues around canonicalisation etc atm, I > will deal with those once I've determined the basic approach towards > message verification. > > Regards > _______________________________________________ evolution-hackers maillist - [email protected] http://lists.ximian.com/mailman/listinfo/evolution-hackers
