From: Simon Josefsson <jas@pdc.kth.se>
Subject: Re: attaching a tar files don't get it encoded
Date: 04 Dec 1999 17:35:06 +0100 [thread overview]
Message-ID: <ilu1z92y891.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: Simon Josefsson's message of "04 Dec 1999 17:00:10 +0100"
Simon Josefsson <jas@pdc.kth.se> writes:
> Attaching a tar file (not gzip:ed) as archive/tar doesn't seem to
> encode it with either base64 or QP, it's sent as binary data.
Sorry for following up on my own post, but I traced it and the problem
is because `find-charset-region' return 'ascii on the file contents
which make `mm-body-7-or-8' return '7bit, which make
`mm-encode-buffer' not encode the buffer at all. This last step is
wrong, becuase \0x00 is ascii (according to `find-charset-region') so
it makes Gnus send out ASCII 0 on the wire.
`mm-encode-buffer':
;; We force buffers that are 7bit to be unencoded, no matter
;; what the preferred encoding is.
(when (eq bits '7bit)
(setq encoding bits))
next prev parent reply other threads:[~1999-12-04 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-04 16:00 Simon Josefsson
1999-12-04 16:35 ` Simon Josefsson [this message]
1999-12-04 16:42 ` Shenghuo ZHU
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=ilu1z92y891.fsf@badis.pdc.kth.se \
--to=jas@pdc.kth.se \
/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).