From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: no RFC-2047 in sent mail
Date: 09 May 2000 09:12:52 -0400 [thread overview]
Message-ID: <2n8zxj98a3.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Steinar Bang's message of "09 May 2000 11:24:22 +0200"
>>>>> "Steinar" == Steinar Bang <sb@metis.no> writes:
Steinar> My CVS checkout from the time Shenghuo fixed the
Steinar> message/rfc822 forward does not encode outgoing email
Steinar> messages according to RFC-2047 it seems.
Steinar> Will a fresh update fix this, I wonder?
If the version number of your copy is 5.8.5, there are many changes
about rfc 2047. If the problem you mentioned has not been fixed, tell
me how to reproduce it.
Shenghuo
prev parent reply other threads:[~2000-05-09 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-09 9:24 Steinar Bang
2000-05-09 13:12 ` Shenghuo ZHU [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=2n8zxj98a3.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).