Mark Sapiro wrote:
> Random832 wrote:
>
>> Any chance that it could fix reference headers to match?
>>
>> Actually, merely prepending the original Message-ID itself to the
>> references header might be enough to change the reply's situation from
>> "nephew" ("reply to [missing] sibling") to
Random832 wrote:
> One additional thing that would be nice and would solve most of the
> duplicate problem with hypothetically including the rewritten
> Message-IDs in outgoing emails, would be to detect crossposts to
> multiple lists in the same Mailman instance, and to send them to Usenet
>
Random832 wrote:
> Any chance that it could fix reference headers to match?
>
> Actually, merely prepending the original Message-ID itself to the
> references header might be enough to change the reply's situation from
> "nephew" ("reply to [missing] sibling") to "grandchild" ("reply to
>
On Thursday 31 March 2016 15:50, Mark Sapiro wrote:
> Hi all,
>
> I'm jumping in on this thread because Tim asked.
[...]
Thanks for the explanation!
--
Steve
--
https://mail.python.org/mailman/listinfo/python-list
On Thu, Mar 31, 2016, at 01:25, Random832 wrote:
> Actually, merely prepending the original Message-ID itself
append, not prepend... I'd misremembered the order that References go
in.
--
https://mail.python.org/mailman/listinfo/python-list
On Thu, Mar 31, 2016, at 01:25, Random832 wrote:
> > 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
On Thu, Mar 31, 2016, at 00:50, Mark Sapiro wrote:
> 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
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
On 30.03.2016 01:43, Steven D'Aprano wrote:
On Tue, 29 Mar 2016 09:26 pm, Sven R. Kunze wrote:
On 27.03.2016 05:01, Steven D'Aprano wrote:
Am I the only one who has noticed that threading of posts here is
severely broken? It's always been the case that there have been a few
posts here and
On Tue, Mar 29, 2016, at 19:54, Rob Gaddi wrote:
> Just read on Usenet instead of through the mailing list. That way
> you can accept broken threading as a given rather than wonder why it's
> happening in a particular case.
It's a given everywhere. Any thread that contains a sufficient number of
Steven D'Aprano wrote:
> Am I the only one who has noticed that threading of posts here is severely
> broken? It's always been the case that there have been a few posts here and
> there that break threading, but now it seems to be much more common.
>
> For instance, I see Jerry Martens' post
On Tue, 29 Mar 2016 09:26 pm, Sven R. Kunze wrote:
> On 27.03.2016 05:01, Steven D'Aprano wrote:
>> Am I the only one who has noticed that threading of posts here is
>> severely broken? It's always been the case that there have been a few
>> posts here and there that break threading, but now it
On 27.03.2016 05:01, Steven D'Aprano wrote:
Am I the only one who has noticed that threading of posts here is severely
broken? It's always been the case that there have been a few posts here and
there that break threading, but now it seems to be much more common.
I agree. Didn't we both
On 27/03/2016 07:25, Random832 wrote:
On Sat, Mar 26, 2016, at 23:18, Ben Finney wrote:
What you've demonstrated is that at least one host is violating
communication standards by altering existing reference fields on
messages in transit.
The usenet gateway relays posts that originated on the
On Sat, Mar 26, 2016, at 23:18, Ben Finney wrote:
> What you've demonstrated is that at least one host is violating
> communication standards by altering existing reference fields on
> messages in transit.
The usenet gateway relays posts that originated on the mailing list to
usenet with their
Steven D'Aprano writes:
> Am I the only one who has noticed that threading of posts here is
> severely broken? It's always been the case that there have been a few
> posts here and there that break threading, but now it seems to be much
> more common.
I can't give an
Am I the only one who has noticed that threading of posts here is severely
broken? It's always been the case that there have been a few posts here and
there that break threading, but now it seems to be much more common.
For instance, I see Jerry Martens' post "help with program". According to my
17 matches
Mail list logo