| |
AA6HF > SYSOP 29.11.19 02:30l 47 Lines 1850 Bytes #999 (0) @ WW
BID : 96278_AA6HF
Read: GUEST
Subj: AA6HF JNOS bbs dupes!
Path: IW8PGT<IR2UBX<IW2OHX<IR1UAW<IZ3LSV<IQ5KG<I0OJJ<N6RME<AA6HF
Sent: 191129/0013z @:AA6HF.#SCA.CA.USA.NOAM [Palm Springs] #:96280 $:96278_AA6H
Sergej, et al
There are more than 140 bulletins that I received from N2NOV that forced my
JNOS bbs to issue new bids. The N2NOV bulletins arrived at AA6HF missing a
BID-ID and other issues. The problem is not on my system it's on N2NOV bbs!
He's been notified. I've stopped all forwarding to/from his bbs 3 days ago.
But the bad bulletins are circulating in the network. I can't do anything
about those bulletins. They wiil eventually be purged. In the meantime,
I0ojj, vk6zrt, cx2sa, ut1hzm and others need to contact the sysop at the
source of these bulletins 'N2NOV@N2NOV.SI.NY.US.NOAM'. Maybe he'll realize
the need to fix the problem.
I've also been working with N1URO on this issue. He just sent this
bulletin regarding these dupes and bids. Here is his message:
Date: 28 Nov 19 23:41:00 GMT
From: n1uro@n1uro.#cct.ct.usa.noam
To: sysop@ww
Subject: Re: AA6HF JNOS bbs dupes!
Path: N1URO
From: N1URO@N1URO.#CCT.CT.USA.NOAM
To : SYSOP@WW
Sergej, Jose, et al
The root cause was a bad feed from N2NOV. I've been working with N2NOV on this
issue of old bulletins getting sent back through into the network. On the
other hand, Jose putting AA6HF into reject.sys as a reject may be a bad idea.
If AA6HF needed to contact you for some debugging information you would not be
able to provide it for him in which case it's like adding to the issue not
helping to solve one if you're simply rejecting such BIDs. You'd be better off
using the H flag instead of the R flag to hold for review in case AA6HF does
need to contact you. Once you see things return to normal you can comment
that line out of reject.sys.
On another note, I received an old bulletin from 2004 sent out from another
JNOS system that is NOT AA6HF. I don't know of any bbs software that would
hold onto BIDs for 15+ years.
---- end of message ----
73 de Jack AA6HF
Read previous mail | Read next mail
| |
