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,302 of 43,341    |
|    Digital Man to Dumas Walker    |
|    Re: letsyncrypt issue    |
|    15 Feb 26 14:57:24    |
      TZUTC: -0800       MSGID: 55900.sync@1:103/705 2df85fb0       REPLY: 74914.sync@723:320/1 2df83f2a       PID: Synchronet 3.21b-Linux master/a3797f107 Feb 15 2026 GCC 12.2.0       TID: SBBSecho 3.37-Linux master/a3797f107 Feb 15 2026 GCC 12.2.0       COLS: 80       BBSID: VERT       CHRS: CP437 2       FORMAT: flowed       NOTE: FSEditor.js v1.105        Re: Re: letsyncrypt issue        By: Dumas Walker to FUSION on Sun Feb 15 2026 10:21 am               > > DW> And, of course, the irc is broken, too:        >        > > DW> Looking up irc.synchro.net        > > ^^^^^^^^^^^^^^^        > > DW> * * Subject: /CN=endofthelinebbs.com        > > ^^^^^^^^^^^^^^^^^^^        > > this will never work because the hosts don't match        >        > I noticed that but that is what happend when I plugged irc.synchro.net into        > hexchat in the server name field and told it to connect. I did *not* put        > *any* info in there for endofthelinebbs.com.              irc.synchro.net is a rotating hostname, it points to *all* of the IRC servers       (and there's a lot of them). That can be seen using tools like nslookup, host,       dig, etc.:              Name: irc.synchro.net       Addresses: 2600:6c88:8c40:5b:f1d0:1:103:705        2604:880:52:866:f1d0:1:124:5016        2001:19f0:6000:94c9::68:234        2001:19f0:6000:94c9::81:241        71.95.196.34        51.75.174.224        158.220.122.223        192.138.210.158        45.32.81.241        138.197.129.1        108.242.55.251        203.191.174.253        59.167.142.49        45.32.68.234               > 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       chat menu on your own BBS!       --         digital man (rob)              Synchronet "Real Fact" #67:       SEXYZ is as a 32-bit replacement for [F]DSZ, CE-XYZ and other protocol drivers       Norco, CA WX: 59.8øF, 58.0% humidity, 6 mph WNW wind, 0.00 inches rain/24hrs       --- SBBSecho 3.37-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/112 134 206 317 400 426 428 470 700 705 240/1120 5832       SEEN-BY: 263/1 266/512 280/464 5003 5006 291/111 292/8125 301/1 310/31       SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58       SEEN-BY: 460/256 1124 633/280 712/848 770/1 902/26 5020/400 8912 5054/30       SEEN-BY: 5075/35       PATH: 103/705 280/464 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca