From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/5196
Path: news.gmane.org!not-for-mail
From: Karl Kleinpaste <karl@charcoal.com>
Newsgroups: gmane.emacs.gnus.user
Subject: Re: Any chance of getting gnus to handle mime attachments?
Date: Wed, 08 Jun 2005 13:47:50 -0400
Organization: Charcoal
Message-ID: <vxkis0o91vd.fsf@mesquite.charcoal.com>
References: <wrxslztezad.fsf@rodney.unidata.ucar.edu>
	<vxk4qc8ap45.fsf@mesquite.charcoal.com>
	<wrxu0k8q3w9.fsf@rodney.unidata.ucar.edu>
	<vxkzmu097cu.fsf@mesquite.charcoal.com>
	<wrxmzq0q15m.fsf@rodney.unidata.ucar.edu>
	<vxkvf4o94nz.fsf@mesquite.charcoal.com>
	<wrxhdg8pys4.fsf@rodney.unidata.ucar.edu>
Reply-To: karl+usenet@charcoal.com
NNTP-Posting-Host: main.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: sea.gmane.org 1138670975 26450 80.91.229.2 (31 Jan 2006 01:29:35 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Tue, 31 Jan 2006 01:29:35 +0000 (UTC)
Keywords: message,mime,gnus,boundary,content
Original-X-From: nobody Tue Jan 17 17:34:55 2006
Original-Path: quimby.gnus.org!newsfeed.gazeta.pl!fu-berlin.de!logbridge.uoregon.edu!usenet01.sei.cmu.edu!nn.andrew.cmu.edu!newsfeeder.srv.cs.cmu.edu!wolfberry.srv.cs.cmu.edu!news.charcoal.com!not-for-mail
Original-Newsgroups: gnu.emacs.gnus
Original-NNTP-Posting-Host: betelnut.srv.cs.cmu.edu
Original-X-Trace: wolfberry.srv.cs.cmu.edu 1118253006 8468 128.2.206.166 (8 Jun 2005 17:50:06 GMT)
Original-X-Complaints-To: abuse@cs.cmu.edu
Original-NNTP-Posting-Date: Wed, 8 Jun 2005 17:50:06 +0000 (UTC)
X-Face: ?=p^Gj2JkX~UU_@W}[q/'Dxn19x-zfIQ](y<&ky/?1-&Nz&,!W}R.Gp+"LeGojoR
	=RF>?!XVs{a:`Yt(gqM<#$Zy(C@]'dR4Hy4S1.I(n3:2"R:=Uy!)K9>U!gNTyH{p
	+_w#F[gt).$Vyvo5=9LF^PeQ(@H#}QLAbfyYxX/8t:TDR5nA\|RmJO"EwjL8tWyvM
User-Agent: Gnus/5.110004 (No Gnus v0.4) XEmacs/21.5-b20 (linux)
Cancel-Lock: sha1:xEMYWFTyccn0WsmsutQZrk7sJT8=
Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:5338
Original-Lines: 23
X-Gnus-Article-Number: 5338   Tue Jan 17 17:34:55 2006
Xref: news.gmane.org gmane.emacs.gnus.user:5196
Archived-At: <http://permalink.gmane.org/gmane.emacs.gnus.user/5196>

Ed Hartnett <ed@unidata.ucar.edu> writes:
> Could you please elaborate?
> What is the boundary supposed to look like?

In the header, Content-Type provides the boundary between message
parts.  That string must appear exactly in the next part.  Your sample
message claims a Content-Type boundary string which is unrelated to
the boundary strings actually in the body.

This is a prime example of Gnus' overachieving in MIME; Gnus actually
obeys the spec.  If a message has been generated by a buggy origin
agent, tough: Gnus will deal with it on its merits.  Gnus will not
guess at what might appear, to fuzzy human thinking, to be a proper
MIME indicator.  (For example, older Netscape mail would intuit
MIMEness in the absence of MIME-Version -- grotesquely wrong behavior.)

At a guess, the sender's mailer botched the recursive MIMEness of a
forwarded message which in turn had its own MIME content.  "Oops."
Many mailers have a broken concept of "forwarding" in which they
neglect to include _all_ the headers necessary to preserve the
message's MIME content descriptors and indicate their own content.

Tell the sender to get a real mailer.  One that doesn't generate garbage.