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

Re: still in search of a good news reader

Michael M. wrote, On 2006-09-24 17:18:

If you can't find a newsreader that does everything you want on it's own, you might want to take a look at Leafnode: http://www.leafnode.org/

I've installed it (-:. It involved a bit of manual fiddling that took me back to the days of running INN under UnixWare 1.X.

It's an NNTP server you can run locally. You can set it up to pull from all three of the remote servers you use, and do all your filtering within Leafnode. That will free you up to use any gui newsreader you want, regardless of how dumb. :-) You can focus on finding one with an interface you like, without having to worry about whether it can handle multiple servers, do server-side filtering, etc.

I think the original idea of Leafnode was to provide people who used "online" newreaders with "offline" newsreading capability, but it does more than that. Basically, Leafnode is to newsreaders as an MTA/MDA is to an email client. Personally, I think Thunderbird works well in combination with Leafnode.

My /etc/news/config is at the moment:

expire = 31
server = news-server.bigpond.net.au
initialfetch = 1000
groupexpire comp.risks = 365
server = news.gmane.org
initialfetch = 1000
only_groups_pcre = gmane\.
server = news.mozilla.org
initialfetch = 1000
only_groups_pcre = mozilla\.
nodesc = 1
maxcrosspost = 5
filterfile = /etc/news/leafnode/filters
article_despite_filter = 1

with /etc/news/leafnode/filters set to:

^Newsgroups:.*[, ]gmane.spam.detected$
^Newsgroups:.*[, ]gmane.spam.detected,

to remove material cross-posted to gmane.spam.detected.

The only problem so far is that comp.risks only has the most recent issue in it, whereas knode fetched the last 17 issues from news-server.bigpond.net.au.

Any suggestions for improvements to the above config or filters welcomed.


Reply to: