[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[leafnode-list] Re: Duplicate posting to a moderated group

Am 20.06.2009, 20:53 Uhr, schrieb Adam Funk <a24061@xxxxxxxxxxxxx>:

> On 2009-06-19, Adam Funk wrote:
>> On 2009-06-17, Adam Funk wrote:
>>> Is this potential problem still in existence?  I suspect that one of
>>> my upstream servers does not have a moderated group flagged
>>> correctly.  How do I tell whether leafnode knows it's moderated or
>>> not?
>> I've checked my groupinfo file: leafnode does not think
>> uk.legal.moderated is moderated (it has "y" instead of "m").
> ...
>> Or should I edit the problematic server's only_groups_pcre to exclude
>> this group (and run `fetchnews -f`, of course)?  I suppose this change
>> should do it (since I don't depend on that upstream server for any
>> groups with "moderated" in the name):
>> only_groups_pcre =  
>> ^([\+\-\w]+)(\.[\+\-\w]+(?<!binaries|binary|mp3|warez|binares|binarios|binari|binair))*$
> I decided to do this and it fixed the problem, but now I have a
> question: how does leafnode 2 decide how to flag a group if it gets
> conflicting information from the upstream servers?  I suspect that my
> problem started when I switched from leafnode 1 to 2 (using the same
> servers) but I'm not certain.

To some extent, it's a leafnode-2 specific problem, in that leafnode-1
doesn't care a bit for the moderator status of groups. Leafnode-1 posts
once to the first server that has the group, and that's it. Leafnode-2
posts to all servers that (a) have the gruop and (b) until the article
appears. Now, "article appears" doesn't work for moderated groups, because
moderation introduces delays. Now, to avoid spamming the moderators, we
need to change to a "post once" (or mail, if we know the moderator)

WRT reconciliation of conflicting flags, it just doesn't happen. First
match wins - where first match is vaguely defined here, as the schedule
for re-querying active files is not fixed and can vary with availability
and errors encountered during the conversations; but "first match" should
work for a fetchnews -f run when all servers are reachable.

I'm not sure if it's possible to solve this with sort of "status
precedence" - which one is "more correct" or "more likely correct"?
Moderated or Open posting groups? I don't think this is solvable without
human interaction.


Matthias Andree
leafnode-list mailing list