Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!newsfeed.kamp.net!newsfeed.kamp.net!fu-berlin.de!uni-berlin.de!not-for-mail
From: Mark Sapiro <mark@msapiro.net>
Newsgroups: comp.lang.python
Subject: Re: Threading is foobared?
Date: Wed, 30 Mar 2016 21:50:54 -0700
Organization: Not Very Much
Lines: 81
Message-ID: <mailman.232.1459401129.28225.python-list@python.org>
References: <56F7B5FA.4040002@timgolden.me.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OqWEt8su6EUNtoGiBGWpGPn8Xc1xI6vnJ"
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
In-Reply-To: <56F7B5FA.4040002@timgolden.me.uk>
Precedence: list
Xref: csiph.com comp.lang.python:106124

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--OqWEt8su6EUNtoGiBGWpGPn8Xc1xI6vnJ
Content-Type: multipart/mixed; boundary="W7lr6r6vVAQf0wSmw2gel5VpJ2RVAi0fU"
From: Mark Sapiro <mark@msapiro.net>
To: python-list@python.org
Message-ID: <56FCACAE.3060405@msapiro.net>
Subject: Re: Threading is foobared?
References: <56F7B5FA.4040002@timgolden.me.uk>
In-Reply-To: <56F7B5FA.4040002@timgolden.me.uk>

--W7lr6r6vVAQf0wSmw2gel5VpJ2RVAi0fU
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi all,

I'm jumping in on this thread because Tim asked.

I'm here because I'm a Mailman developer and the primary maintainer of
Mailman for the @python.org lists.

Regarding the initial post in this thread from Steven D'Aprano
suggesting that broken threading is more common recently and quoting a
couple of Message-ID:/References: headers wherein a message ID was
apparently munged from

<1392737302.749065.1459024715818.JavaMail.yahoo@mail.yahoo.com>
to
<1392737302.749065.1459024715818.JavaMail.yahoo.ref@mail.yahoo.com>

Some Background:

Our long time mail.python.org server provided by xs4all died of severe
hardware failure late last October. We were able to get a replacement
server through the PSF and get it configured and running within a couple
of days, but this new server couldn't access the nntp server at xs4all.
With the kind assistance of members of the community we were able to get
access to a news server at the Free University of Berlin which is now
our gateway to Usenet.

This server undoubtedly has different policies and behaviors from the
prior server at xs4all. I'm not sure what mail or news server is
responsible for munging the IDs as above, but it could be our new Usenet
gateway. All I know for sure is that Mailman doesn't do that specific
munging.

What Mailman does do as noted by Random832 is replace the Message-ID:
header value in posts gated to Usenet with a list specific, Mailman
generated unique value. There is a reason for this, and that reason is
if a message is cross-posted to two lists which both gateway to Usenet,
and Mailman didn't make the Message-IDs unique, the news server would
discard one of the two posts as a duplicate and the post would be
missing from one of the recipient Usenet groups.

Granted that this is bad and breaks threading, but avoiding message loss
is a more important goal.

I understand I'm not providing any solutions here, but perhaps a more
complete understanding of what the issues are will ease the pain.

--=20
Mark Sapiro <mark@msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan


--W7lr6r6vVAQf0wSmw2gel5VpJ2RVAi0fU--

--OqWEt8su6EUNtoGiBGWpGPn8Xc1xI6vnJ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iEYEARECAAYFAlb8rK8ACgkQVVuXXpU7hpOnDQCgshRsSXHvYlafJKeEpVBJGk2q
h9UAn2w9NkBpnNMIauCO6DYh3u6FFbi3
=NKRd
-----END PGP SIGNATURE-----

--OqWEt8su6EUNtoGiBGWpGPn8Xc1xI6vnJ--