Subject: Content-type: header

From: Barry Landy <[email-masked]>
Date: Thu, 2 Mar 2000 14:09:58 +0000 (GMT)

One of my users wishes to set the content-tpe header to text/enriched so
that she can use <bold> this is in bold  </bold> to embolden text (and
if you did not see the meta-symbols and only boldened text, the meta
symbols were "<"bold">" and "<"/bold">" ).

We have several versions of Pine around: it seems as though 3.95/3.96
permits setting Customised-headers to Content-type: text/enriched but
modern versions (4.10 and 4.21) give an error message "not allowed to
change header "Content-type"".

Is this deliberate?
have I missed something?
Is there some other way to achieve this effect?

-- 
Barry Landy                        Computer Laboratory:+44 1223 334600
                                   Direct line:        +44 1223 334713
University of Cambridge Computing Service
New Museums Site                   Email:[email-masked]
Pembroke Street, Cambridge CB2 3QG

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

---

From: "Eduardo Chappa L." <[email-masked]>
Date: Thu, 2 Mar 2000 11:24:41 -0800 (PST)

*** Barry Landy wrote in the pine-info list today:

:) One of my users wishes to set the content-tpe header to text/enriched
:) Is there some other way to achieve this effect?
:) 
Dear Barry,

  There is a way to accomplish this, I posted this message to this list a
few months ago and here I am reposting it again. Notice that this allows
you to change the content-type header to text/html etc...

------------------------------------------------------------------------
"Quoted text"

Here's the way to do it. You have to follow several steps in order to make
this work.

First you have to create a script, say we call it mime_types. Your file
mime_types should say something like this:

#!/bin/sh
echo  "Content-Type:text/html" > $2

[note: You may need to replace echo by "echo -n"] 

remember to give yourself execution permission for this file.

Then you should go to your configuration file, and where it says
sending-filters it should say:

sending-filters=/full/path/to/myme_types _TMPFILE_ _MIMETYPE_

This is enough to accomplish the task, but you should continue to the next
step anyway.

After you do this take a look at the following configuration option:

            [ ]  compose-send-offers-first-filter      

and read its help in order to understand what it does. I have it checked.
Somehow, I could not change Charset to iso-8859-1, which was something I
wanted, it always uses US-ASCII

End of "Quoted text"
------------------------

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

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

---

From: Barry Landy <[email-masked]>
Date: Thu, 2 Mar 2000 22:00:00 +0000 (GMT)

This advice is based on the unix version of pine. What about PC-pine?

The other problem is that the regime in which the mail is processed is a
protected shell system, so users cannot obey scripts.

On Thu, 2 Mar 2000, Eduardo Chappa L. wrote:

:>*** Barry Landy wrote in the pine-info list today:
:>
:>:) One of my users wishes to set the content-tpe header to text/enriched
:>:) Is there some other way to achieve this effect?
:>:) 
:>Dear Barry,
:>
:>  There is a way to accomplish this, I posted this message to this list a
:>few months ago and here I am reposting it again. Notice that this allows
:>you to change the content-type header to text/html etc...
:>
:>------------------------------------------------------------------------
:>"Quoted text"
:>
:>Here's the way to do it. You have to follow several steps in order to make
:>this work.
:>
:>First you have to create a script, say we call it mime_types. Your file
:>mime_types should say something like this:
:>
:>#!/bin/sh
:>echo  "Content-Type:text/html" > $2
:>
:>[note: You may need to replace echo by "echo -n"] 
:>
:>remember to give yourself execution permission for this file.
:>
:>Then you should go to your configuration file, and where it says
:>sending-filters it should say:
:>
:>sending-filters=/full/path/to/myme_types _TMPFILE_ _MIMETYPE_
:>
:>This is enough to accomplish the task, but you should continue to the next
:>step anyway.
:>
:>After you do this take a look at the following configuration option:
:>
:>            [ ]  compose-send-offers-first-filter      
:>
:>and read its help in order to understand what it does. I have it checked.
:>Somehow, I could not change Charset to iso-8859-1, which was something I
:>wanted, it always uses US-ASCII
:>
:>End of "Quoted text"
:>------------------------
:>
:>Eduardo
:>http://www.math.washington.edu/~chappa/pine
:>
:>
:>
:>
:>
:>
:>

-- 
Barry Landy                        Computer Laboratory:+44 1223 334600
192, Gilbert Road                  Direct line:        +44 1223 334713
Cambridge CB4 3PB                  Home:               +44-1223-570417
                                   Email:[email-masked]

---

From: "Eduardo Chappa L." <[email-masked]>
Date: Thu, 2 Mar 2000 14:40:03 -0800 (PST)

:) This advice is based on the unix version of pine. What about PC-pine?
:) 
:) The other problem is that the regime in which the mail is processed is a
:) protected shell system, so users cannot obey scripts.
:) 

This is the only way to do it from within the program. Pine does not
provide another way to do it by itself. You can always try to postpone the
message and edit the headers of the postponed message, I do not know if
that will have the desired effect, but I assume it does.

---

From: Ed Arnold <[email-masked]>
Date: Fri, 3 Mar 2000 09:37:19 -0700 (MST)

