| |
N1URO > SYSOP 29.11.19 00:53l 30 Lines 1279 Bytes #999 (0) @ WW
BID : 35704_N1URO
Read: GUEST
Subj: Re: AA6HF JNOS bbs dupes!
Path: IZ3LSV<IR1UAW<IW2OHX<HB9ON<IW8PGT<I3XTY<I0OJJ<I0OJJ<GB7CIP<N1URO
Sent: 191128/2341Z @:N1URO.#CCT.CT.USA.NOAM #:35704 [Unionville] $:35704_N1URO
>From n1uro%n1uro.#cct.ct.usa.noam@i0ojj.ampr.org Fri Nov 29 00:50:42 2019
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0m-uro) with SMTP
id AA38845 ; Fri, 29 Nov 2019 00:50:42 +0100
Message-Id: <35704_N1URO@i0ojj.bbs>
>From: n1uro@n1uro.#cct.ct.usa.noam
X-JNOS-User-Port: Telnet (i0ojj @ 44.134.32.240) -> Sending message
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.
---
SendBBS v1.1 by N1URO for LinFBB
Read previous mail | Read next mail
| |
