Subject: Fully integrated MIME support? (was Re: error message)

From: [email-masked] (Mike McNally)
Date: 26 May 1994 17:56:44 GMT

In article <[email-masked]>,
David L Miller  <[email-masked]> wrote:
>
>Yes, Pine has fuly integrated MIME support.  In many cases users do not even
>realize they are using MIME... 

Care to elaborate on what "fully integrated MIME support" means in this
case?  I know that Pine can seperate/display at least some types of
MIME enclosures (for example image/gif and maybe audio/basic) but was
wondering if "fully integrated MIME support" meant that recent versions
of Pine have the ability to handle more complex / less common types of
MIME enclosures.  

If so, does the user have the ability to tell Pine how to handle
different enclosure types (as with metamail and MIME extended mh?) 
or is Pine's MIME support limited to well-known types and display
behaviors set at compile time?

---

From: Terry Gray <[email-masked]>
Date: Thu, 26 May 1994 13:24:01 -0700 (PDT)

Mike,
As you suggest "fully integrated" and "complete" are two different things...

For handling more MIME types on incoming mail, in 3.90 you will see
mailcap support, which will allow activating external processors for types
Pine doesn't have internal support for. 

On our short list is dealing with the input file typing problem for
outgoing mail...  probably via something like Mosaic's mimetypes file.  We
have some concerns about the robustness of this strategy, but I personally
see little alternative. Can't promise this part will make into 3.90, but
we definitely consider it a high priority. 

-teg