OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
KB2VXA > INTRUD   18.11.02 04:51l 42 Lines 1578 Bytes #999 (0) @ WW
BID : 62517_WT3V
Read: DB0FHN DK5RAS GUEST
Subj: Re: VK8PDG & WING NUT
Path: DB0FHN<DB0ZWI<DB0HOT<DB0ERF<DB0FBB<DB0GOS<ON0AR<ON0AR<ON0BEL<IK6PYS<
      7M3TJZ<PY4VE<PP5BLU<VK5ASF<VK2CZR<VK2TGB<VK2IO<VK2AAB<FK8KAB<VK2DW<
      N7QDN<WA1URA<K1UOL<K1UOL<WA2PNU<KC2COJ<WT3V
Sent: 021115/1750Z @:WT3V.#CNJ.NJ.USA.NOAM #:62517 [Lakehurst] $:62517_WT3V
From: KB2VXA@WT3V.#CNJ.NJ.USA.NOAM
To  : INTRUD@WW

Hello Peter,
First of all, do you have any indications of whether this QRM is being 
generated locally, within Australia, or outside the country? Don't reply, 
just think about it.

First, YOU must take your best guess and act accordingly. Then take any 
replies to your bull and other sources (if you have made any other 
contacts) into account.

Also, gather evidence that the problem exists, whether or not it is 
intentional, (may be coincidental although it APPEARS intentional) and 
generally log it along with pertinent data as to it's characteristics and 
other "remarks" in the log.

If it is determined by best reasoning that the source is under the 
jurisdiction of your licencing agency, the matter is best turned over to 
them for further investigation and possible enforcement action.

If the source is positively determined to be outside the country, don't 
count on any action being taken, diplomatic and political issues you 
know. Getting another country to comply is like pulling hen's teeth.

remember always, you must have POSITIVE PROOF and provide it to the 
agency ongoing or they will simply dismiss you, politely, but dismiss 
they will.

I sincerely wish you the best of luck!

**********************************************************************
When one does not expect to succeeed, any success, however small, exceeds
all expectations.
**********************************************************************

73 de Warren, KB2VXA

e-mail: kb2vxa@juno.com

Message timed: 17:54 GMT on 15 Nov 02


Read previous mail | Read next mail


 20.11.2026 06:01:12lGo back Go up