ICANN/GNSO GNSO Email List Archives

[ga]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [ga] Got a virus, Ken?

  • To: Richard Henderson <richardhenderson@xxxxxxxxxxxx>
  • Subject: Re: [ga] Got a virus, Ken?
  • From: Jeff Williams <jwkckid1@xxxxxxxxxxxxx>
  • Date: Tue, 06 Apr 2004 18:26:37 -0700
  • Cc: General Assembly of the DNSO <ga@xxxxxxxxxxxxxx>, "kstubbs@xxxxxxxxxxx" <kstubbs@xxxxxxxxxxx>, Netcom Abuse <abuse@xxxxxxxxxx>, "Ken Stubbs (3rd E-mail address)" <kstubbs@xxxxxxxxxxx>, Ken Stubbs <kstubbs@xxxxxxxxxxx>, "Ken Stubbs (Yahoo address)" <kstubbs@xxxxxxxxx>
  • Organization: INEGroup Spokesman
  • References: <001101c41bd6$36198550$2158fc3e@richard>
  • Sender: owner-ga@xxxxxxxxxxxxxx

Richard, Ken, and all former DNSO GA members or other interested
stakeholders/users,

 Richard, Ken in and of himself IS a virus of sorts.  Given his long
standing
dismissive and errant ML behaviors on many forums before you became
involved, Mr. Stubbs has frequently displayed a number of varying and
inconsistent attitudes that have left many to question his overall
mental
health from time to time.  Hence I would question if he EMAIL you
kindly provided from Ken was a virus at all and was not intentional.
In any event I would be sure to inform the proper authorities in the
UK of your receipt of it, and file an official legal complaint, lest
you desire to continue to receive such fraudulent emails from one
of several other of Ken Stubbs Email addresses in the future...

Richard Henderson wrote:

>    I know I've sometimes expressed concerns about Ken Stubbs
> association with ICANN and how I wondered if that created a conflict
> of interest at the time that he headed up Afilias's (successful)
> application for the .info registry... but... I think this virus-laden
> message I received today was probably sent unwittingly from your
> computer, and I just want to advise you and the members of this list
> who may also be in your address book that you seem to have a virus Ken
> which is sending out very plausible messages to people making them
> think they are about to lose their e-mail accounts for improper use
> and tempting them to 'open up' the accompanying document. A phone call
> to my e-mail provider confirmed that this message purporting to come
> from them was not from them at all. So please be careful if any of you
> receive a message like this one below:
>
>
>
> -------------
>
>
>
> Return-Path: <kstubbs@xxxxxxxxxxx>
>
> Received: from [snip]for <richardhenderson@xxxxxxxxxxxx>;
>
>           Tue, 6 Apr 2004 11:33:05 +0100
>
> Date: Sun, 11 Apr 2004 12:34:16 +0100
>
> To: richardhenderson@xxxxxxxxxxxx
>
> Subject: E-mail account security warning.
>
> From: management@xxxxxxxxxxxx
>
> Message-ID: <snip >
>
> MIME-Version: 1.0
>
> Content-Type: multipart/mixed;
>
>         boundary="--------snip "
>
>
>
> ----------[snip]
>
> Content-Type: text/plain; charset="us-ascii"
>
> Content-Transfer-Encoding: 7bit
>
>
>
> Dear user  of Ntlworld.com,
>
>
>
> Your  e-mail account will  be disabled because of improper  using in
> next
>
> three days, if  you  are  still wishing to use  it, please, resign
> your
>
> account information.
>
>
>
> Advanced details can  be  found in attached  file.
>
>
>
> Kind regards,
>
>    The  Ntlworld.com  team
>
>
>
> ----------[attached file obviously snipped]
>
>

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 134k members/stakeholders strong!)
"Be precise in the use of words and expect precision from others" -
    Pierre Abelard

"If the probability be called P; the injury, L; and the burden, B;
liability depends upon whether B is less than L multiplied by
P: i.e., whether B is less than PL."
United States v. Carroll Towing  (159 F.2d 169 [2d Cir. 1947]
===============================================================
Updated 1/26/04
CSO/DIR. Internet Network Eng. SR. Eng. Network data security
IDNS. div. of Information Network Eng.  INEG. INC.
E-Mail jwkckid1@xxxxxxxxxxxxx
 Registered Email addr with the USPS
Contact Number: 214-244-4827





<<< Chronological Index >>>    <<< Thread Index >>>