Date: Thu, 22 Aug 2002 08:18:32 -0400
Reply-To: Michael Raithel <RAITHEM@WESTAT.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Michael Raithel <RAITHEM@WESTAT.COM>
Subject: Re: OT? - maybe: a nascent unwelcome resurgence
The inimitable Ray Pass posted the following:
> A while back, before you joined up, there was a fair amount of discussion
on this list about amounts and types of
> spam" from recruiters that was deemed appropriate. There was an implicit
agreement between the list and those of you in
> your profession who use the list for trolling, marketing, etc, that
certain "general" guidelines would be followed. I use the
> term "general" because it all amounted to an informal agreement with no
real "specific" rules being set or agreed to.
>Basically, the model that was followed for a while was that there would NOT
be a series of daily, short, non-informational
> messages, but instead, there would be a reduced amount of aggregate
summaries of opportunities available, with certain
> pieces of information in them - at a minimum this included general
geographic location, an idea of salary or fee range,
> a listing of types of experience/knowledge expected and tasks to be
> Adhering to these "guidelines" will go a long way to putting yourself in a
more acceptable light on this list. I'm sure a quick
> discussion with Jim or Mike will acquaint you with what goes on here.
I couldn't agree with you more! Lately, I have been directly targeted by
recruiter spam. As a matter of fact, just before reading your SAS-L
posting, this morning, I wrote the following to a "direct-to-me at SAS
Mecca" job recruiting spam message (sent to me on: Wed 8/21/02 6:49 PM) from
> I am not interested in ASG, Inc. I consider your unsolicited E-mail to be
spam. Do not send further E-mail messages to me.
I would be interested in knowing if other SAS-L posters have been getting
this type of direct-to-your-SAS-L-posting E-mail address spam from the
aforementioned person or from other recruiters. Or, am I just SPECIAL?!?!?!
I hope that this discussion proves helpful now, and in the future!
Of course, all of these opinions and insights are my own, and do not reflect
those of my organization or my associates. All SAS code and/or methodologies
specified in this posting are for illustrative purposes only and no warranty
is stated or implied as to their accuracy or applicability. People deciding
to use information in this posting do so at their own risk.
Michael A. Raithel
"The man who wrote the book on performance"
Author: Tuning SAS Applications in the MVS Environment
...Your words waste and decay, nothing you say, reaches my ears anyway... -
Emerson, Lake, and Palmer