From: Matt Simmons <simmonmt@acm.org>
Subject: Re: Inline problems with 0.31?
Date: 23 Sep 1998 22:30:06 -700 [thread overview]
Message-ID: <yfqu31y3wo1.fsf@acm.org> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "19 Sep 1998 14:16:40 +0200"
I'm now using 0.32. MIME attachments aren't showing up at all. When
I view the message in [1], I see the raw mime headers and separators.
The attachment bodies are shown in encoded form (base64 for the
referenced message).
This occurs even when I move both mailcaps out of the way.
Matt
Footnotes:
[1] <m2btqf4s35.fsf@altair.xemacs.org> from xemacs-beta
--
Matt Simmons - simmonmt@acm.org - http://www.netcom.com/~simmonmt
Anyone with money to burn will always find himself surrounded by people
with matches. --Joe Ryan
next prev parent reply other threads:[~1998-09-24 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-16 8:32 Matt Simmons
1998-09-16 10:05 ` Lars Magne Ingebrigtsen
1998-09-16 18:17 ` Matt Simmons
1998-09-19 12:16 ` Lars Magne Ingebrigtsen
1998-09-24 5:30 ` Matt Simmons [this message]
1998-09-24 5:46 ` Shenghuo ZHU
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=yfqu31y3wo1.fsf@acm.org \
--to=simmonmt@acm.org \
/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).