| |
N1URO > SYSOP 15.09.17 16:03l 37 Lines 1213 Bytes #999 (0) @ WW
BID : 50738_N1URO
Read: GUEST
Subj: re: kf5jrv
Path: IW8PGT<LU4ECL<N9PMO
Sent: 170915/1400Z 26888@N9PMO.#SEWI.WI.USA.NA BPQ6.0.14
MID: 50738_N1URO
Date: 2017/09/15 14:00
Type: Bulletin
From: N1URO@N1URO.#CCT.CT.USA.NOAM
To: SYSOP@WW
Subject: re: kf5jrv
Mbo: N9LCF
Body: 1093
R:170915/1400Z 26505@N9LCF.#NEIN.IN.USA.NOAM BPQ6.0.14
R:170915/1400Z @:VE2JOS.#MTL.QC.CAN.NOAM #:16421 [Beauharnois] $:50738_N1URO
R:170915/1359Z 22949@OK2PEN.SP.BRA.SOAM [Sao Jose dos Campos] $:50738_N1URO
R:170915/1331Z @:N1URO.#CCT.CT.USA.NOAM #:50738 [Unionville] $:50738_N1URO
From: N1URO@N1URO.#CCT.CT.USA.NOAM
To : SYSOP@WW
On Fri, 2017-09-15 at 07:55 -0500, VE7ASS wrote:
> So help me out here... as English is not my native tongBrian... so help me out here as English is not my native tongue...
Dupes on line... BPQisms? ;-)
> Do you mean you see the same problem as I described?
I've received about 15 copies of the same message yesterday.
> And, do you mean Good Luck in finding out which BPQ bbs is the problem?
BPQBBS does not show the originating bid in the R: line. How can you find
something that is not there? This is one of the more critical issues that
occur when a software package is not 100% compliant to the systems that are
currently networked together. That's why we don't use it in EastNet.
73 de N1URO - using IPv6 on packet!
Read previous mail | Read next mail
| |
