NOTES TO V6.5 Version 6.5 of the CBBS now allows wild-card entries in the STATES.MB file. Comments are also allowed as long as a space is put between the routing and the comments.. EXAMPLE: WA4ONG.VA.USA.NA QSL Server BBS. If a user does a 'P WA4ONG' the entire line will display to him. The 'P' Command searches your user file first, and then STATES.MB for any match. A sysop doing a 'RM' now sees all the headers in the message. Sysop listing now truncates the title to fit a single line. A sysop can kill up to four messages at a time. A few bug fixes and a little less memory is used. Parsing is now done a little differently and you will store the bid and the original bbs bid in the bid file. Make sure you check the bid file more often as it will grow at a faster rate. NOTES TO V6.6 Users are allowed the send multiple command (S!). You can create a list file for special users that want the same message sent to multiple bbs's. Forward message size limiting is now operation. ( <>0120 3000 ). Look in the manual for proper operation. Held mail is not seen by users. Also if you receive a message with your header in it (meaning you had the message and forwarded it out) the status will be hold. This stops ping-ponging a message back and forth between bbs's. The forward file can now be changed to another file. At the end of the forward file putting YF0024 \MB\BBS\TEMP.MB will change the forward file to TEMP.MB.. Another wild card is created. (!) The '!' is used to match a digit only in the forward file and states.mb. So DU!* will match DU etc. So DUMB will not match as the 'M' is not a digit. Should make it easier for foreign call matches and Canadian Zip codes in the forward file. NOTES TO V6.7a (AMIGA version) I have added a sort of ABORT function in CBBS so that users who get a long listing from any of the 'L' commands can cancel the output. They simply type a carriage return while receiving data (they do NOT type "ABORT"). CBBS will stop sending any more output to the TNC and will return to the CBBS prompt. But remember that the TNC may have buffered a few kilobytes of data so the program may not stop the instant the carriage return is sent. Please read the README file about the two options #C and #E. You should select only ONE of them. V6.7 has better control over how to kill bulletins. See Chapter 2.1 in manual.bbs and the changes in config.mb on the disk. V6.7 will talk to the mailbox in a KAM V3.01 and will correctly ask for reverse forwarding (this would not work with V6.6). I have added a small feature whereby a message from a KAM V3.01 that looks like a bulletin will be automatically changed into one and a BID will be allocated. The standard IBM version of CBBS does not do this. It leaves the message as a personal and then puts it on hold so the SYSOP has to release the message. V6.71b has new versions of mbrestm and prtlog. Mbrestm originally only permitted the sysop to recover mail files from a crash if there were no more than 500 active files to be recovered. A large BBS can easily exceed this limit so I have increased it to 2000 and an error message is produced if this limit is exceeded (the distribution version crashes if the limit is exceeded). I have fixed two bugs in prtlog, one which caused it to produce incorrect uptimes for the system and the other which would cause all time computations to be wrong if the two dates involved were more than two days apart. These have been fixed and I have also added a third page of output which provides 'accounting' on a per user basis. The information printed is: callsign, total connect time and total number of connects, total number of Read and Send commands, and total number of forwarding sessions. V6.71b has a modification to the routine that renames log.mb at the end of the month. The IBM version adds only the month to the renamed log file. V6.71b adds the year as well so that, for example, it will produce a log file with the name log9011.mb at the end of November 1990, instead of just log11.mb.