From: Roman Belenov <roman@nstl.nnov.ru>
Subject: 8-bit again
Date: Wed, 02 Aug 2000 22:43:20 +0400 [thread overview]
Message-ID: <u7l9zld13.fsf@nstl.nnov.ru> (raw)
I tried to check the situation my self; the interesting thing is that
when I send mail to myself, Gcc:'d copy in archive folder comes in
MIME (base64 or quoted-printable) while incoming letter (in nnml
spool) is in 8-bit. So the question is - can the body encoding of
letters in archive be different from one in outgoing messages ? If so,
it seems that everything works fine and I was just overcautious.
--
With regards, Roman.
next reply other threads:[~2000-08-02 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 18:43 Roman Belenov [this message]
2000-08-03 7:49 ` Kai Großjohann
2000-08-03 8:31 ` Roman Belenov
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=u7l9zld13.fsf@nstl.nnov.ru \
--to=roman@nstl.nnov.ru \
/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).