The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] attachments: MIME and uuencode
Date: Thu, 16 Mar 2017 18:52:52 +0000	[thread overview]
Message-ID: <20170316185252.GF21831@yeono.kjorling.se> (raw)
In-Reply-To: <alpine.BSF.2.20.1703140853440.794@aneurin.horsfall.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]

On 14 Mar 2017 08:56 +1100, from dave at horsfall.org (Dave Horsfall):
>> I can live with multipart/alternative { text/plain, text/html } messages 
>> where the plain text part is actually _meaningful_ (my MUA is set up to 
>> do nothing with text/html unless I ask it, at which point they are fed 
>> through 'lynx -dump' plus a few other parameters), but have been known 
>> to shoot back HTML-_only_ messages to the originator. Usually with a 
>> comment to the effect of "this looks like it came through garbled". I'm 
>> still waiting for the first such recipient to obviously take the hint, 
>> but I haven't yet given up hope.
> 
> Procmail?  I'd like to have that script :-)

Sorry, no automation, but it'd probably be possible to cobble
something together using procmail and formail. Just "unauto_view *"
and "alternative_order text/plain text/html text" plus hitting "reply"
in Mutt and coming up with something bearing a not too close
resemblance to insults. The exact wording tends to vary with how
annoyed I am at the particular sender at the moment.

-- 
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
                 “People who think they know everything really annoy
                 those of us who know we don’t.” (Bjarne Stroustrup)


  parent reply	other threads:[~2017-03-16 18:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-12 18:57 Andy Valencia
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
2017-03-12 18:33 ` Paul Winalski
2017-03-13  5:58   ` Dave Horsfall
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=20170316185252.GF21831@yeono.kjorling.se \
    --to=michael@kjorling.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).