From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: Any chance of getting gnus to handle mime attachments?
Date: Wed, 08 Jun 2005 12:47:28 -0400 [thread overview]
Message-ID: <vxkvf4o94nz.fsf@mesquite.charcoal.com> (raw)
In-Reply-To: <wrxmzq0q15m.fsf@rodney.unidata.ucar.edu>
Ed Hartnett <ed@unidata.ucar.edu> writes:
> Here's the headers. Seems like there is a Mime-Version and a
> Content-Type.
> Any help would be appreciated.
The boundary is mismatched; no wonder Gnus can't parse it.
> Mime-Version: 1.0
> Content-Type: multipart/mixed; boundary="----- Forwarded Message"
> ------=_NextPart_RTV6YGPT0A6RG9PMMD0TK2F2
No "Forwarded Message" appears.
next prev parent reply other threads:[~2005-06-08 16:47 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 [this message]
2005-06-08 17:02 ` Ed Hartnett
2005-06-08 17:47 ` Karl Kleinpaste
2005-06-08 18:37 ` Ed Hartnett
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=vxkvf4o94nz.fsf@mesquite.charcoal.com \
--to=karl@charcoal.com \
--cc=karl+usenet@charcoal.com \
/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).