[leafnode-list] still not succeeding ...

[Werner Partner <kairos@xxxxxxxxxxx>]

Some time ago I wrote about that I do not see the deleted postings.
I propose that leafnode works correct, nevertheless I would be better
informed if I knew _which_postings are deleted.

fetchnews gives following protokol:

fetchnews: version 2.0.0.alpha20030209a; verbosity level is 3; debugging
level is 289
fetchnews mode: get articles, get headers, get bodies, post articles
last active refetch 51 days ago.
lockfile_exists(timeout=5), fqdn="idefix.dom"
expiring interesting.groups
reading /var/spool/news/leaf.node/groupinfo and
/etc/leafnode/local.groups
found 0 articles in in.coming.
news.t-online.de: connecting to port nntp
  trying:    address 62.153.159.134 port 119...
  connected: address 62.153.159.134 port 119.
news.t-online.de: connected (200), banner: "200 T-Online Newsserver
bereit [07] (posting ok)."
news.t-online.de: TCP send buffer size is 16384
news.t-online.de: checking for new newsgroups
news.t-online.de: found 0 new newsgroups
de.comp.datenbanken.ms-access: no new articles
filtering in de.rec.musik.klassik: ^Subject:.*D.*E.S.C.R.A.M.B.L.E.R ->
kill
filtering in de.rec.musik.klassik: ^Subject:.*CABLE.*BOX.*DESCRAMBLER ->
kill
filtering in de.rec.musik.klassik: ^From:.*(delete|spam) -> -1
filtering in de.rec.musik.klassik: ^Subject:.*(Debian|Redhat) -> -1
filtering in de.rec.musik.klassik: ^Subject:.*[Ss]tammtisch -> -1
filtering in de.rec.musik.klassik: ^From:.*(Werner
Partner|kairos\@t-online.de) -> +9999
filtering in de.rec.musik.klassik: maxage -> kill
filtering in de.rec.musik.klassik: maxbytes -> -10
filtering in de.rec.musik.klassik: maxcrosspost -> -10
filtering in de.rec.musik.klassik: ^From:.*(A.Melon) -> kill
de.rec.musik.klassik: considering 2 articles 22212 - 22213, using XOVER
de.rec.musik.klassik: XOVER: 2 seen, 0 I have, 0 filtered, 2 to get
de.rec.musik.klassik: will fetch 2 articles
de.rec.musik.klassik: 2 articles fetched (to 3289), 0 killed

[... other newsgroups, other filters ...]

microsoft.public.de.access: considering 2 articles 174762 - 174763,
using XOVER
microsoft.public.de.access: XOVER: 2 seen, 1 I have, 1 filtered, 0 to
get
microsoft.public.de.access: all articles already there
found 5 articles in out.going.
news.cis.dfn.de: 0 articles posted
fetchnews: 3 articles and 0 headers fetched, 14 killed, 5 posted, in 81
seconds

14 articles were killed and I suppose this is correct. But how do I
succeed showing the 14 articles which were killed? I got a patch but
this did not help :-(

What about debugging level?

I just see that last active refetch is 51 days ago, what is active
refetch - and how often should it be?

Werner



-- 
-----------------------------------------------------------
 kairos: Werner Partner * Tel +49 2366 886606 * Fax: 886608
 kairos@xxxxxxxxxxx  * http://www.sonoptikon.de

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list