Chris wrote: > Dropping from Inline to the above. Below is a reply to me on the gnugpg ML: > > "I use PGP/MIME signatures, which Mutt tags as inline MIME elements > following RFC 2183: > - - - Schnipp - - - > 2.1 The Inline Disposition Type > > A bodypart should be marked `inline' if it is intended to be > displayed automatically upon display of the message. Inline > bodyparts should be presented in the order in which they occur, > subject to the normal semantics of multipart messages. > - - - Schnapp - - - > > So a smart mail handler (eg. a mailing list software) that does not > know about PGP/MIME can at least gracefully fall back. > > > KMail does not set this field for the signature (it does for the mail > text), so this is a KMail bug. I'm not sure how receiving MUAs are > expected to cope with a non-existing Content-Disposition field, but > there is a hint in the RFC: "Unrecognized disposition types should be > treated as `attachment'." > > > Here is a rough outline of the MIME headers of our mails: > - - - Schnipp - - - > KMail, signed mail (ie. wrapper around mail text + signature): > Content-Type: multipart/signed; > boundary="nextPart2829039.id6uN21AOM"; > protocol="application/pgp-signature"; > micalg=pgp-sha1 > Content-Transfer-Encoding: 7bit > > KMail, mail text: > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > KMail, signature: > Content-Type: application/pgp-signature > - - - Schnapp - - - > > - - - Schnipp - - - > Mutt, signed mail: > Content-Type: multipart/signed; > boundary="CXFpZVxO6m2Ol4tQ" > protocol="application/pgp-signature"; > micalg=pgp-sha1; > Content-Disposition: inline > > Mutt, mail text: > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > Mutt, signature: > Content-Type: application/pgp-signature > Content-Disposition: inline > - - - Schnapp - - - > > > So the only difference is KMail's redundant Content-Transfer-Encoding > (which is 7bit by default anyway) and Mutt's Content-Disposition. > > > In conclusion, use whatever works for you, but please try to get the > KMail guys to add the Content-Disposition field by filing a bug with > them (they may regard it as a feature request)." > > In reading this it appears as though Kmail is the actual problem, or am I > reading it wrong? > > Hum... Chris, my sigs are sent as attachement (pgp/mime) by the Thunderbird's pgp extension (enigmail)... I send it this way because users on doze don't like to see the pgp signature in the email... so...
Maybe you can see the source of this e-mail to validate? -- +-----------------------------------------------------------+ Albert Charron, B.Sc. [EMAIL PROTECTED] http://pages.videotron.com/aysande +-----------------------------------------------------------+ Aucun produit Microsoft n'a été utilisé pour composer ce courriel. - No Microsoft product have been used to compose this e-mail. +-----------------------------------------------------------+
signature.asc
Description: OpenPGP digital signature
