| |
N1URO > SYSOP 26.06.18 07:13l 35 Lines 1511 Bytes #999 (0) @ WW
BID : 3416_N1URO
Read: GUEST
Subj: N9PMO > RE: F>
Path: IW8PGT<IR2UBX<EA2RCF<ZL2BAU<N1URO
Sent: 180626/0509Z @:N1URO.#CCT.CT.USA.NOAM #:3416 [Unionville] $:3416_N1URO
From: N1URO@N1URO.#CCT.CT.USA.NOAM
To : SYSOP@WW
Mike;
> I beleive i have found the BBS causing the problem, I have sent the BBS
> Sysop a Email about the problem,
First off, thank you for tracking down the offending BBS and making an effort
to contact them. If you read ALL of the messages in regards to this *I* was
not the only one to make comment.
> I hope this puts a stop to the BPQ Bashing, i see no need day after day
> to keep sending out basically the same packet message.
I don't know where you get BPQ bashing from. There's issues with other BBS
software as well which I'm actually assisting with to get resolution on.
When other BBS softwares act up I and other make mention of that as well.
BPQ is not singled out so your perception is not 100%.
I do not post "basically the same packet message" day after day either.
When there is a problem with a BBS it's good to somehow bring it to the
attention of sysop@ at times so that if the offending BBS sysop can't be
contacted at least there's hope their neighbor BBS partners may be able to
halt forwarding with them until the issue is resolved. We've always kept
watch over ourselves that way for the decades I've been running a BBS.
Obviously it worked or else you wouldn't have investigated... and again I
thank you for your diligence in trying to get the issue resolved with the
offending sysop. EastNet users will appreciate being able to read actual
subject lines of mail instead of seeing F> in some cases.
73 de Brian N1URO
Read previous mail | Read next mail
| |
