Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNC_PROGRAMMING    |    Synchronet/Baja/XSDK Programming    |    49,116 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 47,058 of 49,116    |
|    Rob Swindell (on ChromeOS) to Git commit to main/sbbs/master    |
|    src/sbbs3/ssl.c    |
|    08 Jul 25 21:43:38    |
      TZUTC: -0700       MSGID: 52449.syncprog@1:103/705 2cd3f65b       PID: Synchronet 3.21a-Linux master/a43ca30ea Jun 18 2025 GCC 12.2.0       TID: SBBSecho 3.28-Linux master/e2705e616 Jul 05 2025 GCC 12.2.0       BBSID: VERT       CHRS: ASCII 1       FORMAT: flowed       https://gitlab.synchro.net/main/sbbs/-/commit/1d0353858e00d5fade270854       Modified Files:        src/sbbs3/ssl.c       Log Message:       Better error reporting/handling when the ssl.cert file doesn't exist              Since "Create self-signed certificate" defaults to No, it's normal/expected to       not have an ssl.cert file in many cases and the logged errors were not very       helpful. We should probably change the default for this setting to Yes       (and have letsyncrypt.js disable it) or when auto-disable any SSH/TLS       functionality that will expect a certificate file when the file doens't exist       during initialization (startup or recycle). At least this change is a little       bit of an improvement (help to the unknowing sysop). No longer just logging       this unhelpful spew:       7/8 21:23:05 mail 0055 SEND connecting to port 25 on mail.synchro.net       [71.95.196.36]       7/8 21:23:06 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:06 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:06 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:06 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:06 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:06 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:06 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:06 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:06 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:06 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:07 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:08 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:10 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:14 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:22 mail Failed to open/read TLS certificate: /sbbs/ctrl/ssl.cert       7/8 21:23:22 mail 0055 SEND/TLS [mail.synchro.net] ERROR 'Data has not been       initialised' (-11) setting private key              Thanks to Sam Alexander (BLUEBOX) for pointing this bad behavior out.       --- SBBSecho 3.28-Linux        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 7715       SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110       SEEN-BY: 229/206 317 400 426 428 550 700 705 240/1120 5832 263/1 266/512       SEEN-BY: 280/464 5003 5006 291/111 292/8125 301/1 320/219 322/757       SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888       SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35       PATH: 103/705 280/464 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca