From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] please ignore this message
Date: Fri, 29 Jun 2018 14:54:12 +0200 [thread overview]
Message-ID: <20180629125412.Lv7iZ%steffen@sdaoden.eu> (raw)
In-Reply-To: <CAC0cEp-p2cnhXd37msaRCazMacNXHnM3CEe98vSvzUw2cpd9cw@mail.gmail.com>
John P. Linderman wrote in <CAC0cEp-p2cnhXd37msaRCazMacNXHnM3CEe98vSvzUw\
2cpd9cw@mail.gmail.com>:
|With gmail, both attachments showed just (constant-width) single-line \
|names of the attachments, "junk.txt" and "junk.diff" (without the quotes).
|
|On Thu, Jun 28, 2018 at 6:19 PM, Doug McIlroy <[1]doug@cs.dartmouth.edu[\
|/1]> wrote:
|
| [1] mailto:doug@cs.dartmouth.edu
|
||This tests a guess about anomalous behavior of the
||mailing-list digest. I apologize for inflicting it
||on everybody.
|
||Doug
Both attachments where declared as text/plain, only the filename
differed. This is possibly not what Doug McIlroy wanted to test.
Mr. Doug McIlroy, in order to convince your version of Heirloom
mailx to create the correct MIME type for .diff files you need to
provide a mime.types(5) file, as in
echo 'text/x-diff diff patch' >> ~/.mime.types
It will also find this in /etc/mime.types.
(And i think there may also be a difference in the TUHS mailman
instance or configuration, as opposed to the GNU managed one that
drives the groff list. I suppose you referred to the problem of
the groff digest you are reading.)
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2018-06-29 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 22:19 Doug McIlroy
2018-06-29 1:32 ` John P. Linderman
2018-06-29 12:54 ` Steffen Nurpmeso [this message]
2018-06-29 13:00 ` Ralph Corderoy
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=20180629125412.Lv7iZ%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=doug@cs.dartmouth.edu \
--cc=tuhs@tuhs.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).