e-mail<->usenet gateway Reply-To header (PR#303)

[Bug Importer]

Jitterbug-Id: 303
Submitted-By: <email address hidden>
Date: Mon, 24 Jul 2000 18:54:02 -0400 (EDT)
Version: 2.0beta4
OS: Debian linux potato

I'm running a plain e-mail<->usenet gateway.
When someone replies to a usenet post through the list, his e-mail client
sets
an In-Reply-To: header instead of a Reply-To: header. This causes
newsreaders to
improperly thread messages.

I inserted the following bit into Mailman/Handlers/ToUsenet.py at around
line
82:

    # if the message is a reply to a previous post, change the header so
    # that newsreaders can thread it properly
    if msg.getheader('in-reply-to'):
        msg.headers.append('References: %s\n' %
msg.getheader('in-reply-to'))
        del msg['in-reply-to']

I'm happy to say that this solved the problem.

(before you laugh at me, take note that I never looked at python before.)

====================================================================
Audit trail:
None

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

[Barry Warsaw (barry)]

This sounds like the email client in question is broken. Mine for example,
correctly inserts References: headers and the news readers properly thread
the messages. I'm not inclined to cater to broken email or news clients.

[Barry Warsaw (barry)]

RFC 2076 says nothing about using In-Reply-To for news, so it might not be
a bad idea to copy In-Reply-To to References when gating a message from
mail to news.

[Giuans (giuans)]

What a coincidence! I had the same problem and I looked
into the code, then modified it to work properly. The
coincidence is that my patch is *identical* to yours. So,
for sure it works :-)

[Barry Warsaw (barry)]

Changing the group to 2.1 beta because I want to look at
threading issues for gated messages before 2.1 final is
released.

[Barry Warsaw (barry)]

Sigh. Very doubtful I'll get to look at the threading
issues before MM2.1 final. I'll address this again after
the release.

[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 Linux itself.

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