From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: mm-encode doesn't know message/rfc822, and base64's them
Date: 07 Dec 1998 23:20:46 +0100 [thread overview]
Message-ID: <m3soeriog1.fsf@sparky.gnus.org> (raw)
In-Reply-To: Karl Kleinpaste's message of "07 Dec 1998 16:30:59 -0500"
Karl Kleinpaste <karl@justresearch.com> writes:
> I wanted to send a message containing a message/rfc822 pulled from my
> own archives, but `C-c C-a' didn't understand "message/rfc822" as a
> valid type.
Well, you can type in anything you want as the type -- no match is
required.
> I can stuff in a message as text/plain initially, and then manually
> change it to message/rfc822 in the "part" spec. But then mm-encode.el
> wants to base64-encode it, because the CTE defaults aren't terribly
> specific. I did this to mm-encode.el:
Thanks for the patch; I've applied it to Pterodactyl Gnus v0.66.
(But I changed it to qp instead.)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-12-07 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-07 21:30 Karl Kleinpaste
1998-12-07 22:20 ` 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=m3soeriog1.fsf@sparky.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).