Hi All,
We are running a local instace of Usenet server.
[...]
You want to import historic/archived postings into a running inn
instance?
In which format are the postings you have available? One article per
file? Batch files containing multiple postings?
And do you want to know whether or not you use a viable method to import
the postings or do you want to know a / the appropriate way to import the postings?
(I think the later would be the/a sensefull way)
Be aware that article numbers are heavily problematic since they may be -
not unlikely are - already in use on the actual server. They are also
only partially helpfull if you use other storage methods than "tradspool".
Duplicate detection and the like are performed if you "feed" the
postings into inn. This is processor intensive but from my point of
view the most secure method to feed - historic as well as current -
postings into the message base.
[...]
So, for the consistency, i could fetch all the headers, build a list of Message-IDs used and alter the Message-ID as well as 'References:' and 'In-Reply-To:' fields of the message imported.
I need to have proper threading and no duplicate messages on the server.
INN does duplicate detection already by itself. That's nothing you need
to do. And you also need no separate python implemented NNTP feeder
since such tools already exist.
You may find it easier to set up a second INN server, assemble a list of
all the articles you want on that server in correct date sorted order, and then feed all the articles to that server in that order using innxmit or
some similar tool. This will also require some work to assemble all the pieces and build the batch file pointing to all the article files, so it
will take some manual experimentation. (Since I haven't done that experimentation in over ten years, I unfortunately can't give you step-by-step instructions.) But it may mean less fiddling than manually assembling a tradspool structure and rebuilding history and overview. Or
it may not! I'm not sure which is easier.
You may find it easier to set up a second INN server, assemble a list of
all the articles you want on that server in correct date sorted order, and >> then feed all the articles to that server in that order using innxmit or
some similar tool. This will also require some work to assemble all the
pieces and build the batch file pointing to all the article files, so it
will take some manual experimentation. (Since I haven't done that
experimentation in over ten years, I unfortunately can't give you
step-by-step instructions.) But it may mean less fiddling than manually
assembling a tradspool structure and rebuilding history and overview. Or
it may not! I'm not sure which is easier.
This is the way to go - there was a thread I started some months back where Julien helped provide the syntax necessary to generate the list of messages sorted by posting date which you can then transmit to another server.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 304 |
Nodes: | 16 (2 / 14) |
Uptime: | 36:11:46 |
Calls: | 6,822 |
Calls today: | 2 |
Files: | 12,337 |
Messages: | 5,407,256 |