linux user group brescia

Alle 19:16, venerdì 20 settembre 2002, andrea gelmini ha scritto:

> accade che taluni news server tornino un elenco delle news disponibili
> errato... nel senso che il body non e` disponibile... ora, che ti
> accada con tutti i messaggi mi sembra strano.
> guarda i log, o fai delle query direttamente al server, e guarda che
> messaggi/quanti messaggi ti torna disponibili.
> che news server usi, per curiosita`?
>
> ciao,
> andrea

Come news server uso news.cis.dfn.de: è sempre andato molto bene...
Credo sia proprio un problema di configurazione di leafnode, oppure un 
problema di "comunicazione" fra Leafnode e KNode.
Posto il config di Leafnode, così magari qualcuno trova l'inghippo...

Grazie
		Robilio

________________________________________________________________________

## This is the NNTP server leafnode fetches its news from.
## You need read and post access to it. Mandatory.
server = news.cis.dfn.de

## Unread discussion threads will be deleted after this many days if
## you don't define special expire times. Mandatory.
expire = 20

## Important and recommended setting:
## Fetch only a few articles when we subscribe a new newsgroup. The
## default is to fetch all articles.
initialfetch = 150

## I have free access to my news server. If you don't have, comment out
## the following two lines and change them accordingly.
username = xxx
password = xxx

## By default, leafnode only serves connections from addresses in the
## local networks and drops those from outside. An IPv4 address is
## considered local if it is within the networks (IP/netmask) of the local
## interfaces. An IPv6 address is considered local if it is site-local,
## link-local or the loopback address (::1).
## If you do have working AND TESTED access restriction in place, and if 
your
## leafnode is wrapped with tcpd and you have selected remote users you
## still want to let in, uncomment this, capitalize the "strangers" part
## of the name and set this to 42. Yes, I know, this is ugly. But most
## users will not need it. And it's dangerous.
## AGAIN: ONLY SET THIS WHEN WORKING AND TIGHT ACCESS CONTROL
## (hosts.deny, tcpd) IS IN PLACE. USING THIS OPTION WITHOUT ACCESS 
CONTROL
## WILL OPEN LEAFNODE TO ABUSE, SPAMMING, SUBSCRIBE YOU TO GROUPS YOU DO
## NOT WANT ETC. ## YOU REALLY DO NOT WANT TO ENABLE THIS OPTION. TRUST 
ME.
# allowstrangers = 0

## Standard news servers run on port 119. If your newsserver doesn't, 
comment
## out the following line and change it accordingly.
# port = 8000

## If you want to guarantee that the stdout/stderr are line buffered
## (GNU libc sets them to full buffering if they are redirected to
## files), then set this:
# linebuffer = 1

## Non-standard expire times (glob(7) wildcard constructs possible)
#
# groups too big to hold articles 20 days:
# groupexpire comp.os.linux.* = 5
#
# very interesting, hold articles longer:
# groupexpire any.local.newsgroup = 100
#
# archive this group (fetchnews uses the global expire to figure the
# maxage, but texpire will skip it):
# groupexpire my.archived.group = -1

## Never fetch more than this many articles from one group in one run.
## Be careful with this; setting it much below 1000 is probably a bad
## idea.
# maxfetch = 2000

## If you want to use leafnode like an offline newsreader (e.g. Forte
## Agent) you can download headers and bodies separately if you set
## delaybody to 1. In this case, fetch will only download the headers
## and only when you select an article, it will download the body.
## This can save a huge amount of bandwith if only few articles are really
## read from groups with lots of postings.
## This feature works not very well with Netscape, though (which is not
## a fault of Leafnode).
delaybody = 1

## To avoid spam, you can select the maximum number of crosspostings
## that are allowed in incoming postings. Setting this below 5 is
## probably a bad idea. The default is unlimited crossposting.
# maxcrosspost = 5

## If you suffer from repeatedly receiving old postings (this happens
## sometimes when an upstream server goes into hiccup mode) you can
## refuse to receive them with the parameter "maxage" which tells the
## maximum allowed age of an article in days. A value of 0 indicates that
## no checking should be performed. The default maxage is 10 days.
## WARNING: maxage can be overridden by expire! See the clamp_maxage
## parameter below.
# maxage = 10

## By default, maxage is limited to groupexpire (if applicable) or
## expire (otherwise). On some rare occasions, this limit may be
## undesirable. To avoid this maxage manipulation, uncomment this line:
# clamp_maxage = 0

## maxlines will make fetch reject postings that are longer than a certain
## amount of lines.
# maxlines = 100

## minlines will make fetch reject postings that are shorter than a 
certain
## amount of lines.
# minlines = 2

## maxbytes will make fetch reject postings that are larger
# maxbytes = 50000

## timeout_short determines how many days fetch gets a newsgroup which
## has been accidentally opened. The default is two days.
timeout_short = 1

## timeout_long determines how many days fetch will wait before not 
getting
## an unread newsgroup any more. The default is seven days.
timeout_long = 3

## timeout_active determines how many days fetch will wait before 
re-reading
## the whole active file. The default is 90 days.
# timeout_active = 365

## timeout_client determines how many seconds of inactivity to allow 
before
## a client is forcibly disconnected. The default is 15 mins (900s). 
Optional.
# timeout_client = 900

## If you want to have your newsreader score/kill on Xref: lines, you 
might
## want to uncomment this.
# create_all_links = 1

## If you want to filter out certain regular expressions in the header,
## create a "filterfile" (how this is done is explained in the README)
## and set
# filterfile = /path/to/your/filterfile

## If your newsreader does not supply a Message-ID for your postings
## Leafnode will supply one, using the hostname of the machine it is
## running on.  If this hostname is not suitable, this parameter can be
## used to override it.  Do not use a fantasy name, it may interfere with
## the propagation of your messages.  Most modern newsreaders do provide
## a Message-ID.
# hostname = host.domain.country