Perhaps I don't understand the problem, but it appears on the surface
that it might not be necessary to write a script to do this.  I assume the
PC-PINE user has the equivalent of a unix .mime.types file, which is
probably located somewhere down in ...ProgramFiles\Netscape\... .  (It
ought to be possible to figure out which file it is by using Windows
Explorer to search for expected content, e.g. "audio/x-wav".)  Assuming
the user wants to *send* an existing file which is known to be in this
text/enriched format, and assuming the file has a unique extension, (e.g.
".TXE") which is understood by whatever tool (a browser?) is being used
on the receiving end to read it, can't the user just put a line in their
 .mime.types-equivalent file such as

type=text/enriched      exts="txe"

and then just "pine -attach file.txe [email-masked]"?

I tried the equivalent operations on a unix box (put the line in .mime.types,
create a file named "tst.txe", then do an attach).  The attachment in the
message I sent myself ended up with an attachment header which says

Content-Type: type=text/enriched; name="tst.txe"

---

From: "Eduardo Chappa L." <[email-masked]>
Date: Fri, 3 Mar 2000 11:42:50 -0800 (PST)

*** Ed Arnold ([email-masked]) wrote today:

:) Perhaps I don't understand the problem, but it appears on the surface
:) that it might not be necessary to write a script to do this.  I assume the
:) PC-PINE user has the equivalent of a unix .mime.types file, which is

Yes this works if you want to *attach* a file, but what if you want to
*compose* a message with content type header of text/enriched from
scratch? Pine sends every mail in the text/plain format, unless you
instruct it by means of a script and sending-filters not to do so or you
alter the headers by some other mean outside pine.

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

---

From: Barry Landy <[email-masked]>
Date: Sat, 4 Mar 2000 22:37:48 +0000 (GMT)

yes, that works fine, provided you are happy to put it all in an
attachment. Pine can process the attachment just fine so no browser is
needed.

The "Mime-type" file need contain just

text/enriched txe

On Fri, 3 Mar 2000, Ed Arnold wrote:

:>Perhaps I don't understand the problem, but it appears on the surface
:>that it might not be necessary to write a script to do this.  I assume the
:>PC-PINE user has the equivalent of a unix .mime.types file, which is
:>probably located somewhere down in ...ProgramFiles\Netscape\... .  (It
:>ought to be possible to figure out which file it is by using Windows
:>Explorer to search for expected content, e.g. "audio/x-wav".)  Assuming
:>the user wants to *send* an existing file which is known to be in this
:>text/enriched format, and assuming the file has a unique extension, (e.g.
:>".TXE") which is understood by whatever tool (a browser?) is being used
:>on the receiving end to read it, can't the user just put a line in their
:> .mime.types-equivalent file such as
:>
:>type=text/enriched      exts="txe"
:>
:>and then just "pine -attach file.txe [email-masked]"?
:>
:>I tried the equivalent operations on a unix box (put the line in .mime.types,
:>create a file named "tst.txe", then do an attach).  The attachment in the
:>message I sent myself ended up with an attachment header which says
:>
:>Content-Type: type=text/enriched; name="tst.txe"
:>
:>
:>On Thu, 2 Mar 2000, Eduardo Chappa L. wrote:
:>
:>> *** Barry Landy wrote in the pine-info list today:
:>> 
:>> :) One of my users wishes to set the content-tpe header to text/enriched
:>> :) Is there some other way to achieve this effect?
:>> :) 
:>> Dear Barry,
:>> 
:>>   There is a way to accomplish this, I posted this message to this list a
:>> few months ago and here I am reposting it again. Notice that this allows
:>> you to change the content-type header to text/html etc...
:>> 
:>> ------------------------------------------------------------------------
:>> "Quoted text"
:>> 
:>> Here's the way to do it. You have to follow several steps in order to make
:>> this work.
:>> 
:>> First you have to create a script, say we call it mime_types. Your file
:>> mime_types should say something like this:
:>> 
:>> #!/bin/sh
:>> echo  "Content-Type:text/html" > $2
:>> 
:>> [note: You may need to replace echo by "echo -n"] 
:>> 
:>> remember to give yourself execution permission for this file.
:>> 
:>> Then you should go to your configuration file, and where it says
:>> sending-filters it should say:
:>> 
:>> sending-filters=/full/path/to/myme_types _TMPFILE_ _MIMETYPE_
:>> 
:>> This is enough to accomplish the task, but you should continue to the next
:>> step anyway.
:>> 
:>> After you do this take a look at the following configuration option:
:>> 
:>>             [ ]  compose-send-offers-first-filter      
:>> 
:>> and read its help in order to understand what it does. I have it checked.
:>> Somehow, I could not change Charset to iso-8859-1, which was something I
:>> wanted, it always uses US-ASCII
:>> 
:>> End of "Quoted text"
:>> ------------------------
:>> 
:>> Eduardo
:>> http://www.math.washington.edu/~chappa/pine
:>> 
:>> 
:>> 
:>> 
:>> 
:>> 
:>> -- 
:>> Eduardo
:>> http://www.math.washington.edu/~chappa/pine/
:>
:>