[ mailman-Bugs-1256272 ] NNTP gatewaying trashes Message-IDs

SourceForge.net noreply at sourceforge.net
Thu Apr 20 07:13:33 CEST 2006

Bugs item #1256272, was opened at 2005-08-10 16:47
Message generated for change (Comment added) made by nobrowser
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: nntp/news
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Kate Turner (kateturner)
Assigned to: Nobody/Anonymous (nobody)
Summary: NNTP gatewaying trashes Message-IDs

Initial Comment:
when a message is relayed to NNTP, the NewsRunner
unconditionally replaces the existing Message-ID with
its own.  this breaking threading when reading a list
via news, and when an NNTP user replies to a list message.

a better solution would be either:
1) do not rewrite the message-id unless the NNTP server
reports an error when posting it (duplicate ID); or
2) optionally, always rewrite posters' message-ids into
a mailman-generated ID, and use this ID for both mail
and news.

i have implemented the former at our site and it
appears to work, but it's so ugly i'd not feel
comfortable submitting a patch for it.


Comment By: Ian Z. (nobrowser)
Date: 2006-04-19 22:13

Logged In: YES 

Finally!  I thought I was the only one who noticed this.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=346413

Why would the mail message-id ever cause a conflict with
the NNTP server?  message-ids are supposed to be globally
unique and there is a convention (in RFC 2822?) that ensures
it (put in the FQDN and something unique to the generating
software).  So I think 1) is not ugly but correct :)

2) wouldn't completely solve the problem.  
I can post one copy of a message to a mailman list and
another directly to another recipient, including myself.
(I actually Cc myself on all mail I send).  If mailman
does 2), the extra recipient will still be confused.



You can respond by visiting: 

More information about the Mailman-coders mailing list