Menu: attitudes(settings) / Local servers / user / news
Local NNTP-server start automatically:
If this field is active, the local NNTP-server is automatically started by the start of the hamster. The manual changeover is possible for menu about the " Local server ".
Port:
The "Port" number puts the Port of the server firmly i.e. under which TCP/IP-Port the Client on the local news server can access. Standard is the Port 119.
Header add / Message-ID produce, if still nobody exist:
If this field is active, the hamster generates the Message-ID, if she has not been set already by the news-Reader. Then " local part " the Message-ID is formed from the current time, the Task-number and a sequential numerator per unit of time. With an as well unambiguous "FQDN" arises therefore an address which is enough for the technical claims in Message-IDs (i.e. for at least two years unambiguously).
Header add /-Header Produces additional "X-Posting-Agent":
If this field is active, the hamster "immortalizes himself" in the Header of every sent article in form of an additional " X-Posting-Agent: hamster Vxxx "-Headers.
Posts in unknown groups allow:
Usually are automatically rejected Crosspostings which go to at least one to the hamster unknown news group. With this attitude(setting) sending (=Posten) can be allowed in unknown groups - whether the external news server accepts the article, is not sure with it naturally yet.
Followers Einschräkungen are also considered(apply) with activated attitude(setting):
- At least a target group must be confessed.
- Maximally two unknown groups, provided that no "Followup-To"-Header is set.
- Maximally five unknown groups if a "Followup-To"-Header is set.
Max. Size go out for. Postings
Here one can give(indicate), how big maximally going out Postings may be. Standard is two megabytes and one thousand of lines. An input of "0" switches off the respective filter. If only a filter should apply, the Posting nevertheless is rejected.
Holds duration during days...:
Here it is fixed, how long the hamster should keep various data, since he may dispose them(her) with the rangement.
"Postings": this field fixes how much days the hamster the articles stores locally. This information refers not to the date in the Header of the articles, but to the real number of days, since the article was got by the news server.
"History": the History is the list the Message-ID of all articles which have already loaded from the news server. She is stored in the file
".\Groups\History.dat", for Performance-reasons hamster buffers them(her), however, completely in the main memory. On the bases of the History it is checked with the shop by articles whether the article is already known. The higher therefore the holds duration is chosen, the hamster needs all the more main memory, but so more improbably it is that he gets article by accident twice." Killfile-Prot. ": the file
".\Groups\Kills.log") contains the Message-IDs of the articles filtered out about the news-Score/Kill-Filter. The holds duration determines therefore directly, how long one still has the chance to request the article later. If the external news server should not have the article any more, a long holds duration of this protocol helps naturally also nothing.Killfile-protocol: articles below this score do not indicate:
All filtered out articles are usually indicated in the Killfile-protocol. If one wants never again to see certain articles, however, guaranteed, here one can give(indicate) the (negative) value below his(its,that) the articles should be removed "without remains".