[Mailman-Developers] [ mailman-Patches-573505 ] usenet threading improvements

[SourceForge.net]

Patches item #573505, was opened at 2002-06-25 01:59
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103

Category: mail delivery
Group: Mailman 2.0.x
Status: Open
Resolution: None
Priority: 1
Submitted By: Mark Weaver (mdw21)
Assigned to: Nobody/Anonymous (nobody)
Summary: usenet threading improvements

Initial Comment:
Basically message-id munging for all messages.

Might be 
better as an option?  This helps with threading in usenet gating, as 
what happens is this:

someone sends a mail with message-
id foo at bar.com
gating replaces the message-id with 
mailman.123.456.list at list.com
list member replies via mail, 
"in-reply-to" header is set to the foo at bar.com
now when the 
message is gated it can't thread because in-reply-to: (which is 
translated into references:) is wrong.

Solution is to munge 
all message-ids.  Doesn't really do any harm AFAICT.

----------------------------------------------------------------------

Comment By: Nicolas Marchildon (elecnix)
Date: 2003-01-16 00:11

Message:
Logged In: YES 
user_id=106549

I solved the problem by adding the munging code to
DeliverToList, in HandlerAPI.py, right before the message is
sent in the delivery pipeline, and removed it from
ToUsenet.py and CookHeaders.py. This way, the Message-ID
header is calculated only once, and used for all the steps
of the pipeline.

Nicolas Marchildon

----------------------------------------------------------------------

Comment By: Nicolas Marchildon (elecnix)
Date: 2003-01-15 23:21

Message:
Logged In: YES 
user_id=106549

The submitted patch does not do what it should to. The calls
to time.time() will not return the same thing as in
ToUsenet.py. I don't know much about the internals of
Mailman, and not much either about Python, so I don't really
know where to store the "correct" message ID so that it is
generated once, and used in both places.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103