Digital Man wrote to poindexter FORTRAN <=-
Yes, just renaming the file to VERT.QWK should trigger an import
attempt (in the terminal server event thread).
Subject: Re: Re-processing QWK packets
@MSGID: <65B69CDA.67312.dove.sync@realitycheckbbs.org>
@REPLY: <65B58381.51120.sync@vert.synchro.net>
@TZ: 41e0
Digital Man wrote to poindexter FORTRAN <=-
Yes, just renaming the file to VERT.QWK should trigger an import attempt (in the terminal server event thread).
Thanks, I saw this when I tried re-importing:
1/28 09:54:31a QNET !Message from VERT on UNKNOWN QWK CONFERENCE
NUMBER: 2022
1/28 09:54:31a QNET C:\sbbs\data\VERT.qwk renamed to C:\sbbs\data\VERT.qwk.65b694d7.bad
(There were some other errors about duplicate messages as well)
The weird thing was that when I added TECH_TALK to the BBS, I'd noticed
that my DOVE boards were set to dynamic numbers
, and I have a message
area 2022 configured as TECH_TALK.
I just tried deleting the area and re-creating it as a static QWK area # 2022 and got the same error.
Digital Man wrote to poindexter FORTRAN <=-
That conference number (2022) needs to be configured for a QWKhub in SCFG->Networks->QWK->Hubs->VERT->Sub-boards. --
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 68 |
Nodes: | 4 (0 / 4) |
Uptime: | 09:04:04 |
Calls: | 956 |
Calls today: | 2 |
Files: | 7,955 |
Messages: | 297,219 |