[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pine-info
Subject:    Re: When will pine be truly MIME-compliant?
From:       David L Miller <dlm () cac ! washington ! edu>
Date:       1994-08-31 16:17:25
[Download RAW message or body]


Pine does meet the minimal conformance requirements of RFC1521.  We have not
yet completely implemented some of the optional subtypes, like
message/external-body, but we are working on them.  We also intend to support
RFC1522 in a future release....

|\ |  |\/|  David L. Miller    dlm@cac.washington.edu  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

On Wed, 31 Aug 1994, Jan Snellman wrote:

> It seems that MIME does not really understand the message/external-body 
> subtype: viewing the FAQ-pointer in the comp.mail.mime newsgroup, I could 
> not automatically retrieve the FAQs with ftp. GNUS with metamail support 
> handles this correctly.
> 
> Furthermore, it would be very nice if RFC 1522, that allows ISOLATIN 
> characters in message headers, would be implemented. I get a lot of 
> messages from Eudora users; they look kind of strange with the raw Q 
> encoding. 
> 
> Jan Snellman         : "Whenever you find that you are on the side of the 
> jans@matematik.su.se : majority, it is time to reform."  M T
> 
> 
> 

[prev in list] [next in list] [prev in thread] [next in thread]