From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] off-topic list
Date: Sat, 23 Jun 2018 12:49:36 -0600 [thread overview]
Message-ID: <ce6f617c-cf8e-63c6-8186-27e09c78020c@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20180623144959.M9byU%steffen@sdaoden.eu>
On 06/23/2018 08:49 AM, Steffen Nurpmeso wrote:
> Hello.
Hi,
> Oh, I do not know: i have never used a graphical MUA, only pine, then
> mutt, and now, while anytime before now and then anyway, BSD Mail.
I agree that text mode MUAs from before the turn of the century do have
a LOT more functionality than most GUI MUAs that came after that point
in time.
Thankfully we are free to use what ever MUA we want to. :-)
> they i think misinterpreted RFC 2231 to only allow MIME paramaters to be
> split in ten sections.
I've frequently found things that MUAs (and other applications) don't do
properly. That's when it becomes a learning game to see what subset of
the defined standard was implemented incorrectly and deciding if I want
to work around it or not.
> Graphical user interfaces are a difficult abstraction, or tedious to use.
> I have to use a graphical browser, and it is always terrible to enable
> Cookies for a site.
Cookies are their own problem as of late. All the "We use
cookies...<bla>...<bla>...<bla>...." warnings that we now seem to have
to accept get really annoying. I want a cookie, or more likely a
header, that says "I accept (first party) cookies." as a signal to not
pester me.
> For my thing i hope we will at some future day be so resilient that
> users can let go the nmh mailer without loosing any freedom.
Why do you have to let go of one tool? Why can't you use a suite of
tools that collectively do what you want?
> I mean, user interfaces are really a pain, and i think this will not
> go away until we come to that brain implant which i have no doubt will
> arrive some day, and then things may happen with a think. Things like
> emacs or Acme i can understand, and the latter is even Unix like in the
> way it works.
You can keep the brain implant. I have a desire to not have one.
> Interesting that most old a.k.a. established Unix people give up that
> Unix freedom of everything-is-a-file, that was there for email access via
> nupas -- the way i have seen it in Plan9 (i never ran a research Unix),
> at least -- in favour of a restrictive graphical user interface!
Why do you have to give up one tool to start using a different tool?
I personally use Thunderbird as my primary MUA but weekly use mutt
against the same mailbox w/ data going back 10+ years. I extensively
use Procmail to file messages into the proper folders. I recently wrote
a script that checks (copies of) messages that are being written to
folders to move a message with that Message-ID from the Inbox to the
Trash. (The point being to remove copies that I got via To: or CC: when
I get a copy from the mailing list.)
It seems to be like I'm doing things that are far beyond what
Thunderbird can do by leveraging other tools to do things for me. I
also have a handful devices checking the same mailbox.
> No, we use the same threading algorithm that Zawinski described ([1],
> "the threading algorithm that was used in Netscape Mail and News 2.0
> and 3.0"). I meant, in a threaded display, successive follow-up messages
> which belong to the same thread will not reiterate the Subject:, because
> it is the same one as before, and that is irritating.
>
> [1] http://www.jwz.org/doc/threading.html
I *LOVE* threaded views. I've been using threaded view for longer than
I can remember. I can't fathom not using threaded view.
I believe I mistook your statement to mean that you wanted to thread
based on Subject: header, not the In-Reply-To: or References: header.
>>> And you seem to be using DMARC, which irritates the list-reply mechanism
>>> of at least my MUA.
>>
>> Yes I do use DMARC as well as DKIM and SPF (w/ -all). I don't see how
>> me using that causes problems with "list-reply".
>>
>> My working understanding is that "list-reply" should reply to the list's
>> posting address in the List-Post: header.
>>
>> List-Post: <mailto:tuhs@minnie.tuhs.org>
>>
>> What am I missing or not understanding?
>
> That is not how it works for the MUAs i know. It is an interesting idea.
> And in fact it is used during the "mailing-list address-massage"
> if possible. But one must or should differentiate in between a
> subscribed list and a non-subscribed list, for example. This does
> not work without additional configuration (e.g., we have `mlist' and
> `mlsubscribe' commands to make known mailing-lists to the machine),
> though List-Post: we use for automatic configuration (as via `mlist').
>
> And all in all this is a complicated topic (there are Mail-Followup-To:
> and Reply-To:, for example), and before you say "But what i want is a
> list reply!", yes, of course you are right. But. For my thing i hope
> i have found a sensible way through this, and initially also one that
> does not deter users of console MUA number one (mutt).
How does my use of DMARC irritate the list-reply mechanism of your MUA?
DMARC is completely transparent to message contents. Sure, DKIM adds
headers with a signature. But I don't see anything about DKIM's use
that has any impact on how any MUA handles a message.
Or are you referring to the fact that some mailing lists modify the
From: header to be DMARC compliant?
Please elaborate on what you mean by "DMARC irritate the list-reply
mechanism of your MUA".
--
Grant. . . .
unix || die
next prev parent reply other threads:[~2018-06-23 18:49 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 22:44 [TUHS] core Nelson H. F. Beebe
2018-06-21 23:07 ` Grant Taylor via TUHS
2018-06-21 23:38 ` Toby Thain
2018-06-21 23:47 ` [TUHS] off-topic list Warren Toomey
2018-06-22 1:11 ` Grant Taylor via TUHS
2018-06-22 3:53 ` Robert Brockway
2018-06-22 4:18 ` Dave Horsfall
2018-06-22 11:44 ` Arthur Krewat
2018-06-22 14:28 ` Larry McVoy
2018-06-22 14:46 ` Tim Bradshaw
2018-06-22 14:54 ` Larry McVoy
2018-06-22 15:17 ` Steffen Nurpmeso
2018-06-22 17:27 ` Grant Taylor via TUHS
2018-06-22 19:25 ` Steffen Nurpmeso
2018-06-22 21:04 ` Grant Taylor via TUHS
2018-06-23 14:49 ` Steffen Nurpmeso
2018-06-23 15:25 ` Toby Thain
2018-06-23 18:49 ` Grant Taylor via TUHS [this message]
2018-06-23 21:05 ` Tom Ivar Helbekkmo via TUHS
2018-06-23 21:21 ` Michael Parson
2018-06-23 23:31 ` Grant Taylor via TUHS
2018-06-23 23:36 ` Larry McVoy
2018-06-23 23:37 ` Larry McVoy
2018-06-24 0:20 ` Grant Taylor via TUHS
2018-06-25 2:53 ` Dave Horsfall
2018-06-25 5:40 ` Grant Taylor via TUHS
2018-06-25 6:15 ` arnold
2018-06-25 7:27 ` Bakul Shah
2018-06-25 12:52 ` Michael Parson
2018-06-25 13:41 ` arnold
2018-06-25 13:56 ` arnold
2018-06-25 13:59 ` Adam Sampson
2018-06-25 15:05 ` Grant Taylor via TUHS
2018-06-26 9:05 ` Derek Fawcus
2018-06-28 14:25 ` [TUHS] email filtering (was Re: off-topic list) Perry E. Metzger
2018-06-23 22:38 ` [TUHS] off-topic list Steffen Nurpmeso
2018-06-24 0:18 ` Grant Taylor via TUHS
2018-06-24 10:04 ` Michael Kjörling
2018-06-25 16:10 ` Steffen Nurpmeso
2018-06-25 18:48 ` Grant Taylor via TUHS
2018-06-25 0:43 ` [TUHS] mail (Re: " Bakul Shah
2018-06-25 1:15 ` Lyndon Nerenberg
2018-06-25 2:44 ` George Michaelson
2018-06-25 3:04 ` Larry McVoy
2018-06-25 3:15 ` Bakul Shah
2018-06-25 16:26 ` Steffen Nurpmeso
2018-06-25 18:59 ` Grant Taylor via TUHS
2018-06-25 14:18 ` [TUHS] " Clem Cole
2018-06-25 15:28 ` [TUHS] off-topic list [ really mh ] Jon Steinhart
2018-06-26 7:49 ` Ralph Corderoy
2018-06-25 15:51 ` [TUHS] off-topic list Steffen Nurpmeso
2018-06-25 18:21 ` Grant Taylor via TUHS
2018-06-26 20:38 ` Steffen Nurpmeso
2018-06-22 16:07 ` Tim Bradshaw
2018-06-22 16:36 ` Steve Johnson
2018-06-22 20:55 ` Bakul Shah
2018-06-22 14:52 ` Ralph Corderoy
2018-06-22 15:13 ` SPC
2018-06-22 16:45 ` Larry McVoy
2018-06-22 15:28 ` Clem Cole
2018-06-22 17:17 ` Grant Taylor via TUHS
2018-06-22 18:00 ` Dan Cross
2018-06-22 17:29 ` Cág
2018-06-22 2:21 Noel Chiappa
2018-06-22 22:23 Doug McIlroy
2018-06-22 23:20 ` John P. Linderman
2018-06-23 0:22 ` Warren Toomey
2018-06-24 3:08 Norman Wilson
2018-06-24 13:14 Noel Chiappa
2018-06-25 1:38 ` Dave Horsfall
2018-06-25 1:46 ` Grant Taylor via TUHS
2018-06-25 16:44 ` Steffen Nurpmeso
2018-06-25 12:45 ` Tony Finch
2018-06-25 16:41 ` Steffen Nurpmeso
2018-06-25 14:44 Noel Chiappa
2018-06-25 15:44 ` Clem Cole
2018-06-25 16:03 ` Paul Winalski
2018-06-25 17:22 ` Clem Cole
2018-06-25 16:10 Noel Chiappa
2018-06-25 17:37 ` Clem Cole
2018-06-25 19:35 ` Grant Taylor via TUHS
2018-06-25 20:09 ` Clem Cole
2018-06-25 20:47 ` Grant Taylor via TUHS
2018-06-25 21:15 ` Clem Cole
2018-06-26 7:01 ` arnold
2018-06-26 8:57 ` Derek Fawcus
2018-06-26 11:29 ` Tim Bradshaw
2018-06-26 13:09 ` Tony Finch
2018-06-26 18:04 ` Warner Losh
2018-06-26 21:16 ` Clem Cole
2018-06-27 21:33 ` Michael Parson
2018-06-27 22:27 ` Clem cole
2018-06-28 5:57 ` arnold
2018-06-28 18:36 ` Michael Parson
2018-06-26 15:57 ` Michael Kjörling
2018-06-26 21:09 ` Steffen Nurpmeso
2018-06-26 21:18 ` Clem Cole
2018-06-26 23:45 ` George Michaelson
2018-06-25 20:15 ` Lyndon Nerenberg
2018-06-26 8:27 ` Tony Finch
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=ce6f617c-cf8e-63c6-8186-27e09c78020c@spamtrap.tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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).