From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/5197 Path: news.gmane.org!not-for-mail From: Ed Hartnett Newsgroups: gmane.emacs.gnus.user Subject: Re: Any chance of getting gnus to handle mime attachments? Date: Wed, 08 Jun 2005 12:37:16 -0600 Organization: National Center for Atmospheric Research Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138670976 26456 80.91.229.2 (31 Jan 2006 01:29:36 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:29:36 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:34:55 2006 Original-Path: quimby.gnus.org!news.ccs.neu.edu!news.dfci.harvard.edu!news.cis.ohio-state.edu!usenet01.sei.cmu.edu!hammer.uoregon.edu!canoe.uoregon.edu!frgp!ucar!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: rodney.unidata.ucar.edu Original-X-Trace: news.ucar.edu 1118255837 32708 128.117.140.88 (8 Jun 2005 18:37:17 GMT) Original-X-Complaints-To: news@news.ucar.edu Original-NNTP-Posting-Date: Wed, 8 Jun 2005 18:37:17 +0000 (UTC) User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.4 (gnu/linux) Cancel-Lock: sha1:uiu74HYc43m7BIqjJK4t8J7iR0c= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:5339 Original-Lines: 40 X-Gnus-Article-Number: 5339 Tue Jan 17 17:34:55 2006 Xref: news.gmane.org gmane.emacs.gnus.user:5197 Archived-At: Karl Kleinpaste writes: > Ed Hartnett 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. Is there a way for me to edit the message to put the correct separator in a get GNUS to understanding? Reforming the mailers of all people who send me support emails is a *little* bit beyond my job description. Thanks, Ed -- Ed Hartnett -- ed@unidata.ucar.edu