From: dumas.walker@CAPCITY2.remove-vb-this

To: DIGITAL MAN
Good afternoon,
I am a hub for a QWK network. One of my connections, also a synchronet
system, is picking up packets here and, when his system tries to toss them, they are being marked as BAD.

I am about to ask him for additional information but thought I would ask if there are any likely causes for that? Also, I am not familiar with this
issue, so would the reason it gets marked BAD (and not tossed) show up in a
log somewhere?

Thanks!


* SLMR 2.1a * -

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP --- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: digital.man@vert.synchro.net.remove-8m7-this

To: Dumas Walker
Re: BAD QWK Network Packets
By: Dumas Walker to DIGITAL MAN on Fri Mar 13 2020 04:44 pm

Good afternoon,
I am a hub for a QWK network. One of my connections, also a synchronet system, is picking up packets here and, when his system tries to toss them, they are being marked as BAD.

I am about to ask him for additional information but thought I would ask if there are any likely causes for that? Also, I am not familiar with this issue, so would the reason it gets marked BAD (and not tossed) show up in a log somewhere?

Yes, the reasons for the bad packet detection should be in the log output.

digital man

Synchronet "Real Fact" #94:
Synchronet v3.16c was released in August of 2015 (5 years after v3.15b).
Norco, CA WX: 53.2øF, 97.0% humidity, 1 mph SSE wind, 0.52 inches rain/24hrs --- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)