Subject: Using Pine with messages sent in http

From: John Heenan <[email-masked]>
Date: Sat, 17 Jan 1998 12:07:01 +1100 (EST)

Hi

I get email sent to me written in http.  To read it I save the file
attachments and then read the message surrounded by http.  I couldn't find
a way of setting up mime types to cater for this.  

Is there a quick way to instruct the Pine viewer to display messages it
does not know how to deal with, or is there a way to instruct pine to use
another viewer on command, like lynx?

Regards

John Heenan

---

From: John Heenan <[email-masked]>
Date: Sat, 17 Jan 1998 12:08:45 +1100 (EST)

Forgot to mention I use Pine on Linux.

---

From: Drachen <[email-masked]>
Date: Fri, 16 Jan 1998 17:17:31 -0800 (PST)

It's seemed to me that one could pipe it through lynx (that only works for
un*x systems, though). But my computer has been loathe to do that. 

However, that was my old one, my new one seems to handle viewers and such
much better. Maybe I should try it again. (better hardware, more current
version of linux and pine, etc)

anyway, said commands would be V(iew)(highlight the appropriate
attatchment) | lynx

oh, and you have to set that in the configuration.

I don't know if this will work, though. it just should theoretically

Vinnie

---

From: John Heenan <[email-masked]>
Date: Sat, 17 Jan 1998 13:50:36 +1100 (EST)

Thanks for your reply Vinnie.  

I have been able to add an /etc/mailcap entry for text/HTML to enable HTML
to be shown.  Part of my original problem was that text/plain was not even
being displayed.  This problem has been fixed up also. It appears http
emailers also send a plain version of http. 

An /etc/mailcap entry that worked for me is
text/HTML; lynx -force_html -dump %s; copiousoutput

With regard to piping the output to Lynx, I don't think there is a way
within Lynx for it to accept a html file to be proceesed from standard
input.  However piping the output to a script could set up a file for lynx
to read from and then send output to standard output for the viewer. 

John

---

From: Drachen <[email-masked]>
Date: Fri, 16 Jan 1998 18:53:00 -0800 (PST)

hmm. I think you're right..I mean about lynx not reading from standard
input. it would (more or less) explain what happens on this machine when I
try to pipe it. (nothing explains what happens on the last machine, except
perhaps the fact that it was held together by duct tape, bailing wire and
velcro)

Time to fire up vi and write a script.

-force_html looks useful too. I don't know why I havne't seen it before.

Vinnie

---

From: Shoeless in San Jose <[email-masked]>
Date: Fri, 16 Jan 1998 21:02:38 -0800 (PST)

On Sat, 17 Jan 1998, John Heenan wrote:

> I have been able to add an /etc/mailcap entry for text/HTML to
> enable HTML to be shown.  Part of my original problem was that
> text/plain was not even being displayed.  This problem has been
> fixed up also. It appears http emailers also send a plain version of
> http. 

Usually.  I've seen one lately that didn't.  Since I hadn't gotten
this set up till now, thanks to you folks, I'd just skip it.

> text/HTML; lynx -force_html -dump %s; copiousoutput

This is what got it working.  I tried the script below; it would
display the message which was unreadable otherwise (unless I saved and
viewed the file), but it still contained all the HTML tags.  The one
above works; the one below didn't quite cut it:

text/html;lynx -force_html %s;test=test -n "$LYNX_VERSION"
text/html; shownonascii iso-8859-1 %s; copiousoutput
text/html; shownonascii iso-8859-8 %s; copiousoutput
text/html; shownonascii iso-8859-7 %s; copiousoutput

> With regard to piping the output to Lynx, I don't think there is a
> way within Lynx for it to accept a html file to be proceesed from
> standard input.  However piping the output to a script could set up
> a file for lynx to read from and then send output to standard output
> for the viewer. 

I tried piping it through Lynx which was suggested earlier.  I was
using the four-line script above (haven't tried it with the new
one-liner, but it's more work to do that anyway), and it just locked
up.  Couldn't suspend the job; could only cut the connection and
re-logon, so I think I'll stick with the one-liner.  That fixed the
problem.

Greg
[email-masked]