| |
VE3WBZ > SYSOP 15.09.12 00:42l 71 Lines 1593 Bytes #999 (0) @ WW
BID : 12115_VE3LSR
Read: GUEST
Subj: Attn: VE3PRC & VE3TOK BBSes
Path: IZ3LSV<ED1ZAC<IW0QNL<JH4XSY<JE7YGF<VE3UIL<VE3LSR
Sent: 120914/2227Z @:VE3LSR.#SCON.ON.CAN.NOAM #:12115 [Barrie] $:12115_VE3LSR
From: VE3WBZ@VE3LSR.#SCON.ON.CAN.NOAM
To : SYSOP@WW
TO: SYSOP @WW
FR: VE3WBZ
DT: Friday, September 14th.,2012 @1507hrs EST <JPST>
Attention of the sysops of VE3PRC and VE3TOK;
Below is postings by G0TEZ and KB2VXA, that ...well I got
via another BBS, that doesn't have traffic coming thru
as the path shows...VE3PRC ...VE3TOK.
examples:-
> From : G0TEZ
> To : HUH @WW
> Type/Status : B$
> Date/Time : 13-Sep 22:51
> Bid : CE0095G0TEZ
> Message # : 137502
> Title : Re: Arab loonies attack US Embassys
> Path: !VE3PRC!VE3TOK!
> enough to bring on
> the riots.
>
> Thou shalt not insult Mohammed.
>
> CU Mate.
>
> 73 - Ian, G0TEZ @ GB7CIP
>
> Message timed: 20:46 on 2012-Sep-13 BST
> Message sent using WinPack-Telnet V6.80
>
> [End of Message #137502 from G0TEZ]
Obvious the path of this text from G0TEZ begins with GB7CIP
not "VE3TOK".
I have as I say the full text, but they even screw the test
wonderfully.
> From : KB2VXA
> To : CAR @WW
> Type/Status : B$
> Date/Time : 14-Sep 14:06
> Bid : 24987_VK6ZRT
> Message # : 137579
> Title : Re: G0TEZ > Monza
> Path: !VE3PRC!VE3TOK!
>
> Message timed by NIST: 13:47 on 2012-Sep-14 GMT
>
> [End of Message #137579 from KB2VXA]
Again VE3TOK screws up the traffic, as it originates
at VK6ZRT.
Could one of our dedicated sysops please contact VE3TOK
as last time, he got all in a snit when I mailed him
with this problem.
If he can not correct, then PLEASE sysops find a route
around this BBS.
Thanks
Peter VE3WBZ
Read previous mail | Read next mail
| |
