Stable release

v0.9.11aHandshake

Released 2026-09-25, 24.3 MB.

Notices

Behaviour that changed underneath you. Nothing to run, but worth reading before you update.

  • warningAfter updating, run node src/tools/bootUnit.js as the user the BBS runs as. If it reports a problem, run node src/tools/bootUnit.js --install. A board set up with pm2 startup has a boot unit that names one Node version, and under nvm it stops starting the BBS at boot once that version is removed. The tool writes a unit that finds Node when it starts instead, asks for sudo to do so, and restarts nothing: it prints the command to restart when you are ready, which restarts the BBS, so close the board first with node src/tools/maintenanceMode.js --on if callers are online.
  • infoMessages already received keep the layout they were given when they arrived, so ASCII art, MealMaster recipes and other column-aligned posts will still show rows run together until they are rendered again. To repair them, run node src/tools/maintenance.js --regen-html with the worker running (add --area SHORTCODE to do one area first). It can take a while on a large message base; it changes nothing but how stored messages are displayed.
  • warningSince 0.9.7a, files arriving by file echo were refused as loops whenever the TIC listed this system under Seenby, which every uplink does, so most inbound files never reached their areas. This release fixes that for new files. Files refused within the last ftn_keep_tossed_days (7 by default; ftn/tossed/ is purged after that) are still in ftn/tossed/ next to their .tic, and the system log names each one with "loop" and "already lists". To import one, move the .tic and its file back into ftn/in/ and the next toss takes it. For nodelists and other files that replace an earlier one, only the newest needs moving.
  • infoLog files are now rotated every night at 23:59 into logs/production/archive/YYYY-MM-DD/, and archives older than log_retention_days (30 by default) are deleted. The first rotation archives everything your logs hold so far under that night's date, so that history is deleted 30 days later. To keep it, copy logs/production/ somewhere else first, or raise log_retention_days (0 keeps every archive). node src/tools/rotateLogs.js --dry-run shows what a rotation would take.

Canectic BBS v0.9.11a

Files arriving by file echo reach their file areas again. Every board that carries file echoes should take this release, and so should its downlinks.

Released 2026-09-25 (Handshake).

Highlights

Inbound file echoes work again. Since 0.9.7a, nearly every file an uplink sent was refused as a loop and never reached its file area, and nothing reported an error: the refusal was logged as routine and counted as a duplicate. Files arrive normally again, and a refused one is now reported where you will see it. The most recent refused files can still be recovered; see Upgrading.

If your downlinks run Canectic, they need this release to receive your files. A board on 0.9.7a to 0.9.10a refuses files from its uplink for the same reason, whoever that uplink is.

File echo processing has its own log, tic.log, with every file received or sent and the reason for any refused. Failures, refusals and each run's totals still appear in system.log.

Log files are rotated every night. Each log is compressed into logs/production/archive/ and started afresh, and archives older than 30 days are deleted. Until now every log grew for ever.

Turning a purge off now stops it. Setting a retention to keep for ever left the nightly purge running with its old number of days, deleting what you had asked to keep.

Read at 40 or 80 columns on a phone, and ASCII art keeps its shape. The web reader has a 40 | 80 switch on phones, art is shown at 80 on its own, and drawings, recipes and tables no longer have their rows run together.

The Update page shows a release's upgrade notes before you update, and waits for you to tick that you have read them when any is a warning.

A tool to keep the BBS starting at boot through Node upgrades: node src/tools/bootUnit.js --install.

Upgrading

From 0.9.10a the update applies itself. Four things are worth knowing afterwards:

  • Recover files refused since 0.9.7a. Those that arrived within ftn_keep_tossed_days (7 by default; ftn/tossed/ is purged after that) are still in ftn/tossed/, each .tic next to its file, and the system log names each one with already lists followed by your address. To import one, move the .tic and its file back into ftn/in/ and the next toss takes it. Every file you import is also sent on to your downlinks, so for nodelists and other files that replace an earlier one, move only the newest.
  • Your existing logs are archived on the first night and deleted 30 days later. The first rotation puts everything your logs hold so far into one archive dated that night, and it is removed with the rest once it is older than log_retention_days. To keep that history, copy logs/production/ somewhere else first, or raise log_retention_days (0 keeps every archive). node src/tools/rotateLogs.js --dry-run shows what a rotation would take.
  • Check how your BBS starts at boot, once. Run node src/tools/bootUnit.js as the user the BBS runs as, and node src/tools/bootUnit.js --install if it reports anything. A board set up with pm2 startup stops starting at boot once the Node version it names is removed, which under nvm happens on an ordinary Node upgrade. --install asks for sudo and restarts nothing; the restart it prints restarts the BBS, so close the board first with node src/tools/maintenanceMode.js --on if callers are online.
  • Repair the layout of messages already received with node src/tools/maintenance.js --regen-html, with the worker running (add --area SHORTCODE to try one area first). ASCII art and column-aligned posts that arrived before updating still show their rows run together until then. It can take a while on a large message base, and changes nothing but how stored messages are displayed.

Coming from 0.9.9a or earlier? The notes for the releases you skip apply to you too. The Update page lists every one that concerns your board before you update, and they are in the 0.9.10a release notes, https://canectic.tranqsoft.com/releases/0.9.10a/notes.

Changes

