From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Why is Gnus decompressing my attachment?
Date: Fri, 30 Sep 2011 11:43:39 +0900 [thread overview]
Message-ID: <b4mwrcqsqas.fsf@jpl.org> (raw)
In-Reply-To: <m2ty7v883p.fsf@pluto.luannocracy.com>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
Dave Abrahams wrote:
> I'm not sure why sending is failing either ... but the big mystery here
> is why Gnus/message would decompress the archive.
> Sending...
> XZ uncompressing /tmp/YAC2011.mov.xz...done
> Sending via mail...
> message-send-mail-with-sendmail: Sending...failed with exit value 75
Hm, I don't know why it failed. But decompression should not be
to blame. Decompressed data are never passed to m-s-m-w-sendmail.
Decompression is done for only determining the charset of
a compressed part; the charset is added to the Content-Type header
of a part if successfully detected. This is mainly for Gnus users'
convenience. Try viewing the part attached to this message using
the `i' command.
(A Japanese text will be displayed in a human-readable way in spite
of the part that is charset-encoded and compressed. This is
convenient when viewing a compressed patch file that contains
non-ASCII text and is sent as an application/octet-stream part,
for example. Currently only tar archives are excluded from
detecting charset.)
You may want to try another approach. Good luck.
[-- Attachment #2: Japanese.txt.gz --]
[-- Type: application/octet-stream, Size: 81 bytes --]
next prev parent reply other threads:[~2011-09-30 2:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 19:24 Dave Abrahams
2011-09-30 1:43 ` XeCycle
2011-09-30 2:43 ` Katsumi Yamaoka [this message]
2011-09-30 15:46 ` Dave Abrahams
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=b4mwrcqsqas.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
/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).