From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: bug in mime composition
Date: 15 Nov 1998 12:22:14 +0300 [thread overview]
Message-ID: <m3n25ttint.fsf@vvv.vsu.ru> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
Content-Type: multipart/mixed; boundary="==-=-="
--==-=-=
Hi,
sorry if it's too early to report these bugs :-) but here is a message
which is sent incorrectly encoded. The next message shows what was in
by mail buffer when i was pressing C-c C-c.
--==-=-=
Content-Type: application/x-dvi
Content-Transfer-Encoding: base64
÷\x02\x01À\x1c;
,a\v"5ý-:º*\x0fLܹtest¡\v"5ý-:º3\x0fLܹthird\x1e
test again
Best regards, -- Vladimir.
--==-=-=--
reply other threads:[~1998-11-15 9:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3n25ttint.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.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).