> I've got DNews setup and running fairly smoothly, at least to the point
I'm
> at, but I have a few mysteries I'd like to solve.
>
> I've set up a suck feed from msnews.microsoft.com groups and have it
working,
> to a point.
>
> In dnews.conf I have:
>
> nntp_feeder msnews.microsoft.com groups *.public.dotnet.*,...
>
> In newsfeeds.conf I have:
>
> site me
> groups *
> rules d:\server\dnews\filter.rul
> site mail.server
> smtp
> site $nntp_feeder
> groups the_same_group_list
> maxcross 4
> builtin
> onlyposts
> posting
>
> 1) Does the group list (it's long} need to be duplicated in both
dnews.conf
> and newsfeeds.conf?
No. The list in dnews.conf is of the groups you wish to obtain from your
sucking feeds, so only posts to these groups will be obtained. The
newsfeeds.conf settings control what you send to other sites, which will be
limited to what you obtain from other sites or post locally, so duplicating
the list is usually not necessary.
> 2) Does the rules file specified in the me feed apply to any/all other
feeds?
This is the exception to the above rule - the ME feed controls what you
permit on your own server (usually * is adequate espcially if you are only
sucking, as the list is in dnews.conf), and yes, these rules also apply to
the outgoing feeds since the posts will not be permitted locally if stopped
by this rule.
> 3) Is line length limited in any of the configs? The MS groups list is
> approaching 400 char.
Yes there is. To get around this problem for sucking feeds in dnews.conf,
you can specify a file in your workarea containing a list of rules -
suck_file1 filename.txt
The format of this file is just one rule per line... e.g.
*
!*binaries*
...
> 4) _Exactly_ what steps must be taken to update the server after modifying
the
> groups in an existing suck feed? This one gives me the most grief, as I
> occasionally stumble upon the correct sequence of steps, but can never
seem to
> do it twice in a row.
>
> Here's an example of what doesn't work:
>
> mod suck feed group list
> matchgroups
> cached *
> update 1
>
> So, I'm sure I'm doing something totally clueless.
tellnews cached * 2
Should start all the groups updating for 2 days irrespective of them being
read or not... you need to specify the number of days for this to work
correctly.
Before doing this, you must also do a 'tellnews reload' to ensure dnews has
read the changes.
You can check which groups are cached by using the 'tellnews showcached *'
command.
Also, if the groups are new, and you are using multiple feeds, you may need
to update the list of groups which you can do like this - 'tellnews
getgroups upstream.site.name'.
If that doesn't work, you can try these steps -
First check the group is cached:
tellnews showcached problem.group
If it's not cached set it cached:
tellnews cached problem.group 10
Then manually update the group:
tellnews update_clear
tellnews rotate
tellnews getold problem.group 1000
tellnews debug suck:
tellnews loglvl debug
tellnews updateone problem.group
tellnews updateone problem.group
Then wait a couple of minutes and see if the group is getting items,
tellnews showgroup problem.group
IF it still fails send us the resulting dnews.log
- Roydon L
