Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.misc > #17740

email threading

From Ivan Shmakov <ivan@siamics.net>
Newsgroups comp.misc
Subject email threading
Date 2019-04-03 16:00 +0000
Organization Aioe.org NNTP Server
Message-ID <87o95nuli0.fsf_-_@violet.siamics.net> (permalink)
References (3 earlier) <q7m21r$re7$2@dont-email.me> <q7te7b$ni1$2@dont-email.me> <q7udtp$cq6$2@dont-email.me> <u5ddnf-0v5.ln1@rasp.therandymon.com> <q82g7q$9cj$2@dont-email.me>

Show all headers | View raw


>>>>> Rich <rich@example.invalid> writes:

[...]

 > Most 'business email' is not usenet like, it is more boss->slave(s)
 > or simply back and forth on the same subject for a while.  So Outhouse's
 > simple linear 'grouping' seems to work on, 98% of the time.

 > That, and 'threading' is actually easier on Usenet given that Usenet
 > clients actually enter a proper 'references' header pointing at
 > message ID's, so one does not have to parse and dissambiguate subject
 > lines with everyone's clients doing different prefixes for replies.

 > But, mutt shows it is possible, given enough desire to fix the issue,
 > with emails.  So MS certianly /could/ have fixed outhouse's threading.

	Email uses In-Reply-To: header in place of Usenet's References:,
	albeit that only holds the Message-ID: of the "parent" article.
	References: typically provides a short(ish) history of ancestors
	for a given message, but I don't think I've ever seen a newsreader
	that'd make use of anything but the last entry in the list.

	No parsing of human-readable Subject: prefixes is (thankfully)
	necessary for email threading.  (So long as the MUAs in question
	aren't broken in that regard, that is.)

-- 
FSF associate member #7257  http://am-1.org/~ivan/

Back to comp.misc | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

email and time to think RS Wood <rsw@therandymon.com> - 2019-03-28 11:31 -0400
  Re: email and time to think Huge <Huge@nowhere.much.invalid> - 2019-03-28 15:33 +0000
    Re: email and time to think Jerry Peters <jerry@example.invalid> - 2019-03-28 20:26 +0000
      Re: email and time to think RS Wood <rswood@therandymon.com> - 2019-03-28 21:27 -0400
        Re: email and time to think Mike Spencer <mds@bogus.nodomain.nowhere> - 2019-03-29 03:17 -0300
          Re: email and time to think Dan Purgert <dan@djph.net> - 2019-03-29 10:05 +0000
            Re: email and time to think Mike Spencer <mds@bogus.nodomain.nowhere> - 2019-03-29 16:46 -0300
              Re: email and time to think RS Wood <rsw@therandymon.com> - 2019-03-29 21:49 -0400
                Re: email and time to think Mike Spencer <mds@bogus.nodomain.nowhere> - 2019-03-31 17:27 -0300
          Re: email and time to think Jerry Peters <jerry@example.invalid> - 2019-03-29 20:20 +0000
          Re: email and time to think Rich <rich@example.invalid> - 2019-03-29 21:17 +0000
            Re: email and time to think scott@alfter.diespammersdie.us (Scott Alfter) - 2019-04-01 16:28 +0000
              Re: email and time to think Rich <rich@example.invalid> - 2019-04-02 01:29 +0000
                Re: email and time to think RS Wood <rsw@therandymon.com> - 2019-04-02 21:00 -0400
                Re: email and time to think Rich <rich@example.invalid> - 2019-04-03 14:33 +0000
                email threading Ivan Shmakov <ivan@siamics.net> - 2019-04-03 16:00 +0000
                Re: email threading Eli the Bearded <*@eli.users.panix.com> - 2019-04-03 16:59 +0000
                Re: email threading scott@alfter.diespammersdie.us (Scott Alfter) - 2019-04-05 16:26 +0000
                Re: email threading RS Wood <rsw@therandymon.com> - 2019-04-05 21:55 -0400
                Re: email threading Ivan Shmakov <ivan@siamics.net> - 2019-04-07 05:15 +0000
                Re: email threading Eli the Bearded <*@eli.users.panix.com> - 2019-04-08 01:30 +0000
                Re: email threading Pabst Blue Ribbon <pabst@blue.ribbon> - 2019-04-10 14:18 +0000
                Re: email threading Dmitry Alexandrov <321942@gmail.com> - 2019-04-11 04:12 +0300
        Re: email and time to think Rich <rich@example.invalid> - 2019-03-29 21:11 +0000
          Re: email and time to think Richard Kettlewell <invalid@invalid.invalid> - 2019-03-31 15:32 +0100
  Re: email and time to think Oregonian Haruspex <no_email@invalid.invalid> - 2019-03-29 06:36 +0000
  Re: email and time to think visiblink <visiblink@mail.invalid> - 2019-03-29 19:56 -0700
  Re: email and time to think Dostoevsky <dosdoevsky@protonmail.com> - 2019-03-29 23:35 -0500

csiph-web