TZUTC: -0500
MSGID: 834.f_doors@1:2320/105 2d998fab
REPLY: 74.fido-doorgame@1:103/1 2d985302
PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
TID: SBBSecho 3.28-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
BBSID: CAPCITY2
CHRS: ASCII 1
FORMAT: flowed

 > So, the DOSBOX-X "softmodem" does support a telnet mode that may help with
 > the issue... "ATNET1" selects telnet (and "ATNET0" turns it back off).

 > The thing to be careful of is that the entire command gets otherwise ignored
 > if the substring "NET1" or "NET0" is in it, so if you're doing other init
 > stuff you need to be sure it's separate.

So when I am in the BBS program and send 'ATNET1' to the DB-X "modem" I do get
an "OK," which would make me think it supports it.  To verify this, I sent an
unknown string, 'ATBAG', and got "ERROR."

However, if I set the host mode init string to:

ATNET1|~~AT(actual init string)|

Which should send the ATNET1, wait a couple of seconds, and then send the
real init.

I then used the telnet protocol to connect and I still got the same double-CR
issue I had before.  So apparently it recognizes ATNETx as a valid string but
otherwise knows not what it means.... or I need to send it a different way.

Unlike BinkleyTerm, the BBS software *doesn't* have a separate pre-init that
can be defined.

$$
--- SBBSecho 3.28-Linux
 * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
SEEN-BY: 19/10 104/119 105/81 106/201 114/10 120/302 616 128/187 129/14
SEEN-BY: 129/215 305 135/383 153/757 7715 154/10 30 50 110 700 218/700
SEEN-BY: 218/840 220/20 30 70 90 221/1 6 360 226/17 18 30 44 50 100
SEEN-BY: 227/114 229/110 112 134 200 206 307 310 317 400 426 428 470
SEEN-BY: 229/664 700 705 266/512 267/800 291/111 301/1 320/219 322/757
SEEN-BY: 335/364 341/66 342/200 396/45 633/267 280 290 384 414 418
SEEN-BY: 633/420 422 509 2744 712/848 770/1 100 340 350 772/220 230
SEEN-BY: 902/26 2320/0 105 304 3634/12 5020/400 5075/35
PATH: 2320/105 154/10 221/6 218/840 770/1 633/280 229/426