Re: questions on QP, non-text attachments and munpack

John Gardiner Myers <jgm+@cmu.edu> Tue, 13 February 1996 22:46 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00842; 13 Feb 96 17:46 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00836; 13 Feb 96 17:46 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa16411; 13 Feb 96 17:46 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id RAA01834; Tue, 13 Feb 1996 17:14:35 -0500
Received: from po10.andrew.cmu.edu (PO10.ANDREW.CMU.EDU [128.2.10.110]) by list.cren.net (8.6.12/8.6.12) with ESMTP id RAA01816 for <ietf-822@list.cren.net>; Tue, 13 Feb 1996 17:14:12 -0500
Received: (from postman@localhost) by po10.andrew.cmu.edu (8.7.3/8.7.1) id RAA00943 for ietf-822@list.cren.net; Tue, 13 Feb 1996 17:14:10 -0500
Received: via switchmail; Tue, 13 Feb 1996 17:14:10 -0500 (EST)
Received: from hogtown.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/testq0/QF.ol8EnGm00WBw00ZV51>; Tue, 13 Feb 1996 17:12:35 -0500 (EST)
Received: from hogtown.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/usr7/jgm/.Outgoing/QF.gl8EnFe00WBwQ12HlC>; Tue, 13 Feb 1996 17:12:33 -0500 (EST)
Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Tue, 13 Feb 1996 17:12:30 -0500 (EST)
Message-Id: <sl8EnCu00WBwA12HZR@andrew.cmu.edu>
Date: Tue, 13 Feb 1996 17:12:30 -0500 (EST)
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John Gardiner Myers <jgm+@cmu.edu>
To: ietf-822@list.cren.net
Subject: Re: questions on QP, non-text attachments and munpack
In-Reply-To: <9602131801.AA02473@ig4.att.att.com>
References: <9602131801.AA02473@ig4.att.att.com>
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN

hansen@pegasus.att.com writes:
> But munpack uses a different heuristic for base64 encoding: it appears to
> check to see if the content type is text and passes a flag to the base64
> decoder that says whether or not CR's should be suppressed. This heuristic
> works well.

That is because the heuristic is to use the choice of quoted-printable
vs. base64 to intuit whether or not the object is textual.  Few
textual non-text/* objects are encoded in base64.  All text/* objects
are by the spec textual.

-- 
_.John G. Myers		Internet: jgm+@CMU.EDU
			LoseNet:  ...!seismo!ihnp4!wiscvm.wisc.edu!give!up