| |
N2NOV > SYSOP 11.03.20 20:30l 23 Lines 943 Bytes #999 (0) @ WW
BID : 76381_N2NOV
Read: GUEST
Subj: BID Mangling By BPQ?
Path: IW8PGT<LU4ECL<ED1ZAC<NA7KR<N1URO<N1URO<N2NOV
Sent: 200311/1858z @:N2NOV.#RICH.NY.USA.NOAM [NYC] [JNOS] #:76383 $:76381_N2NOV
>From n2nov@n2nov.ampr.org Wed Mar 11 14:58:06 2020
Received: from n2nov.ampr.org by n2nov.ampr.org ([JNOS]) with SMTP
id AA976383 ; Wed, 11 Mar 2020 14:58:06 EDT
Message-Id: <976381@n2nov.ampr.org>
>From: n2nov@n2nov.ampr.org
X-JNOS-User-Port: Telnet (n2nov @ 44.68.41.2) -> Sending message
On March 9th I sent out a message to sysop@ww with a subject pertaining to
the AMPRnet DDoS attack that N1URO was referencing. My original message
went out with BID #973405@n2nov.ampr.org but a copy came around with a
BID #73405_n2nov@N3HYM.bbs
Here is the R: lines of the second message, passing through BPQ6.0.19 at NS2B
and through BPQK6.0.19 at N3HYM:
R:200309/1507Z 15997@N3HYM.MD.USA.NOAM BPQK6.0.19
R:200309/1504Z 48834@NS2B.#WNY.NY.USA.NOAM BPQ6.0.19
R:200309/1603z @:N2NOV.#RICH.NY.USA.NOAM [NYC] [JNOS] #:73407 $:73405_N2NOV
Maybe there is something off in the BPQ in only being able to handle a BID
of five digits and not six?
Read previous mail | Read next mail
| |
