NFN Smith wrote:
>
>> 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.
>
>OK, that makes sense.
>
>Any i
>> 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
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 preci
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
see
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
