From: Bruce Stephens <bruce@cenderis.demon.co.uk>
Subject: Re: forwarded mail problems
Date: 18 Jun 1999 21:14:22 +0100 [thread overview]
Message-ID: <m3vhclmfkx.fsf@cenderis.demon.co.uk> (raw)
In-Reply-To: Wes Hardaker's message of "18 Jun 1999 12:18:20 -0700"
Wes Hardaker <wjhardaker@ucdavis.edu> writes:
> So, uh, ??? Should the encoding be different for outgoing
> message/rfc822 messages?
This hasn't changed for a while, I think. Try looking at the variable
mm-content-transfer-encoding-defaults, and changing that. I think
it's a misfeature, however---I think Gnus ought to look, and if the
enclosed things are 7bit, then it ought to use that (and otherwise, I
suspect base64 would be safer, although possibly not more readable to
people without MIME MUAs).
next prev parent reply other threads:[~1999-06-18 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-18 19:18 Wes Hardaker
1999-06-18 19:26 ` Colin Rafferty
1999-06-18 20:14 ` Bruce Stephens [this message]
1999-06-21 15:56 ` Wes Hardaker
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=m3vhclmfkx.fsf@cenderis.demon.co.uk \
--to=bruce@cenderis.demon.co.uk \
/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).