File echoes

  • Fix: files sent by an uplink never reached their file areas, and nothing reported an error. A file whose TIC listed your system under Seenby was refused as a loop, but an uplink lists every recipient there before sending, so nearly every inbound file was refused. Only Path, which records the systems a file has actually passed through, is checked now.
  • Fix: a file that replaced one of the same name was saved as NAME_1.EXT. Infopacks re-released under their own name, and nodelists a year on, landed beside the file they replaced under a new name, and the next release could not find them to replace, so an area slowly filled with _1, _2, _3 copies. A replacement now takes the old file's place, and the old file is deleted once the new one is recorded. Copies already renamed this way are left as they are.
  • Replaces with wildcards works. Replaces NODELIST.* replaced nothing, so every version stayed. * and ? are now honoured, as long as the pattern names at least three characters of the filename before its extension: *FOO.ZIP works, while *.* or *.ZIP, which would empty the area, are ignored and logged.
  • Fix: a file could be sent back to a system that already had it when that system's address appeared in the TIC with a network domain (@fidonet) or a .0. The same fix means a TIC from such an address is recognised as coming from its peer, so its password is checked.
  • A file whose record could not be saved now goes to ftn/bad/ with its TIC, rather than staying in the area directory unrecorded while the TIC failed again on every toss.
  • New: tic.log, described above.

Messages

  • New: read at 40 or 80 columns on a phone. The web reader sizes text to 40 columns on a phone so it is readable, which breaks anything laid out for 80, ANSI art above all. A 40 | 80 switch, remembered per area, now chooses, and a message recognised as art is shown at 80 whatever the switch says. Desktop is unchanged at 80.
  • Message areas and groups have a "Mostly ANSI art" setting, so an area full of art opens at 80 columns on phones. Set it on the area, or on a group for every area created in it, with Push Group Defaults for areas that already exist.
  • Fix: ASCII art and column-aligned posts had their rows run together. Lines long enough to look like prose were joined into paragraphs, so a drawing, a MealMaster recipe's dividers or a table of figures became long lines that then wrapped. Lines laid out with columns or wide gaps, or drawn mostly from punctuation, are now left as written.
  • Fix: adding a message area with a - in its short code did nothing, with no reason given. A short code may use letters, digits and underscores, up to 52 characters; the form now says so before submitting, and a refused area returns to the group page with the reason. A message group that cannot be created now says why too, and notices on the group page, such as Push Group Defaults results, appear there rather than on a later page.

Administration

  • New: log files are rotated daily at 23:59 into logs/production/archive/YYYY-MM-DD/, compressed, with archives older than log_retention_days (30, or 0 to keep them all) deleted. The settings are under Logging on the configuration page. node src/tools/rotateLogs.js rotates now, and --dry-run shows what it would do.
  • Fix: turning a purge off did not stop it. Setting a retention to keep for ever (0, or 999 for tossed packets) left the nightly purge deleting with its old number of days: tossed packets, notifications, bad echomail, the inbound and outbound file logs, the netmail relay log, mailer session history and update check history. A purge that is switched off is now removed at the next restart, and a change of days applies that night rather than after a restart.
  • Fix: date columns in tables did not sort by date. Dates appeared in several formats and sorted as text, so 10/1 came before 9/30. Every table now shows 2026-09-22 17:57:03, or just the date where that is all there is, and sorts on the actual time. This covers the file logs, the netmail relay log, API tokens, echolists, filebones, nodelists, message and file areas, users, the private mail inbox and file lists.
  • Times in tables show in your own timezone, following your browser's clock; hover over a time to see the zone.

Installation

  • New: node src/tools/bootUnit.js --install keeps the BBS starting at boot through Node upgrades. The unit pm2 startup writes names one Node version, so under nvm the BBS stops booting once that version is removed. The tool installs a small wrapper, writes a unit that uses it (keeping your existing PATH and saving the old unit beside it) and enables it, restarting nothing. node src/tools/bootUnit.js on its own checks a board and says what is wrong; the Update page shows the same warnings. See "Surviving Node Upgrades" in docs/sysop/INSTALL.md.
  • With that unit, the BBS moves to a new Node on its own at boot after a Node upgrade, where before it needed a pm2 save and did not start at all once the old Node was removed.

Updates

  • The Update page shows a release's upgrade notes before you update. A Before you update panel lists the notes that concern your board, from every release you would skip, most serious first, and the Update button waits for you to tick that you have read them when any is a warning. The notes are verified against the release's signed checksum list before being shown, and stay on the Update page afterwards, since several are instructions for after the update. node src/tools/update.js prints them too, and needs --acknowledge-notices to apply when one is a warning. See "Upgrade notes" in docs/sysop/UPDATES.md.
  • The "is available" notification says how many upgrade notes apply to your board.
  • This update is the first to keep its notes for afterwards. The panel before the button appears from the next update on, because the page you update from belongs to the release you are running.
Version
0.9.11a
Channel
Stable
Node
22.0.0 or later
Upgrades from
0.9.0a or later
Migrations
0001-menu-layout0002-msgid-tuple-split0003-qwk-conference-blocks0004-settings-provenance0005-refresh-stale-version0006-normalise-body-text0007-netmail-seenby-text
SHA-256
e83e5f17a5da8a5ce51738a105a72a6df6d2caa322749bd5ba9b2d7e917d7248
Files
metadata·manifest