+-+-+-+ Beginning of part 4 +-+-+-+ X BBOARD April 23, 1990 X`012 X X X X X X X before BBoard will accept a SHUTDOWN command. Normally, BBoard X should not be shut down until all incoming mail has been stopped. X This will prevent Jnet delivering mail to the BBoard user X account, rather than the BBoard Jnet hook X X The only way to ensure that there will be no incoming mail is to X JCP STOP the incoming links. BBoard will use this list to X determine which links are possible incoming Jnet links. X X Col Len Description X --- --- ------------------------------------------------------ X 1 8 Jnet link that must be inactive before BBoard will X SHUTDOWN. X X :links X JCSVAX1 X ! Note: X ! JCSVAX1 is St. Peter's College only link to Bitnet. X X X Control Section - :ignore X X This section tells BBoard which user and node combinations should X be ignored for interactive messages. This is intended to allow X messages from LISTSERVs or MAILERs to be ignored. X X Col Len Description X --- --- ------------------------------------------------------ X 1 8 Node to ignore. Wildcards (*, %) are allowed. X 10 8 User to ignore. Wildcards (*, %) are allowed. X X :ignore X * *SERV X ! Note: X ! We don't want to pay attention to anything from *SERV X ! (LISTSERV, VMSSERV, etc.) from any node. X X X Control Section - :log_file. X X This optional, same-line section is a file specification for the X file that BBoard will create and use to keep track of the posting X status for all conferences. X X The default is BBoard_Dir:BBoard.Notelog X X :log_file.BBoard_Dir:BBoard.Notelog X X X Control Section - :err_conf. X X - Page 11 - X BBOARD April 23, 1990 X`012 X X X X X X X X This optional, same-line section is a Notes conference name in X which BBoard will place all messages whose conference cannot be X properly determined. Messages are usually placed here because X there is no selection information in :lists. X X The default is X-Unknown X X :err_conf.X-Unknown X X X Control Section - :time_int. X X This optional, same-line section describes the time interval for X posting entries to Notes. If this time period has passed since X the last time that entries were posted (or checked to see if they X should be posted) and new entries are waiting, the new entries X will be posted. This time must be specified in VMS delta-time X format. X X The default is 5 minutes. X X :time_int.0 00:05:00.00 X X X Control Section - :count_int. X X This optional, same-line section describes the count interval for X posting entries to Notes. If this many entries have arrived X before one :time_int. has passed, the entries will be posted X immediately and the time interval will be reset. X X The default is 5 entries. X X :count_int.5 X X X Control Section - :local_ctct. X X This optional, same-line section is the VMS username of the X person at your site responsible for local BBoard control and X maintenance. This name (along with your Bitnet node name) will be X included in response to the HELP interactive command to describe X a locally-available person to contact for further information. X X :local_ctct.BEN X X X BBoard LOG File X X X - Page 12 - X BBOARD April 23, 1990 X`012 X X X X X X X BBoard logs all events (incoming files, interactive commands, X startup, etc.) to a file called JAN_SYS:.LOG. (Hook- X name is the same as the logical bboard_hook_name.) X X This file is similar to the LOGfiles created by Jnet Daemon X processes. X X X Suggested Notes Set-up X X Here are some suggestions on the set-up of Notes conferences for X BBoard. Some of these are automatically included if you use the X included tool BBOARD_MAKE_CONF.COM. X X o A person should be assigned to act as BBoard controller and X Notes moderator for all BBoard-driven conferences. X o BBoard-driven conferences should be differentiated from X local conferences in some manner. One possibility is X prefixing the Internet confernence name with "X-". X o BBoard-driven conferences should be SET /NOWRITE to prevent X general users from adding notes without direct submission to X the appropriate LIST. X o Each conference should have the BBoard controller and the X BBOARD username defined as members with moderator privilege. X If Full mode is being used, the "conference user" will also X require moderator privilege so that entries can be posted. X o Only the BBoard controller should have a mailing address X set. All other conference members (BBOARD and the conference X users) should not have mailing addresses to prevent X extraneous mail delivery. X o Create conference keywords where necessary. X o Note to PMDF Users: X You will need to make additions to two files if you have X PMDF. X Add to PMDF_ROOT:[TABLE]PMDF.CNF X jcoerce.bitnet $U%.bitnet@jnet-daemon X X Note that represents your bitnet node name. X X Add to PMDF_ROOT:[TABLE]ALIASES. X bboard: bboard@jcoerce.bitnet X This is required because SMTP mail will be delivered to a X local user. In normal situations, this would be the BBoard X user account, not the BBoard Jnet hook. The above change X forces mail to BBoard to be processed through Jnet and X perform normal delivery. X X X Example Set-Up Files and Tools X X X - Page 13 - X BBOARD April 23, 1990 X`012 X X X X X X X Sample start-up, control files and some usefull BBoard tools are X included with BBoard to use as a starting point for your X installation. X X The following files are supplied in addition to the BBoard X program itself. X X X JANTIDY_ADDITION.COM X X This file shows additions to your JANTIDY daily cleanup X procedures. These additions will attempt to perform an orderly X shutdown of BBOARD before completely cycling Jnet. X X BBOARD.CTL X X This is a sample control file which can be used as the basis for X your own configuration. X X START_BBOARD.COM X X This is a sample startup COM file to define the logicals and X start the BBoard Daemon. X X RUN_BBOARD_DAEMON.COM X X This is a sample startup COM file to purge LOG files in BBoard's X directory and begin running the BBoard program. X X NOTES$COMMAND.SAMPLE X X This contains possible additions to your system-wide Notes X command interface to improve support for BBoard. This might X require adjustment for your specific installation. The following X keys are defined by this addition: X Gold-F Attempt to determine the originating author of a X note by reading the personal name text. If an X author's net address can be determined, send mail X to the author (forwarding the entry). X Gold-K Do a SHOW NOTE/KEYWORD to determine the keyword(s) X attached to a note (useful for conferences with X keywords enabled). X Gold-P Print the current note on a locally attached X printer. This requires the NOTES-PRINT.SAMPLE file X which is also provided. X Gold-R Send an entry to the conference user (which would X then be forwarded to the list address). This is X the equivalent of FORWARD/AUTH for conferences X with conference users. X Gold-S Display the full text of the personal name for the X X - Page 14 - X BBOARD April 23, 1990 X`012 X X X X X X X author of a note. This will be the source field X that was selected as the From field in the :rules X control section. X X The Notes additions which are included will require modification X for local conditions. Comments indicate where changes are needed. X These additions were written for VAX Notes Version 2.0 and may X need rewriting for previous versions. X X These functions were written and provided by Terry Kennedy X (Terry@SPCVXA.Bitnet) who should be contacted if further X information is required. X X NOTES-PRINT.SAMPLE X X A .COM file required for the local printing of Notes, as X described above. X X BBOARD_MAKE_CONF.COM X X This is an automated procedure to create conferences and X conference aliases that will be used with BBoard. This will need X to be customized for your site before you can use it. Most of X this is relatively simple DCL and contains comments for the X appropriate sections. However, I do make the following warnings X about using this: X o You will almost DEFINITELY NEED TO MODIFY THIS for use X at your site. Let me repeat that: DO NOT USE THIS X WITHOUT FIRST LOOKING IT OVER. You'll understand why as X you read further. X o The AUTHORIZE selections are site-specific. You will X probably need to modify them for your site. X o Make sure that you have a UIC group [??????,0] for the X conference aliases (if you are using them). I do not X guarantee behavior if you attempt to use a UIC group X that doesn't exist. X o The "standard moderator list" is site-specific. For St. X Peter's College, we have three users (BEN, SYSTEM, X TERRY) that are always conference moderators. X Additionally, only two of them (BEN, TERRY) have mail X addresses. [I (BEN) am always the one running this X procedure, so I don't explicitly add myself.] X o We have disk quotas enabled for the drive on which all X of our conference aliases live. We provide 100 X permanent and 0 overdraft blocks. Since these usernames X are only used for mail forwarding, I've never seen more X than 6 blocks ever in use by them. You may want to X modify these numbers. X o You will still need to NOTES$MOVE_CONFERENCE the X conference once it's created, along with adding the X X - Page 15 - X BBOARD April 23, 1990 X`012 X X X X X X X required information to the Control File. X o For any conferences created with this procedure, the X first four topics will be allocated for a description X of the conference and for discussion about the X conference (by the moderators). X I hope that this provides a good ground-work for generating your X BBoard conferences. If you have any improvements or suggestions X for improvement, please send me your code or ideas. This is one X of the pieces of BBoard that could probably stand the most X improvement and, in the long run, be one of the most used and X most useful. X X NOTES_PURGE.COM & NOTES_PURGE.FDL X X This is an automated procedure to perform mass deletions of Notes X conferences used by BBoard. There are configuration settings X (within the file itself) for the number of days for expiring, X when to actually perform the purge, and a list of conferences X that are never to have entries deleted from them. X X The default settings for the file as shipped are 60 days, Sunday X at 4:30 AM, and the conferences X-INFO-BBOARD and X-UNKNOWN are X not to be expired. X X This procedure must be executed on the NOTES$LIBRARY node. It X will search through all X-* conferences in the NOTES$LIBRARY X directory. Any conferences which are not on the "never-purge" X list will be scanned. Any topics in that conference which are X older than 60 days (for the first entry in the topic) will be X completely deleted. X X If deleting all topics older than 60 days would wind up deleting X all topics in the conference, the last topic will be left. If X there are no topics older than 60 days, then the conference will X be passed over until the next time the procedure is run. X X After all the deletions have been made for a conference, the X .NOTE file will be compressed (using the file NOTES_PURGE.FDL) to X reclaim space in the file. The .FDL must be in the same directory X as the .COM file. X X This procedure will automatically send SUSPEND and RESUME X commands to BBoard to prevent BBoard posting to Notes while the X conferences are being purged.`032 X X The full list of set-able defaults (all of which are listed and X set at the top of the .COM) are: X expire_days - the age before which topics and replies should -+-+-+-+-+ End of part 4 +-+-+-+-+-