Unfortunately, I don't think I can "fix" GMime 2.2 to treat multipart/signed content streams 100% opaquely without breaking API/ABI :-\
header reformatting as much as I could for the Content-* headers... it should help, but there's still no 100% guarentee.
<snip-2.0.17> Content-Type: multipart/mixed; boundary="fdj2RfSjLxBAspz7" Content-Disposition: inline
--fdj2RfSjLxBAspz7 </snip-2.0.17>
and
<snip-2.1-gmime> Content-Type: multipart/mixed; boundary="fdj2RfSjLxBAspz7" Content-Disposition: inline
--fdj2RfSjLxBAspz7 </snip-2.1-gmime>
(notice a missing empty line) and later on in the same message
<snip-2.1-gmime> --fdj2RfSjLxBAspz7 Content-Type: application/x-gzip Content-Disposition: attachment; filename="balsa-2.0-libmutt-patch.2004-07-02.diff.gz" Content-Transfer-Encoding: base64 <snip-2.1-gmime>
as far as the GMIME_DISABLE_DEPRECATED, I don't plan on removing them[snip discussion about depracted in general and g_mime_part_get_content in particular]
gmime would have to re-encode the content.
Cheers, Albrecht.
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Albrecht Dreß - Johanna-Kirchner-Straße 13 - D-53123 Bonn (Germany) Phone (+49) 228 6199571 - mailto:albrecht dress arcor de _________________________________________________________________________
Attachment:
signature.asc
Description: PGP signature