* mm-encode doesn't know message/rfc822, and base64's them
@ 1998-12-07 21:30 Karl Kleinpaste
1998-12-07 22:20 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 2+ messages in thread
From: Karl Kleinpaste @ 1998-12-07 21:30 UTC (permalink / raw)
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. How do we get more types into the available set? A quick
look through mailcap.el didn't seem to tell me what I wanted to know,
because there are a lot of types there which don't show up in
*Completions* when I try to TAB-complete at the `C-c C-a' prompt.
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:
1998-12-07 Karl Kleinpaste <karl@justresearch.com>
* mm-encode.el (mm-content-transfer-encoding-defaults): Add an
entry for message/rfc822 as 8bit.
--- mm-encode.el.~1~ Mon Dec 7 16:10:26 1998
+++ mm-encode.el Mon Dec 7 16:10:46 1998
@@ -29,6 +29,7 @@
(defvar mm-content-transfer-encoding-defaults
'(("text/.*" quoted-printable)
+ ("message/rfc822" 8bit)
("application/emacs-lisp" 8bit)
(".*" base64))
"Alist of regexps that match MIME types and their encodings.")
But I suspect that something much more general is really in order
here. And I don't know whether 8bit is appropriate, or if perhaps
quoted-printable is what really ought to be used.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: mm-encode doesn't know message/rfc822, and base64's them
1998-12-07 21:30 mm-encode doesn't know message/rfc822, and base64's them Karl Kleinpaste
@ 1998-12-07 22:20 ` Lars Magne Ingebrigtsen
0 siblings, 0 replies; 2+ messages in thread
From: Lars Magne Ingebrigtsen @ 1998-12-07 22:20 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1998-12-07 22:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-12-07 21:30 mm-encode doesn't know message/rfc822, and base64's them Karl Kleinpaste
1998-12-07 22:20 ` Lars Magne Ingebrigtsen
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).