Re: Bug#932: Pine over-encodes files and auto-requests document
This issue has been discussed numerous times on comp.mail.mime and
comp.mail.misc, but here's the executive summary:
o It is true that Pine encodes all attachments, even text.
o The intended way to send text files that (a) don't need to arrive
exactly intact or (b) are going to non-MIME-capable destinations
is indeed to use ^R rather than MIME-attach.
o There are excellent reasons for this behavior: we want Pine to be
known for dependability, and attaching a file in Pine should be
just as reliable as transferring via FTP. Since the Internet message
infrastructure is not completely 7bit safe, this goal requires
encoding even 7bit files.
As you can see, we strongly disagree with the characterization that Pine
is broken at all in this regard, much less "severely" broken.
On Mon, 26 Feb 1996, Dale Scheetz wrote:
> The following is being sent to the Pine Bugs list and to the pine
> developers list in the hopes that they will have some satisfactory
> response to the discussion that follows
> On 19 Feb 1996, Kai Henningsen wrote:
> > firstname.lastname@example.org (Dale Scheetz) wrote on 18.02.96 in <Pine.LNX.3.91.960218141428.18651Bemail@example.com>:
> > > On Sat, 17 Feb 1996, Ian Jackson wrote:
> > > > MIME has been designed so that it is possible to attach plain text
> > > > files in ways that are readable to non-MIME-aware user agents.
> > >
> > > The proper way to do this in pine is NOT with MIME. Use ^R if you wish to
> > > include plain text in your message.
> > If pine does not *allow* non-encoded MIME multipart messages, then pine is
> > *severely* broken.
> > I'll not comment on anything more, because that would turn this message in
> > a severe flame.
> > MfG Kai
> ------------ --------------
> aka Dale Scheetz Phone: 1 (904) 877-0257
> Flexible Software Fax: NONE
> Black Creek Critters e-mail: firstname.lastname@example.org
> ------------ If you don't see what you want, just ask --------------