I'm not sure if this is a problem with Mailman or INN, but I'll start on the Mailman side. If it's an INN problem, I'll be happy to redirect my question to the appropriate forum.
I'm in the process of adding a news/mail gateway to a server that's running Mailman 2.1.9-7 on a Debian 4.0 box. I'm adding INN 2.4.3-1 . Both Mailman and INN are installed from the Debian Stable channel.
Where I'm having problems is with messages posted from the news side -- they're gated into Mailman, and distributed correctly to mailing list subscribers, but then a copy of the message goes back through to the INN server, and INN isn't recognizing the message as having been seen, and the result is that the news side of thing sees a duplicate copy of the message.
On further inspection, the duplicate message has clearly been submitted to news by Mailman, and includes lots of Mailman-specific headers. In particular, the Message-ID: header is rewritten by Mailman, and I'm assuming that INN relies on Message-ID: to track what has been seen or not.
This is happening with nearly all the mailing lists configured to be gated to news on this server, with the exception of one list, where I'm not getting dupes. This implies that the difficulty is specific to the configuration of individual lists, but I can't see any difference in configurations on either Mailman or INN between the list/newsgroups that are getting duplicates, and the one that isn't.
It looks like I'm missing something small, but I'm not seeing it.
Any clue as to where I should start looking?
Composed by sacbeemail. Get Your Free E-mail at http://www.sacbeemail.com . Or visit Northern Californias premiere news and information website at http://www.sacbee.com .
NFN Smith wrote:
Where I'm having problems is with messages posted from the news side -- they're gated into Mailman, and distributed correctly to mailing list subscribers, but then a copy of the message goes back through to the INN server, and INN isn't recognizing the message as having been seen, and the result is that the news side of thing sees a duplicate copy of the message.
What I've seen a lot is that people tend to post to news with clients that also send out a copy by e-mail, and the mailing list is configured to gateway articles back to the newsgroup, thus resulting in duplicates.
Another source of duplication is if you have multiple people operating mail-to-news gateways.
On further inspection, the duplicate message has clearly been submitted to news by Mailman, and includes lots of Mailman-specific headers. In particular, the Message-ID: header is rewritten by Mailman, and I'm assuming that INN relies on Message-ID: to track what has been seen or not.
INN does rely on the Message-ID to track whether or not it has seen this particular message, but an article being gatewayed in via USENET should not then be gatewayed back out to USENET by Mailman. The pipeline of routines within Mailman should be set up to avoid precisely that condition.
However, see FAQ 4.59 at <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.059.htp> for the reasons why Mailman modifies the Message-ID header on incoming USENET news.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
Brad Knowles wrote:
INN does rely on the Message-ID to track whether or not it has seen this particular message, but an article being gatewayed in via USENET should not then be gatewayed back out to USENET by Mailman. The pipeline of routines within Mailman should be set up to avoid precisely that condition.
Exactly. When cron/gate_news polls the news group and posts messages to the Mailman list, it puts a fromusenet flag in the message's metadata. The ToUsenet handler looks for this flag and will not process the message if it is present.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Brad Knowles -
Mark Sapiro -
NFN Smith