enamel - the mailserver for the BeO S
Contents [ MCP ] [ nntp ] [ smtp ] [ smtpd ] [ pop3 ] [ pop3d ] [ hermes ] [ Up ] | nntp nntp is an nntp client. It will connect to a host which is running an nntpd and gets new news articles and it also delivers your outoging articles to it. You can configure it to deliver news for different targets to different systems and you can fetch different groups from different servers. To configure nntp, you have to edit the file /boot/home/config/settings/smtp_settings with an editor like StyledEdit or vi. Please have a look at the example config file to find out more about that file. The following is a description of the available config keywords: Logfile <Name> The file where nntp writes some logging output to. (e.g.: LogFile /boot/home/log/nntp.log) Newsserver <Address> [Port <Port>] CheckIntervall <Intervall> [Target <Target>] [Source <Source>] [<Group>] [<Group>] ... This line (or better: these lines) tells nntp where to get and/or send your postings to. "Address" is the newsserver to connect to, where "Port" can define a different port number than the standard 119. "CheckIntervall" specifies how often nntp should check for new postings and deliver your own postings. With "Target", you can specify which postings should be sent to the newsserver. "Source" is the source attribute that should be added to all messages fetched from this server. This can be used by MCP to control where these messages should go to. Starting with the next line, until an empty line comes, you can specify group after group that should be fetched by nntp. As you might have noticed, it is possible to get all articles from one host and send the articles you have written to a different one. (e.g.: Newsserver news.ai-lab.fh-furtwangen.de Port 119 CheckIntervall 60 Target nntp Source nntp comp.sys.be.misc de.comp.os.be )