DNEWS Installation, a brief guide by NetWin World ------------------------------------------------- DNEWS is a dynamic news server system, it is not a news reader but rather it is the server which a news reader reads news from. DNEWS is not freeware, see license.txt for details. Index to this document: (1) DNEWS Feature list (2) Installation VMS (3) Installation for UNIX (4) Installation for Windows NT (5) Installing a full feed (6) Recommended news readers (7) FAQ and What if it doesn't work (8) Using other TCPIP stacks on VMS (9) Mailing lists (10) Notes on compiling and porting DNEWS (unix) (11) Updates, List of bugs fixed for each version. (12) See the FAQ section for "Creating local news groups" ----------------------------------------------------------------------------- (1) DNEWS Feature list: Dynamic sucking feed. A sucking feed may use as little as 10% of the normal disk space and network bandwidth. By only getting news items that people usually read very large savings are possible particularly for small sites & workgroups. A hundred users can be supported on 100 MB depending on their reading habbits! I run a single user server on my NT as a background service, it's using less than 5MB. Flexible expire settings By allowing expiration by 'number of items' low volume groups become much more useful. Also by allowing settings which change with disk space the system is much more stable to large influxes of news. Flexible access restrictions Reading and Posting access can be given separately to to different users and selections of news groups. Binarys available for common platforms On many platforms you do not need to build the binary yourself, e.g. VMS, (VAX & ALPHA), Solaris, Linux, Windows NT Email confirmation of posts DNEWS can be configured to send email confirmations as it sends items up to a main news server. This gives users a clear record of a posted item and it's successful transfer into the 'net'. Items stored in a database Items are stored in a database which puts items together in blocks of 100. This saves directory entries, inodes, and the empty space usually wasted due to blocking factors. Also file open and closes are minimized, this is essential on systems where this is a 'costly' operation, e.g. VMS. Compiling and porting relatively easy DNEWS was designed to be portable from the ground up, it does not rely on obscure UNIX features. Installation easy, totally configurable without recompiling DNEWS can be configured without recompiling and all the configuration scripts have been simplified where possible. Documentated A user manual is available. Supported EMAIL support is available for help with installation and management. Speed On comparable systems DNEWS typically out performs other news software, (even the likes of CNEWS and INN in some instances), other VMS news servers don't even come close. This is partly because DNEWS uses a more advanced database to store the news items. The difference is also very noteable on smaller systems (e.g. Linux) XOVER implemented in software No xover database is created, the normal DNEWS database is fast enough to create this information 'on the fly' Streaming support Streaming NNTP extensions are built in. Strictly limited machine impact due to single threaded nature. DNEWS runs on a single process, this speeds up connect time as a process does not need to be created, and it self-limits the impact on the system. Limitations: DNEWS does not store items in the same file structure as used by INN and CNEWS, so old software which accesses these files directly will not work. ----------------------------------------------------------------------------- These instructions describe how to setup a sucking news feed, see the manual for setting up a traditional feeding mechanism. ----------------------------------------------------------------------------- (2) Installation VMS: (see below for UNIX and Windows NT) 1) FTP the files from ftp.std.com ftp/vendors/netwin/dnews... extract.com (ascii) install.txt (ascii) dnews.bck_z (binary) 2) @extract Extracts the required files from the saveset 3) Modify REGISTER_USER.COM to register a user DNEWS$SERVER 4) @REGISTER_USER.COM 5) Modify DNEWS_START.COM to define the disks news should use. (don't run it yet!) 6) $ edit sys$manager:systartup_v5.com Add a call to dnews_start.com 7) $ edit sys$sylogin: Add the symbol, see dnews_login.com 8) $ edit dnews_top:dnews.conf Modify the file DNEWS.CONF to describe your system by defining the following symbols SYMBOL EXAMPLE manager system (email address or user@site.com) nntp_feeder news.feeder.site myname news.this.place timezone nzst (new zealand standard time) diskspace 100 (space available in megabytes) mail smtp (the foreign email protocol name) confirm *.this.place Enable email confirmation when item is passed up to a feeder site. 9) If your news feeder stamps news items with a name other than the ip name you specified above, then you will need to add an exclude field to the file newsfeeds.conf to prevent your system echoing all news back to the feeder!!! (check the path header of an item to see what it is doing) 10) $ edit access.conf Grant an ip range access to your users. by name or number, e.g. *.this.place:read,post:::* 161.23.4.*:read,post:::* 11) $ @dnews_start Start the system $ @dnews_login (to define the symbol tellnews) The system will now try and get a list of news groups from your feeder site, while this is happenning it will not respond, but you can check it's progress by: $ type dnews.log When it has finished (give it 10-20 minutes), you can then try: $ tellnews status 12) Go to a PC and try out your news reader software pointed at the new system. ----------------------------------------------------------------------------- (3) Installation for UNIX: (Sucking feed) See below for Windows NT 1) FTP the files from ftp.std.com ftp/vendors/netwin/dnews... dnews_MACHINE.tar.Z (binary) (e.g. dnews_linux.tar.Z ) 2) Extract to a temporary directory in your own account uncompress dnews_linux.tar tar -xvf dnews_linux.tar 3) EDIT dnews.conf Modify the file DNEWS.CONF to describe your system by defining the following symbols SYMBOL EXAMPLE manager system (email address or user@site.com) nntp_feeder news.feeder.site myname news.this.place diskspace 100 (space available in megabytes) df The path and flags for df sendmail The path and flags for sendmail confirm *.this.place Enable email confirmation when item is passed up to a feeder site. 4) Edit your system startup script, the name will vary: On LINUX /etc/rc.d/rc.local Add a line: /usr/local/dnews/dnews_start.sh 5) If your news feeder stamps news items with a name other than the ip name you specified above, then you will need to add an exclude field to the file newsfeeds.conf to prevent your system echoing all news back to the feeder!!! (check the path header of an item to see what it is doing) 6) Edit access.conf Grant an ip range access to your users. by name or number, e.g. *.this.place:read,post:::* 161.23.4.*:read,post:::* 7) If you have changed any of the default directories, then edit all the .sh scripts to reflect the changes. 8) Run the installation script su root (You need priv to install the files start dnews) ./install.sh 9) Start the system ./dnews_start.sh The system will now try and get a list of news groups from your feeder site, while this is happenning it will not respond, but you can check it's progress by: more dnews.log When it has finished (give it 10-20 minutes), you can then try: > tellnews status 10) Go to a PC and try out your news reader software pointed at the new system. ----------------------------------------------------------------------------- (4) Installation for Windows NT, !!!! UPGRADING !!! Shutdown the server: tellnews exit Do steps 1 and 2 below Restart the server. Tell DNEWS to upgrade the database. tellnews purgelost (4) Installation for Windows NT !!! on a new system !!! (Sucking feed) 1) FTP the files from ftp.std.com ftp/vendors/netwin/dnews... dnews_nt.zip (binary) 2) Extract the files and run the install procedure (from a DOS box) Do this from your main system disk or modify install.cmd mkdir \tmp cd \tmp pkunzip \whereveritis\dnews_nt.zip (for new systems) install.cmd (or for upgrading) upgrade.cmd del \tmp\*.* cd \dnews 3) NOTEPAD \winnt35\system32\dnews.conf Modify the file DNEWS.CONF to describe your system by defining the following symbols SYMBOL EXAMPLE manager jbloggs@here.com (email address or user@site.com) nntp_feeder news.feeder.site myname myntname.this.site diskspace 100 (space available in megabytes) confirm *.this.place Enable email confirmation when item is passed up to a feeder site. 4) If your news feeder stamps news items with a name other than the ip name you specified above, then you will need to add an exclude field to the file newsfeeds.conf to prevent your system echoing all news back to the feeder!!! (check the path header of a news item to see what name it uses) 5) NOTEPAD \dnews\newsfeeds.conf and add an smtp host so your system can email you log files, and also send email confirmations to users etc. SITE mail.gateway.here.com SMTP 6) NOTEPAD \dnews\access.conf Grant an ip range access to your users. by name or number, e.g. *.this.place:read,post:::* 161.23.4.*:read,post:::* 7) Start the system In Control Panel, Double click on SERVICES and then click on DNEWS and click on START 8) Give the system a couple of minutes to get going, and then try out the management commands from a DOS box. > tellnews status It may lock up for 5 minutes while it does an initial download, this only happens the first time it is started. 9) Point your news reader software at your NT and try out your new fast news system. 10) Join the mailing lists for advice an update information, and don't forget to register :-) tellnews -register If it fails, look in type \dnews\dnews.log Then check the FAQ section below Then send email to us if you think you've found a bug, or to the mailing list if you just want advice from other DNEWS managers. ----------------------------------------------------------------------------- (5) Installing a full feed: In access.conf, give your feed site access to send you ihave messages: my.feeder.site.com:ihave:::* In dnews.conf, comment out the nntp_feeder definition and add a line: cachedall true In newsfeeds.conf Replace site $NNTP_FEEDER groups * builtin posting With site my.feeder.site groups * builtin Copying important files from an existing system: With a sucking system you can do this with the commands: tellnews getnames The active file will be fetched automatically. However if you are replacing a news system then you want the active file from the one you replace, not from your feeder site: You can safely copy these files: active -> active.dat active.times -> active.times newsgroups -> active.names (may be changed in future) If you copy the active file, you must reset it so that it doesn't think it has any items, do this with the command tellnews resetall The only way to get the actual news items from an existing system is to setup DNEWS on a second system (or on the same system on a different PORT) and then suck the entire database via nntp. Obviously to do this you need a lot of free disk space. Renaming a volume (on unix): You may wish to rename a current volume /var/spool/news to be /var/spool/dnews, to do this: cd /var/spool/news mkdir OLD mv * OLD umount /var/spool/news emacs /etc/vfstab (or /etc/fstab) (change /news into /dnews) mount /var/spool/dnews When you are happy with the new system, or you need the space: rm -r /var/spool/dnews/OLD (XMIT (Setting up full feeds) This is necessary when you want to send a full feed onto another site. If you are a leaf site then you DONT NEED TO DO THIS !!!!!! First add entries to your NEWSFEEDS.CONF file, this creates the file site_name.feed, then you need to setup a timed job to send those items to the other sites using NNTP IHAVE (or streaming extensions) You should set all groups as cached, in dnews.conf add a line: cachedall true XMIT (On unix) Add lines to your rc.local procedure, e.g. cd /usr/local/dnews ./xmit send.to.site.name -at "*2" "*" ./xmit send.other.site.name -at "*7" "*" XMIT (On Windows NT) On windows NT you need to setup each xmit job as a service, to do this use the program ADDSVC.EXE which came with the dnews distribution to add a service for each outgoing feed, e.g. (see setupsvc.cmd) addsvc -add dxmit1 xmit.exe "dxmit1 site.name.edu -at *5 *" addsvc -add dxmit2 xmit.exe "dxmit2 site2.name.edu -at *5 *" Then from CONTROL PANEL, SERVICES, and start the feeds. XMIT (On VMS) See RUNXMIT.COM ----------------------------------------------------------------------------- (6) Recommended news readers: For PC's Netscape's built in reader. WINVN Trumpet (old versions are slow, get a new version) Freeagent For VMS FNEWS Testing DNEWS or your FEEDER site or your OWN site by hand: VMS $ telnet feeder.site /port=119 UNIX > telnet feeder.site 119 group comp.os.vms (select a group) head (display the header) body (display the body) next (next item please) help (show valid commands) quit (exit the connection) $ ----------------------------------------------------------------------------- (7) FAQ and What if it doesn't work: ----------------------------------------------------------------------------- Index to FAQ section: Can't BIND, and tellnews sais "I can't talk to you" TELLNEWS fails TELLNEWS gives unusual error message TELLNEWS GETOLD * gives a core dump Transfer permission denied. Creating local news groups: What if DNEWS Crashes !!! FTP the complete manual in MS word 6 format from: ftp.std.com ftp/vendors/netwin/dnews/dnewsdoc.zip HINT: when reading the log files, it is easy to confuse an error message from DNEWS with an error message that dnews got while talking to your feeding site. Usually if the error looks like: Status {223 transfer permission denied} then it came from somewhere else, not your system. Can't BIND, and tellnews sais "I can't talk to you" LINUX slackware: Comes with a dummy nntp daemon installed, you must remove this so dnews can bind to the socket. edit /etc/inetd.conf (comment out the NNTP line) kill -HUP TELLNEWS fails The DNEWS process may take 1-2 minutes to initialize, so wait a bit before panicking. Check if the process is running (linux) ps -axl | grep dnews (sunos) ps -ef | grep dnews (nt) Look at services in control panel Check the log files more /usr/local/dnews/dnews.log (nt) type /dnews/dnews.log If it gets started up with the wrong PID you will get all sorts of protection problems, all the files in /var/spool/dnews/... (including var/spool/dnews) must be owned by the same user, normally 'news' Also all the files in: /var/local/dnews/* TELLNEWS gives unusual error message On vms, if the symbol tellnews is not defined, it will try and run telnet instead, this can be confusing. On Windows NT if you left the disk name out of the config file and you run the tellnews command from a different default disk then it won't be able to find all the files it needs to work. TELLNEWS GETOLD * gives a core dump Try tellnews getold "*" Need I say more? This gets me every time too :-) Transfer permission denied. This can come from one of two directions, DNEWS can give this error when a site tries to feed it new items. If you are using a sucking feed then you should stop the site that is trying to send to you from sending as DNEWS will ask for any items it wants. If you do want to allow incoming IHAVE messages, then add an IHAVE record for this ip address in the ACCESS.CONF file, and also remove the 'POSTING' flag from the NEWSFEEDS.CONF file for the ME site. The last possibility is that this error is coming from your feeding site, in which case that system manager has to fix the problem for you. Creating local news groups: If you wish to have local groups on your server, that are not on the server you 'suck' from, then you should remove the 'POSTING' flag from the feed to your feeder site (in newsfeeds.conf). But only if you can get ihave or transfer permission to send articles up stream rather than simple 'posting' access. You can add groups with the TELLNEWS NEWGROUP command, e.g. tellnews newgroup here.chat y myname Local group for chatting here.chat = name of group y = Normal group (m = moderated) myname = Just a record of who created the group (one word) Local group for chatting = description for active.names file. To stop your local group from being sent up stream, you would change the line in your newsfeeds.conf file: groups *,!here.chat,!here.secret.* NOTE: KNOWN BUG, with version 2.0 items will still be sent upstream if you have left the 'POSTING' keyword in your feed. This will probably be fixed in a future version What if DNEWS Crashes !!! Don't Panic! (in large friendly letters) It is a design goal of DNEWS that it should never never never never never crash. We have now built in some special debugging options so you can help us track down the problem if this should happen on your machine. So, if it crashes, do this: Edit dnews.conf and change the debugging lines to: loglvl flush debug_rotate 2000 Then start the system, and the next time it crashes, email dnews.log & dnews.conf & newsfeeds.conf To us at: netwin@world.std.com Together with any other facts that you can give us, e.g. If you are sucking news or getting a full feed. If you are using xmit What systems and news readers are reading from you, (e.g. tin, trumpet, pc's only, whatever...) At what time of day it crashes. any other clues... Many thanks for your assistance in this. ----------------------------------------------------------------------------- (8) Using other TCPIP stacks on VMS ----------------------------------- Only the multinet driver has been tested. The ucx driver has been compiled and will probably work with very little effort. To build a new TCPIP driver: $ edit nntp.c (Add a section to include the header files for your version of tcpip, ifdef it in some obvious way). e.g. #ifdef MULTINET #include "multinet_root:[multinet.include.sys]socket.h" ... #endif $ edit n.com (Change the compile line so it defines the symbol that you used above to distinguish your tcpip software AND change the name of the object file too) e.g. $ cc nntp.c /define=("MULTINET"="TRUE") /obj=nntp_multi.obj $ edit l.com (Add a section to link to your tcpip stack, you will need to change the name of the nntp_XXX.obj file name and probably the socket library name.) Try and compile it and link it: $ @N $ @l multinet all Most likely it will fail because of some conflict between names e.g. socket_close(), or simply close(), add ifdefs to NNTP.C to correct for this. Once you have it working, email the files nntp.c and l.com and n.com to us and we will maintain and distribute these changes for others. netwin@world.std.com ----------------------------------------------------------------------------- (9) Mailing list (Announcements) (discussion list below) --------------------------------------------------- You can join the dnews mailing list by sending a message to: maiser@emagic.co.nz Containing one line: subscribe dnews This is a moderated mailing list, it's only function is to announce new versions of dnews and to disseminate up to date information on installation problems, bugs, new features etc to people who manage news systems. You will not be flooded with mail from this mailing list, it will probably average 1-2 messages a month. Mailing list, (Discussion) -------------------------------------- If you want to 'chat' about DNEWS with other DNEWS users, discuss possible new features, complain or praise the wonderful support we give or generally natter to other people running similar systems, then you can join the DNEWS discussion list which is kindly hosted by Stephen White: To subscribe send a message to: dnews-request@adam.com.au Containing one line: subscribe To send messages to the list send to: dnews@adam.com.au ----------------------------------------------------------------------------- (10) Notes on compiling and porting DNEWS (unix) ------------------------------------------------ Uncompess and untar the saveset Copy a config file which matches your machine, if one does not match then find the closest one you can. e.g. (for SunOS) > cp config.solaris config.i (for LINUX) > cp config.linux config.i Edit and modify config.i as necessary. Type in make all. > make all Now follow the normal installation instructions. If you have to make changes to the config.i file, then email it to us, specifying what type of machine & OS it is for and we will include it in the next distribution. If you change source code then email us the entire source files that were changes, please don't send diff or patch files these are extremely difficult to merge from multiple sources. When making machine specific changes, IFDEF all the changes and where possible use 'feature' like ifdefs rather than 'machine' related ifdefs, e.g. #ifdef NEEDS_STRDUP ... #endif (then define NEEDS_STRDUP in the config.i file) Rather than: #ifdef LINUX ... #endif ----------------------------------------------------------------------------- (11) Updates, List of bugs/features for each version. (in reverse order) ----------------------------------------------------------------------------- 2.1a (31/10/1995) + Full release of version 2.x 2.0 Beta-5 + Added dnews.conf paramter, open_retry, it defaults to 60 minutes. This is how long dnews should wait before re-trying to open a channel to your feeder site if it fails the first time. + upgrade command changed to 'doupgrade' to avoid confusion with 'update' command. So when you upgrade from any version 1.x copy of dnews to 2.x you should enter: TELLNEWS DOUPGRADE You DO NOT need to do this with every upgrade, it is only needed once when you go from 1.x to 2.x + Fixed new feature so it doesn't get a whole list of groups unless you have more than 300 cached (feature was supposed to work in beta-2) 2.0 Beta-4 + Fixed expire so that if it is above 94% when it starts it will recheck the free disk space after deleting the first 10,000 items. + Fixed nntp command list newsgroups. + Modified memory allocation again :-) 2.0 Beta-3 (26-Oct-1995) + Fixed bug in xover introduced in Beta-2 2.0 Beta-2 (24-Oct-1995) + dnews.conf item_max defines how large an item dnews can process, if an item larger than this is recieved it will be rejected. Increasing this can waste memory. The default is 1000000 (1mb) Note: in newsfeeds.conf there is also a setting for rejecting large items per feed rather than globally. + String allocation routines re-written to allow memory compaction on the fly, also minor changes to indenting style to solve all other memory problems. + Update made more intelligent so it doesn't get a list of newsgroups every 10 minutes unless you have more than 300 news groups cached. + New command, tellnews getgroups, which will force an update of group names which won't happen automatically if you are using less than 300 cached groups :-) 2.0 Beta-1 (22-Oct-1995) NOTE: After installing type in: tellnews upgrade (now DOUPGRADE instead) + New database Format, note the database will be upgraded 'on the fly' however, it is recommended you do a TELLNEWS UPGRADE to make sure the entire database is upgraded, and performance will not be good while this is happenning, so try and schedule it for off-peak time. + File IO improved to handle much heavier loads and improve xover performance when groups are heavily cross posted. + The following NNTP commands all speeded up by about a factor of 10, NEWNEWS, NEWGROUPS, GROUP. + History rebuild fixed (tellnews addlost) + XMIT exiting when it can't connect fixed. + Log files flushed more completely + Timeout of idle channels now settable in minutes (TIMEOUT NN) in dnews.conf + Two new settings to clearly specify how cached groups should be dealt with: cachedonly true (don't allow items into non cached groups) cachedall true (pretend all groups are cached) The first one can be used to emulate a sucking feed when items are being sent in with IHAVE. The second one is for FULL feeds to prevent any 'downloading' messages appearing. + Case is now preserved in group names, I don't like mixed case group names but they exist so DNEWS will now deal with them, however, it's matching is non case sensitive, (like NT file names). + New command TELLNEWS FIXGROUPS which rechecks the number of items in each group. (this doesn't expand the range of numbers use addlost to do that) + Modified memory allocation routines to avoid common operating system bugs, resulting in much lower memory use. + Fixed bug with running out of file handles if the feed site isn't responding. + Changed log files. There are now three, dnews.log (all log messages) dnews.in (Log of incoming articles) dnews.out (log of outgoing articles and email) The loglvl affects what gets stored in dnews.log debug_rotate can be set to prevent log files from getting too big. + TELLNEWS ROTATE command added to rotate log files. This also happens once per night automatically. Files are renamed: dnews.log -> .log2 -> .log3 -> .log4 -> (deleted) + New dnews.conf setting, ACTIVE_STATIC TRUE, will stop new groups from being created by the sucking feed. (good if you don't want 20,000 empty news groups slowing things down. + Newnews command fixed, it was not responding with the correct status. + Config parameter. POSTONLY TRUE, which stops items from being posted locally until they come 'back' from the feeder. (this is the way it used to work until version 2.0) The advantage of the new default is that you can have local groups and they will work even with a posting feed. + If WinVN crashes every time you try and read a newsgroup then type in. tellnews fixrange WinVN gets upset if DNEWS reports an incorrect number of items in a group and DNEWS can get this number wrong in rare circumstances usually just after upgrading. + Maximum number of newsgroups increased from 20,000 to 35,000. Note: Just because DNEWS can handle it, doesn't mean the pc news readers can, if you look in one of these large active files you will find an awful lot of crap, I suggest you save memory and bandwidth by removing this rubbish. 1.1g (30-Sep-1995) + New mailing list for discussion, send to dnews-request@adam.com.au + Added config setting NODNS this will stop dnews from doing reverse name translations. If you find your system takes 30 seconds to connect then try this setting, it could be your reverse name translation server is not working. This only affects access.conf, you will have to put 'numbers' in to control access instead of names. + Fixed bug in expire and purgelost. + Added 'TELLNEWS ADDLOST' command, this will restore the history file if it is deleted. (You don't need to delete it first unless it is corrupt) + *** Upgrade procedure, I recommend after upgrading to 1.1g you type in: tellnews purgelost On a system with many gigs of news this may take 24hours to run. (the system will be very slow while this is running) Then use the command: tellnews setused nnn To set the current disk usage correctly (nnn=MB used) 1.1f (27-Sep-1995) + Fixed bug with header records containing tabs being returned by xover or xhdr incorrectly. 1.1e (26-Sep-1995) + Fixed bug in body command, if body is empty the server crashed. (although this is rare as empty body messages are not accepted it can only happen when the database is corrupt) + Fixed free disk space display on NT + Added reporting on memory allocated + Added LOGDIR_MIN to config files + Added TELLNEWS STATS command. + Fixed History memory usage display + Fixed 'mode reader' command, it had a trailing space and some news servers didn't like that. (thanks to S White for finding this) + Fixed bug with the 'cached' groups, they were not being 'reset' as cached when users read items. (bug introduced a couple of version back) 1.1d (20-Sep-1995) + Fixed expire problem (with deleted groups) + Removed code that prevents ihave incoming when outgoing feed is posting (but this is still probably a bad idea) + Fixed memory leak in NT version. 1.1c (14-Sep-1995) + Fixed remaining memory leaks. + Changes default FEED_READER to TRUE. 1.1b (Internal only) + Fixed tellnews command when port is not 119 + Fixed bug when expring if no items in system at all. + Added FEED_READER TRUE OR FALSE, to force the 'mode reader' command to be sent, or not sent. + Added maxcross flag for limiting crossposts in newsfeeds.conf + Made major improvements in memory allocation, greatly reducing memory usage. + Added debugging option DNEWS_ROTATE 1000 + Fixed bug if the right/wrong slash is used in dnews.conf on NT 1.1a (6-Sep-1995) + Fixed possible bug with very long group names. 1.0e (Internal version) + Fixed possible bug with multiple simultaneous incoming ihave feeds + Fixed possible bug with items cross posted to > 200 groups + Fixed possible bug with incoming items corrupting memmory. + Fixed bug with tellnews.pass not being accessible after it runs out of disk space. + Extended newsfeeds exclude command to allow a list of sites e.g. exclude feeder1.site,feeder2.site 1.0d (Internal version) + Fixed NNTP DATE command, required by TRN + Fixed NNTP responses for list commands for TIN + Added dnews.conf paramter PORT to run the server on a different port. + Added dnews.conf NNTP_USER, NNTP_PASS user and password for feed site + Fixed bug internal mail sending system (NT & VMS not saying HELO) + Added NNTP extension list active x.y.z + Added config, LOGUSE ON, enables reader logging to used.log + Added config, CACHEDONLY ON, stops messages from going into groups that are not cached. Use this to make an ihave feed become partly dynamic. 1.0c (22-Aug-1995) + Made feed and mail queues higher priority than background suck entries. + Fixed major bug in internal feeding code which could loose local posts if the system was under load when it tried to send them. + Fixed possible crash during expire if history file was corrupt. 1.0b (20-Aug-1995) + Fixed tellnews reload so it reloads dnews.conf, access.conf and newsfeeds.conf. Also made expire.conf reload automatically. + Fixed rejection message if nntp access is not permitted. + Fixed display of downloading message for new groups on NT. + Correction made to default access.conf + Updated Documentation 1.0a (14-Aug-1995) + Silently reject cancel messages which don't have a message id or that have 'cancel' with no spaces. + Added streaming extensions to DNEWS server check takethis mode stream + New xmit, a hi speed nntp IHAVE feeding program this allows DNEWS to be used on non leaf sites. + dnews_start now takes ownership of (spool) /var/spool/dnews directory as the correct usercode to run dnews under. + Modified startup scripts to change directory before starting DNEWS + Windows NT version created. + Changed config file processing so it is not TAB sensitive. + Fixed bug with tabs in dnews.conf causing problems. + Log files flushed early on in startup, so you can see if its going. + Startup and generate speeded up, this was causing DNEWS to lockup for periods of up to 60 seconds, now there is virtually no lock up. + Corrected expire.conf, settings for keep and default were mixed up. + Modified control.conf so it doesn't generate as much email. + Group command now shows correct number of articles in a group. + NT changed file names /aux/ into /a_x/ because NTFS does not allow a file called aux (strange system) 0.9d (Wide BETA release 2) + Fixed bug which prevented news groups from being added. + Added missing nocached.body file to distribution. 0.9c (Wide BETA release) + Socket error's trapped correctly, this was causing the process to dissappear when a connection was badly closed at the other end. + New articles added after an expire run were indexed incorrectly. + Messages tidied up + Control mail messages now contain "done" or "logged only" + Pause message now contains status information. + Inactive sockets closed even when data still pending on output. 0.9b First ALPHA testing release ------------------------------------------------------------------------- Copyright & Disclaimer ------------------------------------------------------------------------- The software DNEWS is Copyright (C) 1995 NetWin LTD, New Zealand, All rights reserved. The software remains the sole and exclusive property of NetWin at all times. This software and the accompanying files are sold "as is" and without warranties as to performance of merchantability or any other warranties whether expressed or implied. No warranty of fitness for a particular purpose is offered. ------------------------------------------------------------------------- DNEWS is an extremely complex piece of software. NetWin will make reasonable efforts to solve any reported problems but we must limit our legal liability for obvious reasons.