Subject: Question about _MIMETYPE_ token.

From: "Andres Plaza R." <[email-masked]>
Date: Sun, 8 Jul 2001 21:36:13 -0400 (CLT)

Hi!

	I'm trying to change the Content-type of an email sent from
Pine. I use a shell in the sending-filters option that reads _TMPFILE_,
_RECIPIENTS_ and _MIMETYPE_.

	The problem is that everytime that I change the _MIMETYPE_ to
something like:

Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="----4928B7D1C220F1D22E19A1AE71B967E3"

Pine send the mail with his default value:

Content-Type: TEXT/PLAIN; charset=US-ASCII

	Anybody knows why this happend?

			Thanks in advance...
-- 
					Andres Plaza R.
				      Email: [email-masked]
				   http://la.mafia.cl/aplaza

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Eduardo Chappa <[email-masked]>
Date: Mon, 9 Jul 2001 09:19:15 -0700 (PDT)

*** Andres Plaza R. ([email-masked]) wrote in the pine-info list on Jul 8, 2001:

:) 	The problem is that everytime that I change the _MIMETYPE_ to
:) something like:
:)
:) Content-Type: multipart/signed;
:) protocol="application/x-pkcs7-signature"; micalg=sha1;
:) boundary="----4928B7D1C220F1D22E19A1AE71B967E3"
:)
:) Pine send the mail with his default value:
:)
:) Content-Type: TEXT/PLAIN; charset=US-ASCII

I think this is because you can only change the mime-type of a message to
TEXT/*, so TEXT/HTML is fine, but not "multipart/signed".

-- 
Eduardo
http://www.math.washington.edu/~chappa/pine/