[ mailman-Bugs-1256272 ] NNTP gatewaying trashes Message-IDs
SourceForge.net
noreply at sourceforge.net
Sat Apr 29 16:44:01 CEST 2006
Bugs item #1256272, was opened at 2005-08-11 00:47
Message generated for change (Comment added) made by kateturner
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1256272&group_id=103
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: Kate Turner (kateturner)
Date: 2006-04-29 15:44
Message:
Logged In: YES
user_id=1116721
the conflicts occur when a user cross-posts a message to
two lists. the newsrunner won't turn it into a cross-post,
instead it tries to post it separately to both groups, and
the news server rejects the second one for a duplicate
message-id (tested with innd).
of course, you could say this behaviour is a bug too :) i'm
not sure what the best way to group cross-posted messages
is, since they won't be received by the same mailman
instance. (cancelling the first and re-posting to both
groups might work, but i don't know if inn will still
record the message-id and not allow it to be reused.)
----------------------------------------------------------------------
Comment By: Ian Z. (nobrowser)
Date: 2006-04-20 06:13
Message:
Logged In: YES
user_id=1192798
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.
Ian
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1256272&group_id=103
More information about the Mailman-coders
mailing list