Restore removed ChangeLog_2023
Add Linux Mint support to SETUP.sh
Add support for setting a password on the bbs (newuser) account to enable new
Remove obsolete BBS list menu from example menus/textfiles. Correct URL for
v1.1.0 - Missed updating germandu.txt
v1.1.0 - Re-add the option to ask new users if they want ANSI color.
v1.1.0 - Add a few missing function declarations.
v1.1.0 - Add missing files.
v1.1.0 - Re-implement line editor for messages
Issues with install script
v1.0.9 - Re-implement plain ASCII support.
mbsebbs-1.0.8.8 released
Building 1.0.8.8 under Linux
v1.0.8.8 - Don't add connections to netmail areas/fix missing echomail tearline.t
v1.0.8.7 - Supress tearline in local message areas option/mbmsg updates.
Update to FTSCPROD.020 as released by the FTSC.
I have just tried this setting up (in order : elist test 2 ELIST-TEST-2 then changing 26 to remove the default uplink and 27 setting 32. The path is created as well as the four files. You do need to fill in in the echo set up fields 1, 2 so that the path is auto created and your example does not show this. There is no defect showing for this
Message group area templates not populating fields
Local mail area template not populating fields
Add new FTSC Product Code listing
Update FTSC Product Code listing
v1.0.8.6 - Fix message deleting bug/add ability to reduce frequency of clock & status
fixed in svn and vers -> 1.0.8.6
Non-Sysop users can only delete a message when they are the sender of that message, but not the recipient
Home
mbse 1.0.8.5a has been released at SF under files. The "a" part also includes a fix for scripts / mbsedos.
mbsebbs-1.0.8.5 released
Read the file INSTALL and follow it. This involves downloading the mbse archive which is currently for 1.0.8.2 (my mistake as I have not updated it) although the code base in GIT and SVN is for 1.0.8.5. Download and install required additional packages as discussed in README.Ubuntu or any of the others that match your nix distro or closest to it but where possible use your distro's package manager. Follow the notes in INSTALL noting what user to be using at each step. If you follow these instructions...
In order to run mbsebbs you must set the global variable $MBSE_ROOT. This variable must point to the root directory of the bbs structure. The main configuration file config.data must be present in the ~/etc directory.
Issues with install script
v1.0.8.5 - Fix internal full screen editor crash/segfault.
Internal editor segfaults & disconnects after exiting "Help" screen
Thank you for the detailed bug report and fix.
Internal editor segfaults & disconnects after exiting "Help" screen
Fixed in v1.0.8.4. The message area duplicate checking code needs further work/testing, and has been temporarily disabled to fix this issue.
v1.0.8.4 - Fix problems saving new message areas. Disabled duplicate checking
Cannot create a new message area on 1.0.8.3 on fresh install
Confirmed issue with the duplicate area checking; will be fixed ASAP.
Thanks for the quick reply. Unfortunately, I refreshed the whole install and removed everything from 1.0.8.3 when I saw 1.0.8.2 worked. However, out of memory, I know the permissions on the data files were right since I checked them. Weirdly, only the Message Areas couldn't get created, everything else appeared to be working. As for the build process, it was finishing with a success but I don't have the logs for the build anymore. Since it was pretty consistent, I'll try to redo the whole thing with...
A few silly questions : When you compiled mbse did you get any error or warning messages ? If in doubt, go in to the source folder (mbsebbs) then run ./configure, make > build.log 2> build.err You may well have to do the above as root, so follow the INSTALL doc details. Now less build.err and there should be NO errors and not too many warnings Now less build.log should be clean and at the end msg for leaving script directory. Check status of data files so ls -la etc/*.data All owned by mbse.bbs and...
Cannot create a new message area on 1.0.8.3 on fresh install
Fix incorrect display text when creating site documentation in mbsetup.
fix: potential fix for dupe area checking (experimental code)
In one case, the crash is related to the email mode not being set to an ISP or no-ISP in internet mail config. I have applied a fix in the git code for that to emit "Undefined" for invalid answers. If you have a chance to test the code, please do.
fix: segfault when creating site docs
It'd be nice to be able to do that for external logging purposes (such as having an alert pop up on the system's desktop or another computer on the LAN). -- Sean On Fri, Feb 3, 2023 at 9:15 AM Michael Dillon gsvalore@users.sourceforge.net wrote: The current codebase now has a script that will be called when a new user joins the BBS. This however does not trigger when a user logs in that's existing. Should this be extended? [tickets:#14] Add New User notification Status: open Milestone: 1.0.7 Created:...
The current codebase now has a script that will be called when a new user joins the BBS. This however does not trigger when a user logs in that's existing. Should this be extended?
refactor: fixed call to exec to use fork as parent is still needed.
refactor: adjusted previous commit to use a cached value from getenv
fix: segfault in mbindex
changed: nuscript.sh is now nuscript (for conventions) and MBSE_ROOT is passed to the script
Update: BACKBONE.NA is now updated monthly at 23:30 on the 1st of each month and daily if any changes happen in the Elist system ( see echo ELIST ). This system produces one of two archives that contains this file amongst others and are sent to file group ECHOLIST. These archives are replacements from any previous created one and NOT accumlative. Along with the BACKBONE.NA is BACKBONE.RPT a full detailed listing of all echos as well as a directory containing the rules and one for the descriptions...
Fix missing ChangeLog_2022 in distribution tarball.
changed: re-enabled duplicate checking
v1.0.8.3 Run script after new user logs in/duplicate message area checking.
Tested with 1.0.8.2 working for distro Mageia v8 X64 and built with clang. Is this cleared with same versions ?
After upgrade from 1.0.7.24 to 1.0.8.1: msetup corrupts etc/mareas.data, leaves mareas.temp behind
mbsebbs 1.0.8.2 released
For netmails, I have a different NETMAIL echo for each AKA I will use, e.g., primary is for 2:250/1 Another is for 2:25/1 and lastly one for 2:25/21 when the same system used the later, but now all work for it, is now on a different system. This is used with Golded, and it seems to work. Switching the AKA to use with Golded does not work as it will always take the default for that Echo area regardless of the one I select, and the only other way is to have a golded.cfg for each one that is set up...
Note that the duplicate MAINFRAME areas I strongly suspect are over writes from other file areas and sorry no, I do not know what ones were overwritten (if at all). All very confusing.
Netmail packages not tossed to designated areas, remain in var/inbound/ - affects all versions >= 1.0.7.22
The netmail not tossing issue has been fixed in v1.0.8.2, and you may enable the automatic tossing of .PKTs from the unprotected inbound (1.11.21) if you desire. The mareas.data/mareas.temp issue is a known problem; Mike has temporarily disabled the duplicate message area checking feature until he gets this bug squashed.
v1.0.8.2 -- Fix bug in Auto processing of NetMail from unprotected inbound.
MBSETUP SegFault
Just pulled your latest commit and the issue is gone now. Thanks for providing a workaround that fast!!
change: disabled duplicate checking for further testing.
For the time being I have reverted(disabled) the duplication checking code due to some obscure errors. It'll take more time to figure it out but this behavior will be more consistent with previous versions now. It has already been pushed to the repo for now.