Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNCHRONET    |    Rob Swindell fetishistic worship forum    |    43,341 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 43,312 of 43,341    |
|    Dumas Walker to DIGITAL MAN    |
|    Re: letsyncrypt issue    |
|    16 Feb 26 09:27:23    |
      TZUTC: -0500       MSGID: 74923.sync@723:320/1 2df983f6       REPLY: 55900.sync@1:103/705 2df85fb0       PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0       TID: SBBSecho 3.37-Linux master/160d568ce Feb 16 2026 GCC 12.2.0       BBSID: CAPCITY2       CHRS: CP437 2       FORMAT: flowed       > > I can only assume that came from the host end as I only saw that response       > > the one time it connected. The other few times, when it got other errors       > > or timed-out, that erroneous address didn't show up.              > Simple turn off TLS in the IRC client and it'll use TCP port 6667 (didn't I       > already explani this?) and work. Or heck, just use the IRC option from the       cha       > menu on your own BBS!              Yes, you explained it in a message that I read after reading and responding       to this one. ;)                      * SLMR 2.1a * EBCDIC: Erase Backup Chew Disk Ignite Cards       ---        þ Synchronet þ CAPCITY2 * Capitol City Online        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187       SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 700 840 860 880 226/30       SEEN-BY: 227/114 229/110 112 134 206 317 400 426 428 470 700 705 266/512       SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58       SEEN-BY: 633/280 712/848 902/26 5075/35       PATH: 103/705 218/700 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca