From: Ed Hartnett <ed@unidata.ucar.edu>
Subject: Re: Any chance of getting gnus to handle mime attachments?
Date: Wed, 08 Jun 2005 12:37:16 -0600 [thread overview]
Message-ID: <wrx4qc8pueb.fsf@rodney.unidata.ucar.edu> (raw)
In-Reply-To: <vxkis0o91vd.fsf@mesquite.charcoal.com>
Karl Kleinpaste <karl@charcoal.com> writes:
> 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.
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
next prev parent reply other threads:[~2005-06-08 18:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 13:47 Ed Hartnett
2005-06-08 14:05 ` David Kastrup
2005-06-08 14:40 ` Karl Kleinpaste
2005-06-08 15:12 ` Ed Hartnett
2005-06-08 15:49 ` Karl Kleinpaste
2005-06-08 16:11 ` Ed Hartnett
2005-06-08 16:47 ` Karl Kleinpaste
2005-06-08 17:02 ` Ed Hartnett
2005-06-08 17:47 ` Karl Kleinpaste
2005-06-08 18:37 ` Ed Hartnett [this message]
2005-06-08 19:27 ` Karl Kleinpaste
2005-06-08 21:26 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wrx4qc8pueb.fsf@rodney.unidata.ucar.edu \
--to=ed@unidata.ucar.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).