["Followup-To:" header set to news.software.readers.]
On 2011-11-21, Fritz Wuehler
<
fr...@spamexpire-201111.rodent.frell.theremailer.net> wrote:
> Hello. I am looking at a program called 'nget', which I run in Windows.
> It uses the shell command line interface, and its purpose is to download
> news messages from NNTP servers. I just started using it, and it is not
> all that difficult to configure. I managed to configure it to download
> messages from a server according to my specified criteria of the last 10
> days of postings. I do not believe it is still being maintained, but it
> works nicely, and is well suited to a purpose of mine.
It's "mature" rather than "not maintained", I think ;))
> The downloaded messages are saving in individual files for each message,
> which is what I want, instead of mbox format. What I am seeing is that
> there is a separate text file (filename.txt) containing a message's
> headers and another file for the message body, which is being saved in
> base64 format even though the messages have only plain-text data. These
> files are getting named with the message subjects, and that is fine with
> me too.
I imagine the 'bodies' are being saved separately and in Base64 because
nget is intended to handle multi-part binary and multiple upstream
servers; you'd want such posts to be recombined and decoded into their
original form.
> I would prefer to have the message body and headers kept together, if
> possible, in a separate text file. Also, I have not figured out whether
> there is a way to use nget to browse through these messages. If not, I
> need a suggestion for doing so.
>
> Finally, I would like to know if there is a way to speed up the download
> by skipping the decoding a temp file process. Not sure if that is
> doable, but I would like to know.
The 'decoding' step is probably related to nget's use with binary posts.
The man file may give you the command-line parameter(s) to use to control
that behaviour, ir it's possible.
> Any ideas would be welcome. Thanks.
I think you'd be better served by using a "local cashing proxy
news-server" of your own. This would create a standard usenet "spool" on
your hard disc, and you could use any news-reader you like to read the
messages. (A usenet spool has a directory for each newsgroup and a single
file for each post, with the complete headers and body exactly as posted).
I use Leafnode2 (command-line controlled) as my local server, and slrn
(text-only console interface) for reading. If you only want to use one
up-stream server, srln's companion slrn-pull would probably suit you
better than Leafnode.
The only Windows-native news-server I've used is "Hamster".
--
-- ^^^^^^^^^^
-- Whiskers
-- ~~~~~~~~~~