[ mailman-Bugs-214205 ] e-mail<->usenet gateway Reply-To header (PR#303)
Bugs item #214205, was opened at 2000-09-11 22:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103
Category: nntp/news Group: None Status: Open Resolution: None Priority: 4 Submitted By: Nobody/Anonymous (nobody) Assigned to: Barry Warsaw (bwarsaw) Summary: e-mail<->usenet gateway Reply-To header (PR#303)
Initial Comment: Jitterbug-Id: 303 Submitted-By: orion@tribble.dyndns.org 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
Comment By: Giovanni Lopedote (giuans) Date: 2002-05-01 14:34
Message: Logged In: YES user_id=531451
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 :-)
Comment By: Barry Warsaw (bwarsaw) Date: 2000-09-27 23:00
Message: 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.
Comment By: Barry Warsaw (bwarsaw) Date: 2000-09-19 18:48
Message: 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.
You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103
participants (1)
-
noreply@sourceforge.net