I'm running leafnode on our small company's server.
I can read news without a problem, but I can't post messages.
The client program sends the message to leafnode without a
problem, but leafnode just doesn't send it onto the upstream
The debug from "fetch" claims that it doesn't send it because
the upstream server already has that message.
But of course, this isn't possible.
I'm thinking that either leafnode is making up article numbers
which are very coincidently repeats of existing ones on the
upstream server, or there's just something funny going on.
The following is debug output of leafnode:
root> fetch -vvvv
1.9: verbosity level is 4
Trying to connect to news.upstream.net.au ... connected.
9754-934970872-1 already available upstream
Getting new newsgroups from news.upstream.net.au
Read server info from /var/spool/news/leaf.node/news.upstream.net.au
sci.geo.satellite-nav: no new articles
comp.os.linux.networking: no new articles
aus.test: no new articles
aus.electronics: no new articles
sci.electronics.design: no new articles
Disconnected from news.upstream.net.au.
What's causing it to think that the article is already sent ?
By the way, I can definately send emails directly from my news
client to the news.upstream.net.au server successfully every
time, and I cannot sent anything through leafnode (tried 10
Is there better documentation on leafnode than the README
which comes with leafnode, or the NEWS-Leafsite mini-howto ?
Delete the 'x' to remove the spamblock