From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: MIME stuff
Date: 19 Feb 1999 17:06:40 +0100 [thread overview]
Message-ID: <m3yalupecv.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Bruce Stephens's message of "15 Feb 1999 19:03:08 +0000"
Bruce Stephens <bruce@cenderis.demon.co.uk> writes:
> How do I set things up so that message/external-body works sensibly?
Oh; that hasn't been implemented at all yet. :-)
> Also, when I edited the message and saved it again (and the MIME->MML
> and MML->MIME stuff is very cool, BTW), everything worked OK except
> that the bodypart of the message/external-body (containing the
> Content-type and Content-ID) was base64 encoded, which is specifically
> disallowed by rfc2046, so I suspect a bug in the MML processing, or at
> least a poor default (by default, it ought to produce 7bit, even
> though I can't imagine MUAs failing to cope with base64 in this
> context).
Sounds like a bug, but I think it should wait until we actually
support message/external-body.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-02-19 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-15 19:03 Bruce Stephens
1999-02-16 3:59 ` Hrvoje Niksic
1999-02-16 19:37 ` Bruce Stephens
1999-02-19 16:06 ` Lars Magne Ingebrigtsen [this message]
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=m3yalupecv.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).