The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: [TUHS] attachments: MIME and uuencode
Date: Tue, 14 Mar 2017 11:49:43 +0100	[thread overview]
Message-ID: <20170314104943.Zn7LG%steffen@sdaoden.eu> (raw)
In-Reply-To: <201703132214.v2DMEM8d032173@coolidge.cs.Dartmouth.EDU>

Doug McIlroy <doug at cs.dartmouth.edu> wrote:
 |>|Turning off the HTML text part takes a button click (or took once
 ||i looked last) 
 |
 |No offense taken, but there's no way to turn off the HTML part 
 |when that's the only part--and that is often the case.

It is the decision of the sending party what type of message is
produced, this i hope is still possible even for purely web-based
mail clients.  This sender-side decision i was referring to in the
post quoted above.  Unfortunately your observation is correct, but
luckily on this list, and also on most lists that i read!

But it seems many administrator tools only ever generate HTML or
other rich text log files and statistics, and so on request
generating mails to send these as the main body my MUA will
support in the future (even though very primitive yet, disallowing
additional signature injection, for example).  The world turns,
and integration progresses, and if you don't move you will be left
behind: this is not necessarily something bad.  E.g., on FreeBSD
many tools in the base system now use a XO (i think) library for
generating output, so that the output can be plain text, as
normal, but also JSON or XML, and maybe even binary CBOR at some
future time, and if there is a correct MIME type then why should
Mail not be a valid transport for this, that then can be correctly
decoded on the receiver side according to the MIME content type.
I for one very much prefer plain text in human interaction.

--steffen


  reply	other threads:[~2017-03-14 10:49 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 18:13 Doug McIlroy
2017-03-12 18:22 ` Larry McVoy
2017-03-12 18:26 ` Clem Cole
2017-03-13  0:34   ` Dan Cross
2017-03-13  1:28     ` Larry McVoy
2017-03-13  5:39       ` Dave Horsfall
2017-03-13 11:37   ` Steffen Nurpmeso
2017-03-13 20:21     ` Steffen Nurpmeso
2017-03-13 22:14       ` Doug McIlroy
2017-03-14 10:49         ` Steffen Nurpmeso [this message]
2017-03-12 18:33 ` Paul Winalski
2017-03-13  5:58   ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2017-03-12 20:04 Noel Chiappa
2017-03-12 21:34 ` Random832
2017-03-12 22:12   ` Noel Chiappa
2017-03-13 14:58     ` Michael Kjörling
2017-03-13 21:56       ` Dave Horsfall
2017-03-14 10:33         ` Steffen Nurpmeso
2017-03-16 18:52         ` Michael Kjörling
2017-03-12 18:57 Andy Valencia
2017-03-12 15:10 Noel Chiappa
2017-03-11 19:07 Mary Ann Horton
2017-03-11 23:01 ` Paul Winalski
2017-03-11 23:05   ` Mary Ann Horton
2017-03-12  1:14     ` Dan Cross
2017-03-12  6:28       ` jsteve
2017-03-12 23:41         ` Gregg Levine
2017-03-13  0:00           ` Larry McVoy
2017-03-13  1:59             ` Dave Horsfall
2017-03-12 23:43       ` Mary Ann Horton
2017-03-12 21:10   ` Dave Horsfall
     [not found]     ` <12de3888-3a82-4a8c-9177-50e6cb4cb931.maildroid@localhost>
2017-03-19  2:34       ` Dave Horsfall
2017-03-12 13:53 ` Tim Bradshaw
2017-03-12 17:42 ` Clem Cole
2017-03-12 23:35   ` Mary Ann Horton
2017-03-13  0:07     ` Clem Cole
2017-03-13  0:09     ` Warren Toomey
2017-03-13  0:11       ` Clem Cole

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=20170314104943.Zn7LG%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    /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).