header munging ruins threading

[Monkeymaster]

The header hacking done by ToUsenet.py ruins threading
in mail! It takes a perfectly good message ID, and
throws it away! news replies to a mail message appear
to be replies to the parent (since the news messag
references contain the references of the parent + some
crazy mailman message ID).

This is bogus.

At the very least, could you add the real message ID
somewhere so that newsreaders will include it in the
references headers? Some of us actually use threaded
mailers, you know!

[http://sourceforge.net/tracker/index.php?func=detail&aid=451475&group_id=103&atid=100103]

[Barry Warsaw (barry)]

The problem is that many NNTP servers are really picky about
message-id's; they won't allow duplicates, and they won't
allow cross-postings with the same message-id. I suppose if
the message had an id we could try to preserve it, attempt a
post, and if that's rejected by the nntpd, we could try
again with our own crafted message-id.

I'm up for any suggestions that are rfc-compliant and work
with the widest range of currently existing nntpds.

[Elecnix (elecnix)]

The solution is probably not to remove munging, but to munge
both mail and usenet message IDs.

See patch #573505

[Jean.c.h (slug71)]

Marked this bug as 'Invalid' due to its age and nothing further has been added in a long time. New versions have been released since as well as some underlying stuff in the OS platform itself.

If this bug still affects then please change status back to 'Confirmed'.