The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: Mangled and non-mangled TUHS mail lists
Date: Tue, 3 Oct 2017 15:59:46 -0600	[thread overview]
Message-ID: <d9a04642-b035-8369-2415-423fd33f177a@tnetconsulting.net> (raw)
In-Reply-To: <20171003184345.rout343iwjwc57e4@matica.foolinux.mooo.com>

On 10/03/2017 12:43 PM, Ian Zimmerman wrote:
> It's a valid viewpoint, but one of its consequences is that there is no
> straight way of relating multiple copies of the original message.  Not
> only in the somewhat shady case of personal reply+list followup, but
> also in the quite legitimate case of posting the same message to
> multiple lists.

You bring up a valid point.  Something I've not specifically thought 
about before, mainly because I've not wanted to maintain a MLM.

> A related situation is list managers that act as 2-way gateways from/to
> Usenet groups.  Mailman can do that, and when it does it rewrites the
> Message-ID.  The result is that all threads with mixed participants
> (posting both via Unsenet and via email) are broken.

I see no reason that the hypothetical MLM that I'm alluding to couldn't 
re-use the message ID or at least cite it in the References: header 
rather than making something arbitrary up.

I think that would help with the problem that you're describing.

> This is why I stopped reading the core GNU lists (help-gnu-emacs et al.)
> when they adopted Mailman.

I'm sorry.  That makes me believe that the list has failed in it's 
purpose of enabling communications.  :-(



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3717 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171003/78736c5f/attachment.bin>


  reply	other threads:[~2017-10-03 21:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01  3:25 Warren Toomey
2017-10-01 14:00 ` Clem Cole
2017-10-01 14:08   ` Don Hopkins
2017-10-02  1:01 ` Dave Horsfall
2017-10-02  8:22   ` jason-tuhs
2017-10-02 12:38     ` Steve Nickolas
2017-10-02 13:34       ` David Ryskalczyk
2017-10-03  0:51         ` Dave Horsfall
2017-10-03  2:19           ` Steve Nickolas
2017-10-03  3:25             ` Grant Taylor
2017-10-03  3:33               ` Dave Horsfall
2017-10-03  3:55                 ` Grant Taylor
2017-10-03  4:17                   ` Dave Horsfall
2017-10-03  4:12                 ` Kurt H Maier
2017-10-03  7:40                   ` Ian Zimmerman
2017-10-03 14:08                 ` Steffen Nurpmeso
2017-10-03 18:20                   ` Grant Taylor
2017-10-03 18:43                     ` Ian Zimmerman
2017-10-03 21:59                       ` Grant Taylor [this message]
2017-10-03 18:49                     ` Steffen Nurpmeso
2017-10-03 21:54                       ` Grant Taylor
2017-10-03 22:00                         ` Mangled and non-mangled TUHS mail lists [ enough already? ] Jon Steinhart
2017-10-04 20:17                         ` Mangled and non-mangled TUHS mail lists Steffen Nurpmeso
2017-10-04  2:28                       ` Dave Horsfall
2017-10-04 20:59                         ` Steffen Nurpmeso
2017-10-03 10:12               ` Steve Nickolas
2017-10-03 19:21                 ` Bakul Shah

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=d9a04642-b035-8369-2415-423fd33f177a@tnetconsulting.net \
    --to=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).