Synchronet has a lot of per-user configuration options for how QWK packet
are created. I would try experimenting with them. -- digital man
(rob)

I've tried from not sending anything other than the messages via zip to sending everything with no change in me receiving QWK packets.

He means you need to try playing with the QWK settings on this end. If you
log onto the bbs using your QWK account... log on via telnet and not ftp...
you will receive a prompt. If you type '?', it will display the QWK menu.

Check the (C)onfiguration options. There may be one that is set No (or Yes) that is causing the packets to be incompatable with RA. You may have to
play with them some to get a configuration that works.

Here are the settings that work with a GT Power board, so I won't guarantee that they work with RA but you can try them.

[A] Ctrl-A Color Codes : Expand to ANSI
[T] Archive Type : ZIP
[E] Include E-mail Messages : Un-read Only
[I] Include File Attachments : Yes
[D] Delete E-mail Automatically : Yes
[F] Include New Files List : No
[N] Include Index Files : Yes
[C] Include Control Files : Yes
[V] Include VOTING.DAT File : No
[H] Include HEADERS.DAT File : No
[Y] Include Messages from You : No
[Z] Include Time Zone (@TZ) : Yes
[P] Include Message Path (@VIA) : No
[M] Include Message/Reply IDs : No
[U] Include UTF-8 Characters : No
[X] Extended (QWKE) Packet Format: No

You may also want to check your QWK network software documentation and see if it mentions needing/not needing Index, Control, or HEADERS.DAT files, or if
it supports QWKE (it probably does not!). Then make any changes to your configuration settings based on what the documentation tells you (if
anything).


* SLMR 2.1a * Excuse me - but HOW do you spell EMT ????
---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Synchronet has a lot of per-user configuration options for how QWK packets are
reated. I would try experimenting with them.

I received an email this am from a user complaining about how the board was acting and mentioned the time change. I thought they were mistaken.

I tried logging on just now to give Marty a little guidance on how to
"work" the QWK configuration settings. I received a "sorry time reduced... goodbye" result for a system event that is allegedly scheduled for 05:00.

Local time is now after 09:30 and I have confirmed that the OS time (linux) is correct.

The 05:00 event appears to be MSGMAINT. I just kicked it off manually and
that fixed it. That was after I tried restarting Synchronet and getting
the same (not good) results.

I have never had Synchronet mess itself over the time change before.
It is with 3.20 that I upgraded to just over a week ago.


* SLMR 2.1a * Ted Kennedy's Bumper Sticker: My other car is underwater.
---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: RA to SBBS QWK Networ
By: Dumas Walker to DIGITAL MAN on Sun Mar 10 2024 09:59 am

Synchronet has a lot of per-user configuration options for how QWK packets are
reated. I would try experimenting with them.

I received an email this am from a user complaining about how the board was acting and mentioned the time change. I thought they were mistaken.

What was their complaint?

I tried logging on just now to give Marty a little guidance on how to
"work" the QWK configuration settings. I received a "sorry time reduced... goodbye" result for a system event that is allegedly scheduled for 05:00.

Local time is now after 09:30 and I have confirmed that the OS time (linux) is correct.

The 05:00 event appears to be MSGMAINT. I just kicked it off manually and that fixed it. That was after I tried restarting Synchronet and getting
the same (not good) results.

I have never had Synchronet mess itself over the time change before.
It is with 3.20 that I upgraded to just over a week ago.

The log output from the terminal server would be helpful to know more about what happened.
--
digital man (rob)

Steven Wright quote #7:
A clear conscience is usually the sign of a bad memory.
Norco, CA WX: 67.0°F, 34.0% humidity, 8 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Synchronet has a lot of per-user configuration options for how QWK

packet

are created. I would try experimenting with them. -- digital man
(rob)

I've tried from not sending anything other than the messages via zip to
sending everything with no change in me receiving QWK packets.

He means you need to try playing with the QWK settings on this end. If you log onto the bbs using your QWK account... log on via telnet
and not ftp... you will receive a prompt. If you type '?', it will
display the QWK menu.

That's what I meant too.

Check the (C)onfiguration options. There may be one that is set No (or Yes) that is causing the packets to be incompatable with RA. You may
have to play with them some to get a configuration that works.

I've went from nothing on to everything on as well as trying just some of
them, but I haven't found the right configuration yet. I'm hoping an RA
sysop could help.

Here are the settings that work with a GT Power board, so I won't guarantee that they work with RA but you can try them.

[A] Ctrl-A Color Codes : Expand to ANSI [T] Archive Type
: ZIP [E] Include E-mail Messages : Un-read Only [I]
Include File Attachments : Yes [D] Delete E-mail Automatically
: Yes [F] Include New Files List : No [N] Include Index Files : Yes
[C] Include Control Files : Yes [V] Include VOTING.DAT
File : No [H] Include HEADERS.DAT File : No [Y] Include
Messages from You : No [Z] Include Time Zone (@TZ) : Yes [P]
Include Message Path (@VIA) : No [M] Include Message/Reply
IDs : No [U] Include UTF-8 Characters : No [X] Extended (QWKE)
Packet Format: No

I'll try that, thanks.

You may also want to check your QWK network software documentation and see if it mentions needing/not needing Index, Control, or HEADERS.DAT
files, or if it supports QWKE (it probably does not!). Then make
any changes to your configuration settings based on what the
documentation tells you (if anything).

The documentation just says how to set up the configuration for the software, nothing about receiving or sending packets, just that it should work.

---
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp)
(ports 22, 23, 110, 21, 119) (ssh: login bbs password shsbbs)


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (1:340/1101)

so why hasn't this furry guy got his problem fixed after all this time?

I don't know. He needs to buy his own modem as far as I can tell...

It sounds like you were actually able to start connecting via FTN with him again?

Being able to connect with him still doesn't fix your issue with two networks using the same Zone number, though.


* SLMR 2.1a * Salesmen do it with their tongues.
---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)