[49804] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Stop it with putting your e-mail body in my MUA OT

daemon@ATHENA.MIT.EDU (Stephen Sprunk)
Wed Jul 10 12:12:22 2002

From: "Stephen Sprunk" <ssprunk@cisco.com>
To: "Leo Bicknell" <bicknell@ufp.org>,
	"Email List: nanog" <nanog@nanog.org>
Date: Wed, 10 Jul 2002 11:11:41 -0500
Errors-To: owner-nanog-outgoing@merit.edu


Thus spake "Leo Bicknell" <bicknell@ufp.org>
> More to the point, if anyone bothered to look at a MIME/PGP message,
> that's all it is.  Specifically, you'll see two parts:
>
> ] Content-Type: text/plain; charset=us-ascii
> ] Content-Disposition: inline
> ] Content-Transfer-Encoding: quoted-printable
>
> ] Content-Type: application/pgp-signature
> ] Content-Disposition: inline
>
> If your mailer isn't showing you the first one as a text/plain
> message, even if it doesn't understand the second you need a new
> mailer.

You left out the MIME header that's actually causing the problem:

] Content-Type: multipart/signed; micalg=pgp-md5;
]  protocol="application/pgp-signature"; boundary="0eh6TmSyL6TZE2Uz"

My MUA understands multipart/mixed and multipart/alternative; it doesn't
understand multipart/signed and therefore has no clue what to do with the
message as a whole, even if it does understand one of the component's type.

If anyone has a procmail recipe for dropping the second part and promoting the
text/* to main body, I'm all ears.

S


home help back first fref pref prev next nref lref last post