Searching \ for 'Information as per your request.' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/index.htm?key=information+per
Search entire site for: 'Information as per your request.'.

Truncated match.
PICList Thread
'Information as per your request.'
1995\08\20@195437 by SORGI

flavicon
face
.edu,
             spam_OUTmde-lTakeThisOuTspammizzou1.missouri.edu, .....kidlit-lKILLspamspam@spam@bingvmb.cc.binghamton.edu,
             nihtoc-lspamKILLspamlist.nih.gov, .....alctsKILLspamspam.....UICVM.CC.UIC.EDU,
             EraseMEill-lspam_OUTspamTakeThisOuTuvmvm.uvm.edu, macscrptspamspam_OUTcaligari.Dartmouth.EDU,
             fapesp-l%@spam@bruspvm.bitnetKILLspamspamlistserv.net, KILLspamcruise-lKILLspamspamunlvm.unl.edu,
             pgssnews%RemoveMEvm1.mcgill.canihongoTakeThisOuTspammitvma.mit.edu,
             spamBeGonedirect-lspamBeGonespamuafsysb.uark.edu, TakeThisOuTexlibrisEraseMEspamspam_OUTrutvm1.rutgers.edu,
             RemoveMEisworldspamTakeThisOuTirlearn.ucd.ie, sbpchoje%brlncc.bitnetEraseMEspam.....listserv.net,
             EraseMEpagemakrspamindycms.iupui.edu, RemoveMEclayartEraseMEspamEraseMEukcc.uky.edu,
             RemoveMEmuseum-lspam_OUTspamKILLspamunmvma.unm.edu, RemoveMEberita-lTakeThisOuTspamspamvmd.cso.uiuc.edu,
             EraseMEicen-lspamspamspamBeGoneiubvm.ucs.indiana.edu, RemoveMEarch-lKILLspamspamtamvm1.tamu.edu,
             h-amstdySTOPspamspamspam_OUTmsu.edu, spamBeGonepakistanSTOPspamspamEraseMEasuvm.inre.asu.edu,
             KILLspamlastwedsspamBeGonespamlistserv.clark.net, EraseMEcrtnetspamEraseMEpsuvm.psu.edu,
             @spam@help-net@spam@spamspam_OUTvm.temple.edu, spamBeGonepu-newsspamKILLspamvm.cc.purdue.edu,
             mdk-12%.....umdd.bitnetspam_OUTspamlistserv.net, TakeThisOuTansax-l.....spamTakeThisOuTwvnvm.wvnet.edu,
             TakeThisOuTair-lKILLspamspamspamvtvm1.cc.vt.edu, .....comics-lspamRemoveMEunlvm.unl.edu,
             RemoveMEcommcollspamspamBeGoneukcc.uky.edu, spamBeGoneenews-out@spam@spamspam_OUTmail.eworld.com,
             TakeThisOuTpsrt-lspamspammizzou1.missouri.edu, activ-lEraseMEspammizzou1.missouri.edu,
             ufrjncen%RemoveMEufrj.bitnetEraseMEspamspam_OUTlistserv.net, @spam@jobplaceRemoveMEspamEraseMEnews.jobweb.org,
             EraseMEcar-engspam@spam@earn.cvut.cz, @spam@teslca-lspam_OUTspam.....cunyvm.cuny.edu,
             spamBeGonenetmonthEraseMEspamvm.marist.edu, mediev-lspamBeGonespamukanvm.cc.ukans.edu,
             dairy-l%RemoveMEumdd.bitnet@spam@spamspamBeGonelistserv.net, .....h-women@spam@spamEraseMEUICVM.CC.UIC.EDU,
             .....oracle-lRemoveMEspamccvm.sunysb.edu, .....psygrd-jSTOPspamspam@spam@acadvm1.uottawa.ca,
             bestwebEraseMEspam@spam@vm.ege.edu.tr, RemoveMEwx-talkspamspamBeGonevmd.cso.uiuc.edu,
             spamBeGonemarmamKILLspamspam@spam@uvvm.uvic.ca, chminf-lspam_OUTspam@spam@iubvm.ucs.indiana.edu,
             spamBeGonenetscape@spam@spamirlearn.ucd.ie, RemoveMEaeraEraseMEspamKILLspamasuvm.inre.asu.edu,
             spamBeGoneindiaspam_OUTspamRemoveMEcunyvm.cuny.edu, .....native-lspamRemoveMEtamvm1.tamu.edu, cwis-lspam@spam@msu.edu,
             EraseMEnatosciRemoveMEspamSTOPspamcc1.kuleuven.ac.be, RemoveMEbgrass-lKILLspamspamTakeThisOuTukcc.uky.edu,
             spamBeGoneir-lspam@spam@uccvma.ucop.edu, RemoveMEfish-ecologyspam_OUTspamsearn.sunet.se,
             kidcafespamspamvm1.nodak.edu, spam_OUTsonic-versespam_OUTspamspam_OUTvm.marist.edu,
             pns-lspam_OUTspampsuvm.psu.edu, RemoveMEquiltnetKILLspamspam@spam@ukcc.uky.edu,
             philosopspamBeGonespam.....vm1.yorku.ca, KILLspamgardensspam.....ukcc.uky.edu,
             spam_OUTchemed-lspamKILLspamuwf.cc.uwf.edu, RemoveMEseasia-lRemoveMEspamEraseMEmsu.edu,
             buslib-l%KILLspamidbsu.bitnetspamspamBeGonelistserv.net, qualrs-lspamspamuga.cc.uga.edu,
             RemoveMEwinhlp-lspamBeGonespamRemoveMEadmin.humberc.on.ca, KILLspamhum-molgenspamBeGonespamnic.surfnet.nl,
             @spam@educational-researchSTOPspamspam@spam@asuvm.inre.asu.edu, ankietaspamBeGonespamspamBeGoneplearn.edu.pl,
             spamBeGonevolcanospamasuvm.inre.asu.edu, spam_OUTanthro-lSTOPspamspamubvm.cc.buffalo.edu,
             RemoveMEdevel-lspamspamamerican.edu,
             e-poetry%TakeThisOuTubvm.cc.buffalo.eduwindowsspamspamRemoveMEvm1.mcgill.ca,>              KILLspamstat-lspamspamspam_OUTvm1.mcgill.ca, arlis-lRemoveMEspamukcc.uky.edu,
             EraseMEinfo-macSTOPspamspamRemoveMEvmd.cso.uiuc.edu, spam_OUTtheoryntRemoveMEspamEraseMEvm1.nodak.edu,
             TakeThisOuTblues-lRemoveMEspam@spam@brownvm.brown.edu, newnir-l%EraseMEitocsivm.bitnetRemoveMEspamlistserv.net,
             spambbshop.....spamspamadmin.humberc.on.ca, asis-lspam_OUTspam@spam@vmd.cso.uiuc.edu,
             .....nurseresspamspam.....kentvm.kent.edu, scupnewsKILLspamspamEraseMEcmsa.berkeley.edu,
             EraseMEvocnet@spam@spam@spam@cmsa.berkeley.edu, @spam@primaryspamspamKILLspamumrvmb.umr.edu,
             spamBeGoneteluguRemoveMEspamEraseMEvm1.nodak.edu, RemoveMEflyfishKILLspamspamRemoveMEukcc.uky.edu, TakeThisOuTsas-lspamuga.cc.uga.edu,
             spamBeGonetec-tenKILLspamspamTakeThisOuTsjuvm.stjohns.edu, EraseMEtoolb-l.....spamKILLspamlistserv.arizona.edu,
             spamvictoriaspamiubvm.ucs.indiana.edu, suearn-lSTOPspamspamubvm.cc.buffalo.edu,
             reachSTOPspamspamKILLspamucsbvm.ucsb.edu, @spam@cumrec-l.....spamspamvm1.nodak.edu,
             spamheproc-l.....spam.....american.edu, medtextl.....spamvmd.cso.uiuc.edu,
             KILLspamconslinkspam_OUTspamsivm.si.edu, spam_OUTh-teachspamTakeThisOuTmsu.edu,
             .....humanist.....spamRemoveMEbrownvm.brown.edu, spam_OUTacsoft-lTakeThisOuTspamEraseMEwuvmd.wustl.edu,
             EraseMEioob-lspamBeGonespamKILLspamuga.cc.uga.edu, RemoveMEhytel-lspamBeGonespamspamkentvm.kent.edu,
             @spam@flteachspamspamubvm.cc.buffalo.edu, TakeThisOuTh-rhetorKILLspamspam@spam@UICVM.CC.UIC.EDU,
             .....mitbayRemoveMEspammitvma.mit.edu, KILLspamipct-lspamTakeThisOuTguvm.ccf.georgetown.edu,
             TakeThisOuTmedia-lspamspam_OUTbingvmb.cc.binghamton.edu, RemoveMEchildlitspamspamSTOPspamrutvm1.rutgers.edu,
             .....psycgradEraseMEspamacadvm1.uottawa.ca, spamBeGonementor-lspamRemoveMEvm.its.rpi.edu,
             .....christiaEraseMEspamasuvm.inre.asu.edu, spamnsc94-lspam_OUTspam@spam@gumncc.earn.net,
             spamk12admin@spam@spamSTOPspamlistserv.syr.edu, spamBeGonee-clipsspamBeGonespam@spam@sjuvm.stjohns.edu,
             RemoveMEjwaRemoveMEspamRemoveMEubvm.cc.buffalo.edu, cybsys-lKILLspamspamspambingvmb.cc.binghamton.edu,
             spam_OUTsts-l@spam@spamutkvm1.utk.edu, TakeThisOuTaccess-lspam_OUTspameva.dc.LSOFT.COM,
             KILLspamvpiej-l.....spamTakeThisOuTvtvm1.cc.vt.edu, TakeThisOuTmtg-lEraseMEspamRemoveMEoracle.wizards.com,
             spam_OUTscit-bibRemoveMEspam.....qucdn.queensu.ca, spambirdchatKILLspamspamKILLspamlistserv.arizona.edu,
             spampoli-scispam_OUTspamrutvm1.rutgers.edu,
             shaksper%STOPspamutoronto.bitnetspam_OUTspamspamBeGonelistserv.net,
             usuvm-l%spam_OUTbrlncc.bitnetspamspamBeGonelistserv.net, EraseMEgames-lspamKILLspambrownvm.brown.edu,
             EraseMEtaxacomRemoveMEspamcmsa.berkeley.edu, .....h-asiaspamspam_OUTmsu.edu, @spam@labmgrEraseMEspamspamukcc.uky.edu,
             balt-lTakeThisOuTspamKILLspamubvm.cc.buffalo.edu, RemoveMEcompmedTakeThisOuTspamwuvmd.wustl.edu,
             @spam@int-lawSTOPspamspamvm1.spcs.umn.edu, TakeThisOuTgaelic-lTakeThisOuTspamRemoveMEirlearn.ucd.ie,
             spam_OUTnewedu-lspamspam.....uhccvm.uhcc.hawaii.edu, pnews-l.....spam@spam@sjuvm.stjohns.edu,
             spamBeGonemaps-lspamspam_OUTuga.cc.uga.edu, EraseMEmla-l.....spamiubvm.ucs.indiana.edu,
             autism%spamsjuvm.stjohns.eduh-filmKILLspamspam@spam@msu.edu,
             libraryspamspamTakeThisOuTmiamiu.acs.muohio.edu, RemoveMEjapanRemoveMEspampucc.princeton.edu,
             TakeThisOuTceth@spam@spam@spam@pucc.princeton.edu, TakeThisOuTquarkxprspamspamiubvm.ucs.indiana.edu,
             KILLspamaera-cKILLspamspamspamBeGoneasuvm.inre.asu.edu, spamBeGonejournetKILLspamspamqucdn.queensu.ca,
             macav-l@spam@spamKILLspamuafsysb.uark.edu, EraseMEsex-lRemoveMEspam@spam@tamvm1.tamu.edu,
             RemoveMEimagelibspamspamEraseMElistserv.arizona.edu, STOPspambibsoft.....spamindycms.iupui.edu,
             spamBeGonec18-lRemoveMEspamRemoveMEpsuvm.psu.edu, @spam@birdeastspamBeGonespamlistserv.arizona.edu,
             spam_OUTassessspamspamukcc.uky.edu, cdromlan%spamidbsu.bitnetspamspamspamlistserv.net,
             spamBeGoneh-rhetorKILLspamspamKILLspammsu.edu, TakeThisOuT4ad-lspamspamamerican.edu, spamBeGonenotis-lspamUICVM.CC.UIC.EDU,
             EraseMEcfs-lEraseMEspamlist.nih.gov, c+spamBeGonehealthspam_OUTspam.....iubvm.ucs.indiana.edu,
             spamdis-lspamiubvm.ucs.indiana.edu, RemoveMEmletherKILLspamspamKILLspamvm1.mcgill.ca,
             EraseMEire-lspamBeGonespamspammizzou1.missouri.edu, KILLspamccnet-lspamuga.cc.uga.edu,
             itd-jnlspam_OUTspamspamsjuvm.stjohns.edu, vbdata-lspamspam@spam@tamvm1.tamu.edu,
             circplus%spamBeGoneidbsu.bitnet.....spamlistserv.net, .....lita-l@spam@spamUICVM.CC.UIC.EDU,
             @spam@pubpol-lspamvm1.spcs.umn.edu, sag-lRemoveMEspamuafsysb.uark.edu,
             spamaaashranspamgwuvm.gwu.edu, travel-lspam_OUTspamTakeThisOuTvm.ege.edu.tr,
             spam_OUTsocwork@spam@spamRemoveMEuafsysb.uark.edu, spamfriendsspamspamcaligari.Dartmouth.EDU,
             @spam@fcr-intspam_OUTspamaliga.cesca.es, .....mac-l-requestspam.....yalevm.ycc.yale.edu,
             spamqstudy-lKILLspamspamubvm.cc.buffalo.edu, RemoveMEpsyche-dRemoveMEspamrfmh.org, KILLspamh-diplo.....spamKILLspammsu.edu,
             holocausspam_OUTspamspam_OUTUICVM.CC.UIC.EDU, KILLspamawarespam@spam@cc1.kuleuven.ac.be,
             @spam@h-urbanRemoveMEspamUICVM.CC.UIC.EDU, omri-l@spam@spamEraseMEearn.cvut.cz,
             spam_OUTibmtcp-lspam_OUTspamRemoveMEpucc.princeton.edu, RemoveMEslart-lspam.....cunyvm.cuny.edu,
             spamjewishgen@spam@spammail.eworld.com, athtrn-lTakeThisOuTspamiubvm.ucs.india
To:           Multiple recipients of list PICLIST <.....PICLISTspamTakeThisOuTmitvma.mit.edu>

                    Secured Overseas Regulatory Gaming Investments
                                                     SORGI

The Secured Overseas Regulatory Gaming Investments is a marketing group.
We have been martketing casinos for the past 10 years. Because, of the
expansion of gambling in over 21 different countries in various juristictions,
we are now able to offer you a ground floor opportunity in this regulatory
group.

Various styles of gambling are allowed by law depending on the country and
jusitiction. Casinos with only slot machines to complete Vegas or
Monte Carlo style gambling.

We have sucessfully found investement for several casinos in various countries.
Experience indicates the avarage return will be a minium of $600 US per month.

This is your opportunity to be a part of a powerful group!

ACT NOW! Send your money order for $100 US dollars to SORGI.
You will recieve your Registration Number for identifiaction and correspondence.

Secured Overseas Regulatory Gaming Investments is looking for a limited
number of members in this exclusive group. Once the required number of
members is achieved - this offer will be closed.


================================================
ACT NOW - TO JOIN THE GROUP!!
Complete the form and retun it with your $100 investment to the address below.

[   ]          I have enclosed my Investment for $100 US dollars
              (money order made payable to SORGI)
               Please send me my Registration Number in the group for
               identifcation & further correspondence.

Name:   ___________________________________________________________________

Address:   ___________________________________________________________________

City / Town:__________________________________________________________________

State/Province: _______________________________________________________________

ZIP/Postal:  __________________________________________________________________

Country:_____________________________________________________________________

E-Mail:_____________________________________________________________________

       I understand, that casinos are not developed in a day I can expect
       my first payment no sooner than 3 months (1 fiscal quarter) from
       the time of enrollment.


Signature:      ________________________________________________________________
__

================================================
Make money orders payable to SORGI and
Mail to:
       SORGI
       Suite 13, 2255 Centre Street North
       Calgary, Alberta
       Canada
       T2E 2T4

1995\08\21@054325 by Markus Imhof

flavicon
face
--========================_19125980==_
Content-Type: text/plain; charset="us-ascii"

FUCK OFF

I DID NOT REQUEST INFORMATION - YOUR SYSAD, NET-ABUSE AND BLACKLIST WILL BE
INFORMED.

Info about how to reasonably advertise on usenet appended.







{Quote hidden}

--========================_19125980==_
Content-Type: text/plain; name="spam_answer"; charset="us-ascii"
Content-Disposition: attachment; filename="spam_answer"

Path:
rz.uni-karlsruhe.de!news.rz.uni-ulm.de!zib-berlin.de!news.mathworks.com!news
.ultranet.com!usenet.eel.ufl.edu!news-feed-1.peachnet.edu!gatech!howland.res
ton.ans.net!math.ohio-state.edu!deshaw.com!do-not-use-path-to-reply
Date: Tue, 28 Feb 1995 09:00:22 GMT
Supersedes: <EraseMED3wt9F.3IJspamKILLspamdeshaw.com>
Expires: Tue, 28 Mar 1995 09:00:22 GMT
Message-ID: <D4pD0M.EAxEraseMEspamdeshaw.com>
From: EraseMEnetannouncespamspamBeGonedeshaw.com (Mark Moraes)
Subject: A Primer on How to Work With the Usenet Community
Newsgroups: news.announce.newusers,news.answers
Followup-To: news.newusers.questions
Approved: TakeThisOuTnetannouncespamTakeThisOuTdeshaw.com (Mark Moraes)
Lines: 416
Xref: rz.uni-karlsruhe.de news.announce.newusers:1049
news.answers:38725

Archive-name: usenet/primer/part1
Original-author: chuqspamspam_OUTapple.COM (Chuq Von Rospach)
Comment: enhanced & edited until 5/93 by spamspaf@spam@spamcs.purdue.edu (Gene
Spafford)
Last-change: 29 Jan 1995 by spam_OUTnetannounceTakeThisOuTspamKILLspamdeshaw.com (Mark Moraes)
Changes-posted-to: news.misc,news.answers


             A Primer on How to Work With the Usenet Community
                            Chuq Von Rospach



 *** This message describes the Usenet culture and customs that have
 developed over time.  Other documents in this newsgroup describe what
 Usenet is and manuals or on-line help on your system should provide
 detailed technical documentation.  All new users should read this
 message to acclimate themselves to Usenet. (Old users could read it,
 too, to refresh their memories.)  ***

 It is the people participating in Usenet that make it worth the
effort
 to read and maintain; for Usenet to function properly those people
must
 be able to interact in productive ways.  This document is intended as
a
 guide to using the net in ways that will be pleasant and productive
for
 everyone.

 This document is not intended to teach you how to use Usenet.
 Instead, it is a guide to using it politely, effectively and
 efficiently.  Communication by computer is new to almost everybody,
 and there are certain aspects that can make it a frustrating
 experience until you get used to them.  This document should help
 you avoid the worst traps.

 The easiest way to learn how to use Usenet is to watch how others
 use it.  Start reading the news and try to figure out what people
 are doing and why.  After a couple of weeks you will start
 understanding why certain things are done and what things shouldn't
 be done.  There are documents available describing the technical
 details of how to use the software.  These are different depending
 on which programs you use to access the news.  You can get copies of
 these from your system administrator.  If you do not know who that
 person is, they can be contacted on most systems by mailing to
 account "news", "usenet" or "postmaster".


          Never Forget that the Person on the Other Side is Human.

 Because your interaction with the network is through a computer it is
easy
 to forget that there are people "out there." Situations arise where
 emotions erupt into a verbal free-for-all that can lead to hurt
feelings.

 Please remember that people all over the world are reading your
words.  Do
 not attack people if you cannot persuade them with your presentation
of
 the facts.  Screaming, cursing, and abusing others only serves to
make
 people think less of you and less willing to help you when you need
it.

 If you are upset at something or someone, wait until you have had a
 chance to calm down and think about it.  A cup of (decaf!) coffee or
 a good night's sleep works wonders on your perspective.  Hasty words
 create more problems than they solve.  Try not to say anything to
 others you would not say to them in person in a room full of people.

           Don't Blame System Admins for their Users' Behavior.

 Sometimes, you may find it necessary to write to a system
administrator
 about something concerning his or her site.  Maybe it is a case of
the
 software not working, or a control message escaped, or maybe one of
the
 users at that site has done something you feel requires comment.  No
matter
 how steamed you may be, be polite to the sysadmin -- he or she may
not have
 any idea of what you are going to say, and may not have any part in
the
 incidents involved.  By being civil and temperate, you are more
likely to
 obtain their courteous attention and assistance.

     Never assume that a person is speaking for their organization.

 Many people who post to Usenet do so from machines at their office or
 school.  Despite that, never assume that the person is speaking for
the
 organization that they are posting their articles from (unless the
 person explicitly says so).  Some people put explicit disclaimers to
 this effect in their messages, but this is a good general rule.  If
you
 find an article offensive, consider taking it up with the person
 directly, or ignoring it.  Learn about "kill files" in your
newsreader,
 and other techniques for ignoring people whose postings you find
 offensive.

                   Be Careful What You Say About Others.

 Please remember -- you read netnews; so do as many as 3,000,000 other
 people.  This group quite possibly includes your boss, your friend's
 boss, your girl friend's brother's best friend and one of your
 father's beer buddies.  Information posted on the net can come back
 to haunt you or the person you are talking about.

 Think twice before you post personal information about yourself or
 others.  This applies especially strongly to groups like soc.singles
 and alt.sex but even postings in groups like talk.politics.misc have
 included information about the personal life of third parties that
 could get them into serious trouble if it got into the wrong hands.

                                 Be Brief.

 Never say in ten words what you can say in fewer.  Say it succinctly
and
 it will have a greater impact.  Remember that the longer you make
your
 article, the fewer people will bother to read it.

            Your Postings Reflect Upon You -- Be Proud of Them.

 Most people on Usenet will know you only by what you say and how well
you
 say it.  They may someday be your co-workers or friends.  Take some
time
 to make sure each posting is something that will not embarrass you
later.
 Minimize your spelling errors and make sure that the article is easy
to
 read and understand.  Writing is an art and to do it well requires
 practice.  Since much of how people judge you on the net is based on
your
 writing, such time is well spent.

                          Use Descriptive Titles.

 The subject line of an article is there to enable a person with a
limited
 amount of time to decide whether or not to read your article.  Tell
people
 what the article is about before they read it.  A title like "Car for
 Sale" to rec.autos does not help as much as "66 MG Midget for sale:
 Beaverton OR." Don't expect people to read your article to find out
what
 it is about because many of them won't bother.  Some sites truncate
the
 length of the subject line to 40 characters so keep your subjects
short
 and to the point.

                        Think About Your Audience.

 When you post an article, think about the people you are trying to
 reach.  Asking UNIX(*) questions on rec.autos will not reach as many
 of the people you want to reach as if you asked them on
 comp.unix.questions or comp.unix.internals.  Try to get the most
 appropriate audience for your message, not the widest.

 It is considered bad form to post both to misc.misc, soc.net-people,
 or misc.wanted and to some other newsgroup.  If it belongs in that
 other newsgroup, it does not belong in misc.misc, soc.net-people,
 or misc.wanted.

 If your message is of interest to a limited geographic area
(apartments,
 car sales, meetings, concerts, etc...), restrict the distribution of
the
 message to your local area.  Some areas have special newsgroups with
 geographical limitations, and the recent versions of the news
software
 allow you to limit the distribution of material sent to world-wide
 newsgroups.  Check with your system administrator to see what
newsgroups
 are available and how to use them.

 If you want to try a test of something, do not use a world-wide
newsgroup!
 Messages in misc.misc that say "This is a test" are likely to cause
 large numbers of caustic messages to flow into your mailbox.  There
are
 newsgroups that are local to your computer or area that should be
used.
 Your system administrator can tell you what they are.

 Be familiar with the group you are posting to before you post!  You
 shouldn't post to groups you do not read, or post to groups you've
 only read a few articles from -- you may not be familiar with the
on-going
 conventions and themes of the group.  One normally does not join
 a conversation by just walking up and talking.  Instead, you listen
 first and then join in if you have something pertinent to contribute.

                    Be Careful with Humor and Sarcasm.

 Without the voice inflections and body language of personal
 communications, it is easy for a remark meant to be funny to be
 misinterpreted.  Subtle humor tends to get lost, so take steps to
make
 sure that people realize you are trying to be funny.  The net has
 developed a symbol called the smiley face.  It looks like ":-)" and
points
 out sections of articles with humorous intent.  No matter how broad
the
 humor or satire, it is safer to remind people that you are being
funny.

 But also be aware that quite frequently satire is posted without any
 explicit indications.  If an article outrages you strongly, you
 should ask yourself if it just may have been unmarked satire.
 Several self-proclaimed connoisseurs refuse to use smiley faces, so
 take heed or you may make a temporary fool of yourself.

                         Only Post a Message Once.

 Avoid posting messages to more than one newsgroup unless you are sure
 it is appropriate.  If you do post to multiple newsgroups, do not
 post to each group separately.  Instead, specify all the groups on a
 single copy of the message.  This reduces network overhead and lets
 people who subscribe to more than one of those groups see the message
 once instead of having to wade through each copy.

             Please Rotate Messages With Questionable Content.

 Certain newsgroups (such as rec.humor) have messages in them that may
 be offensive to some people.  To make sure that these messages are
 not read unless they are explicitly requested, these messages should
 be encrypted.  The standard encryption method is to rotate each
 letter by thirteen characters so that an "a" becomes an "n".  This is
 known on the network as "rot13" and when you rotate a message the
 word "rot13" should be in the "Subject:" line.  Most of the software
 used to read Usenet articles have some way of encrypting and
 decrypting messages.  Your system administrator can tell you how the
 software on your system works, or you can use the Unix command
       tr '[a-m][n-z][A-M][N-Z]' '[n-z][a-m][N-Z][A-M]'
 Don't forget the single quotes!)

                   Summarize What You are Following Up.

 When you are following up someone's article, please summarize the
parts of
 the article to which you are responding.  This allows readers to
 appreciate your comments rather than trying to remember what the
original
 article said.  It is also possible for your response to get to some
sites
 before the original article.

 Summarization is best done by including appropriate quotes from the
 original article.  Do not include the entire article since it will
 irritate the people who have already seen it.  Even if you are
responding
 to the entire article, summarize only the major points you are
discussing.

                       When Summarizing, Summarize!

 When you request information from the network, it is common courtesy
to
 report your findings so that others can benefit as well.  The best
way of
 doing this is to take all the responses that you received and edit
them
 into a single article that is posted to the places where you
originally
 posted your question.  Take the time to strip headers, combine
duplicate
 information, and write a short summary.  Try to credit the
information to
 the people that sent it to you, where possible.

1995\08\21@054325 by Markus Imhof

flavicon
face

                     Use Mail, Don't Post a Follow-up.

 One of the biggest problems we have on the network is that when
someone
 asks a question, many people send out identical answers.  When this
 happens, dozens of identical answers pour through the net.  Mail your
 answer to the person and suggest that they summarize to the network.
This
 way the net will only see a single copy of the answers, no matter how
many
 people answer the question.

 If you post a question, please remind people to send you the answers
by
 mail and at least offer to summarize them to the network.

     Read All Follow-ups and Don't Repeat What Has Already Been Said.

 Before you submit a follow-up to a message, read the rest of the
messages
 in the newsgroup to see whether someone has already said what you
want to
 say.  If someone has, don't repeat it.

                   Check the Headers When Following Up.

 The news software has provisions to specify that follow-ups to an
 article should go to a specific set of newsgroups -- possibly
 different from the newsgroups to which the original article was
 posted.  Sometimes the groups chosen for follow-ups are totally
 inappropriate, especially as a thread of discussion changes with
 repeated postings.  You should carefully check the groups and
 distributions given in the header and edit them as appropriate.  If
 you change the groups named in the header, or if you direct
 follow-ups to a particular group, say so in the body of the message
 -- not everyone reads the headers of postings.

                 Be Careful About Copyrights and Licenses.

 Once something is posted onto the network, it is *probably* in the
 public domain unless you own the appropriate rights (most notably,
 if you wrote the thing yourself) and you post it with a valid
 copyright notice; a court would have to decide the specifics and
 there are arguments for both sides of the issue. Now that the US has
 ratified the Berne convention, the issue is even murkier (if you are
 a poster in the US).  For all practical purposes, though, assume
 that you effectively give up the copyright if you don't put in a
 notice.  Of course, the *information* becomes public, so you mustn't
 post trade secrets that way.

 When posting material to the network, keep in mind that material
 that is UNIX-related may be restricted by the license you or your
 company signed with AT&T and be careful not to violate it.  You
 should also be aware that posting movie reviews, song lyrics, or
 anything else published under a copyright could cause you, your
 company, or members of the net community to be held liable for
 damages, so we highly recommend caution in using this material.

                       Cite Appropriate References.

 If you are using facts to support a cause, state where they came
from.
 Don't take someone else's ideas and use them as your own.  You don't
want
 someone pretending that your ideas are theirs; show them the same
respect.

                   Mark or Rotate Answers and Spoilers.

 When you post something (like a movie review that discusses a detail
of
 the plot) which might spoil a surprise for other people, please mark
your
 message with a warning so that they can skip the message.  Another
 alternative would be to use the "rot13" protocol to encrypt the
message so
 it cannot be read accidentally.  When you post a message with a
spoiler in
 it make sure the word "spoiler" is part of the "Subject:" line.

                    Spelling Flames Considered Harmful.

 Every few months a plague descends on Usenet called the spelling
flame.
 It starts out when someone posts an article correcting the spelling
or
 grammar in some article.  The immediate result seems to be for
everyone on
 the net to turn into a 6th grade English teacher and pick apart each
other's
 postings for a few weeks.  This is not productive and tends to cause
 people who used to be friends to get angry with each other.

 It is important to remember that we all make mistakes, and that
 there are many users on the net who use English as a second
 language.  There are also a number of people who suffer from
 dyslexia and who have difficulty noticing their spelling mistakes.
 If you feel that you must make a comment on the quality of a
 posting, please do so by mail, not on the network.

                         Don't Overdo Signatures.

 Signatures are nice, and many people can have a signature added to
 their postings automatically by placing it in a file called
 "$HOME/.signature".  Don't overdo it.  Signatures can tell the world
 something about you, but keep them short.  A signature that is longer
 than the message itself is considered to be in bad taste.  The main
 purpose of a signature is to help people locate you, not to tell your
 life story.  Every signature should include at least your return
 address relative to a major, known site on the network and a proper
 domain-format address.   Your system administrator can give this to
 you.  Some news posters attempt to enforce a 4 line limit on
 signature files -- an amount that should be more than sufficient to
 provide a return address and attribution.

              Limit Line Length and Avoid Control Characters.

 Try to keep your text in a generic format.  Many (if not most) of
 the people reading Usenet do so from 80 column terminals or from
 workstations with 80 column terminal windows.  Try to keep your
 lines of text to less than 80 characters for optimal readability.
 If people quote part of your article in a followup, short lines will
 probably show up better, too.

 Also realize that there are many, many different forms of terminals
 in use.  If you enter special control characters in your message, it
 may result in your message being unreadable on some terminal types;
 a character sequence that causes reverse video on your screen may
 result in a keyboard lock and graphics mode on someone else's
 terminal.  You should also try to avoid the use of tabs, too, since
 they may also be interpreted differently on terminals other than
 your own.

      Please do not use Usenet as a resource for homework assignments.

 Usenet is not a resource for homework or class assignments. A common
 new user reaction to learning of all these people out there holding
 discussions is to view them as a great resource for gathering
 information for reports and papers.  Trouble is, after seeing a few
 hundred such requests, most people get tired of them, and won't reply
 anyway. Certainly not in the expected or hoped-for numbers. Posting
 student questionnaires automatically brands you a "newbie" and does
not
 usually garner much more than a tiny number of replies.  Further,
 some of those replies are likely to be incorrect.

 Instead, read the group of interest for a while, and find out what
the
 main "threads" are - what are people discussing? Are there any themes
 you can discover?  Are there different schools of thought?

 Only post something after you've followed the group for a few weeks,
 after you have read the Frequently Asked Questions posting if the
group
 has one, and if you still have a question or opinion that others will
 probably find interesting.  If you have something interesting to
 contribute, you'll find that you gain almost instant acceptance, and
 your posting will generate a large number of follow-up postings. Use
 these in your research; it is a far more efficient (and accepted) way
 to learn about the group than to follow that first instinct and post
a
 simple questionnaire.

          Please do not use Usenet as an advertising medium.

 Advertisements on Usenet are rarely appreciated.  In general, the
louder
 or more inappropriate the ad is, the more antagonism it will stir up.
 The accompanying posting "Rules for posting to Usenet" has more on
this
 in the section about "Announcement of professional products or
services".
 Try the biz.* hierarchies instead.

                  Avoid posting to multiple newsgroups.

 Few things annoy Usenet readers as much as multiple copies of a
posting
 appearing in multiple newsgroups.  (called 'spamming' for historical
 reasons) A posting that is cross-posted (i.e lists multiple
newsgroups
 on the Newsgroups: header line) to a few appropriate newsgroups is
 fine, but even with cross-posts, restraint is advised.  For a
 cross-post, you may want to set the Followup-To: header line to the
 most suitable group for the rest of the discussion.

                      Summary of Things to Remember


      Never forget that the person on the other side is human.
      Don't blame system admins for their users' behavior.
      Never assume that a person is speaking for their organization.
      Be careful what you say about others.
      Be brief.
      Your postings reflect upon you; be proud of them.
      Use descriptive titles
      Think about your audience.
      Be careful with humor and sarcasm.
      Only post a message once.
      Please rotate material with questionable content.
      Summarize what you are following up.
      Use mail, don't post a follow-up.
      Read all follow-ups and don't repeat what has already been said.
      Double-check follow-up newsgroups and distributions.
      Be careful about copyrights and licenses.
      Cite appropriate references.
      When summarizing, summarize.
      Mark or rotate answers or spoilers.
      Spelling flames considered harmful.
      Don't overdo signatures.
      Limit line length and avoid control characters.
      Please do not use Usenet as a resource for homework assignments.
      Please do not use Usenet as an advertising medium.
      Avoid posting to multiple newsgroups.

(*)UNIX is a registered trademark of X/Open.

-----------
     This document is in the public domain and may be reproduced or
     excerpted by anyone wishing to do so.




Advertising on Usenet

1. Introduction
2. Philosophy of Usenet
3. How to do it
4. How not to do it
5. Conclusion
6. Afterword: Advertising on the Internet


Introduction:
-------------

Advertising on Usenet is a frequently misunderstood subject.  The purpose
of this message is to explain some Usenet conventions regarding
advertising to new users and, hopefully, spare everyone involved a lot of
needless worry.


Philosophy of Usenet:
---------------------

Usenet started out in 1980 as a UNIX network linking sites which needed to
talk about and receive prompt updates on UNIX system configuration and
other UNIX questions, but almost immediately expanded to include forums on
science fiction, humans and computers, and other subjects.  In the decade
and a half since the creation of Usenet, a very strong onus *against*
advertising in Usenet discussion groups has grown up.

Advertising is widely seen as an 'off-topic' intrusion into the
discussions of any particular newsgroup (newsgroup is the Usenet word for
discussion group or bulletin board).  If everyone disregarded the
particular topics each newsgroup is intended to cover, and simply posted
whatever they want wherever they want, the entire system would break down.
Since no one is in charge of Usenet, and therefore no one can enforce the
custom of staying on-topic in any given newsgroup, it falls on each user
to help preserve the culture of open discussion and free speech that
Usenet has come to embody by not posting off-topic material in any
newsgroup.

This, of course, includes advertising.  Advertising is by far the most
pervasive form of off-topic posting, and therefore, gets most of the heat.

If an analogy will help you to visualize the situation, imagine a meeting
at your workplace or school.  People are discussing a certain issue -- for
example, getting new sidewalks installed downtown or getting new
schoolbooks for the elementary school.  In the midst of the discussions on
the new sidewalks or textbooks, someone walks into the room, clears their
throat, and begins to read an ad for a local restaurant.  When the person
finishes, he or she leaves without waiting for comment.

Now imagine if this happened over and over again each time you tried to
hold a meeting.  Very little would get done.  It's disruptive; it has
nothing to do with the reason the meeting was called; and worst, you're
taking up their time and not paying for it.

On Usenet, you see, if you wander into a newsgroup and post an ad for your
company in a discussion group, you're not paying for anything but the time
it took you to post it -- but thousands of computer systems around the
world are paying to receive it along with all their other Usenet messages,
and paying to store it, and so forth.  Is it any wonder people get testy
when some people ignore the no-advertising convention and make sites around
the world pay to receive advertising in a place it's not supposed to be
anyway?

That's not to say that advertising is absolutely banned from Usenet.
It's not.  It's only banned when it's off-topic.  This means that it's
considered extremely rude to post the same ad over and over to a bunch of
discussion groups without regard for what those groups are supposed to be
about, but on the other hand, it's perfectly all right to advertise in
places where your advertisement would be on-topic.

One suggestion, though: when you advertise in relevant groups, try to
keep the hype down.  Sales pitches are disliked; actual facts are not.


How to do it:
-------------

There are many newsgroups directly involved in selling.

Most of them are located in the misc.forsale hierarchy, and most of those
are related to computer buying and selling.  If you have an item to sell
which is in no way associated with computers, try
misc.forsale.non-computer (or misc.forsale, which
misc.forsale.non-computer will officially replace in a few months). Here
are all the misc.forsale groups:


misc.forsale                    General items for sale
misc.forsale.computers.d        Discussion of misc.forsale.computers.*.
misc.forsale.computers.discussion  Discussions only about items for sale.
misc.forsale.computers.mac      Apple Macintosh related computer items.
misc.forsale.computers.mac-specific.cards.misc  Macintosh expansion cards.
misc.forsale.computers.mac-specific.cards.video Macintosh video cards.
misc.forsale.computers.mac-specific.misc        Other Macintosh equipment.
misc.forsale.computers.mac-specific.portables   Portable Macintosh systems.
misc.forsale.computers.mac-specific.software    Macintosh software.
misc.forsale.computers.mac-specific.systems     Complete Macintosh systems.
misc.forsale.computers.memory   Memory chips & modules for sale & wanted.
misc.forsale.computers.modems   Modems for sale and wanted.
misc.forsale.computers.monitors Monitors and displays for sale and wanted.
misc.forsale.computers.net-hardware     Networking hardware for sale & wanted.
misc.forsale.computers.other    Selling miscellaneous computer stuff.
misc.forsale.computers.other.misc       Miscellaneous other equipment.
misc.forsale.computers.other.software   Software for other systems.
misc.forsale.computers.other.systems    Complete other types of systems.
misc.forsale.computers.pc-clone IBM PC related computer items.
misc.forsale.computers.pc-specific.audio        PC audio equipment.
misc.forsale.computers.pc-specific.cards.misc   PC expansion cards.
misc.forsale.computers.pc-specific.cards.video  PC video cards.

1995\08\21@054325 by Markus Imhof

flavicon
face
misc.forsale.computers.pc-specific.misc Other PC-specific equipment.
misc.forsale.computers.pc-specific.motherboards PC motherboards.
misc.forsale.computers.pc-specific.portables    Portable PC systems.
misc.forsale.computers.pc-specific.software     PC software.
misc.forsale.computers.pc-specific.systems      Complete PC systems.
misc.forsale.computers.printers Printers and plotters for sale and wanted.
misc.forsale.computers.storage  Disk, CDROM, tape drives for sale and wanted.
misc.forsale.computers.workstation      Workstation related computer items.
misc.forsale.non-computer       Non-computer items for sale and wanted.

There are other options as well:

1) If and only if you are with a computer company which is releasing a new
product and you want to make word of this new product known to the
computing community, you can post a notice to the moderated newsgroup
comp.newprod.  The moderator, Chip Rosenthal, requires submissions to be
informative and hype-free so people will use comp.newprod as a reliable
way of gaining information.

2) Each part of the world tends to have what's called a 'local hierarchy
of newsgroups' -- newsgroups limited to a geographic area.  For example,
central North Carolina (home of the so-called Raleigh/Durham/Chapel Hill
"Research Triangle") has a local hierarchy called triangle.*.  In your
local hierarchy, if one exists (and not everyone has one, but most people
do), you'll often find groups with names like *.classifieds, *.forsale,
*.wanted: triangle.forsale and triangle.wanted are the groups in the
aforementioned triangle.* hierarchy.

3) There is a hierarchy of newsgroups called "biz.*" which exist mainly
for announcement from companies of new products, fixes and enhancements,
postings of demo software, and so forth.  If your site carries biz.*, and
you feel that a biz.* hierarchy group would suit your purposes, go to
biz.config and ask for it.

Here are existing biz.* groups:

biz.americast           AmeriCast announcements.
biz.americast.samples   Samples of AmeriCast. (Moderated)
biz.books.technical     Technical bookstore & publisher advertising & info.
biz.clarinet            Announcements about ClariNet.
biz.clarinet.sample     Samples of ClariNet newsgroups for the outside world.
biz.comp.accounting     Dialogue specific to the accounting software industry.
biz.comp.hardware       Generic commercial hardware postings.
biz.comp.mcs            MCSNet. (Moderated)
biz.comp.services       Generic commercial service postings.
biz.comp.software       Generic commercial software postings.
biz.comp.telebit        Support of the Telebit modem.
biz.comp.telebit.netblazer      The Telebit Netblazer.
biz.config              Biz Usenet configuration and administration.
biz.dec                 DEC equipment & software.
biz.dec.decathena       DECathena discussions.
biz.dec.decnews         The DECNews newsletter. (Moderated)
biz.dec.ip              IP networking on DEC machines.
biz.digex.announce      Announcements from Digex. (Moderated)
biz.digital.announce    DEC news & announcements. (Moderated)
biz.digital.articles    DEC newsletter, catalog & journal. (Moderated)
biz.general             Dialogue related to business operations & offerings.
biz.jobs.offered        Position announcements.
biz.misc                Miscellaneous postings of a commercial nature.
biz.next.newprod        New product announcements for the NeXT.
biz.oreilly.announce    New prod. announcements from O'Reilly & Assoc. (Mod)
biz.pagesat             For discussion Pagesat Satellite Usenet Newsfeed.
biz.sco.announce        SCO and related product announcements. (Moderated)
biz.sco.binaries        Binary packages for SCO Xenix, UNIX, or ODT. (Mod)
biz.sco.general         Q&A, discussions and comments on SCO products.
biz.sco.magazine        To discuss SCO Magazine and its contents.
biz.sco.opendesktop     ODT environment and applications tech info, q&a.
biz.sco.sources         Source code ported to an SCO operating env. (Mod)
biz.sco.vtcl            SCO Visual Tcl.
biz.stolen              Postings about stolen merchandise.
biz.stortek.forum       Storage Technology Corporation.
biz.tadpole.sparcbook   Discussions on the Sparcbook portable computer.
biz.test                Biz newsgroup test messages.
biz.univel.misc         Discussions and comments on Univel products.
biz.zeos.announce       Zeos Product Announcements. (Moderated)
biz.zeos.general        Zeos technical support and general information.

Not every company's goods will be appropriate for a biz.* hierarchy
newsgroup, and not every site will carry biz.*.  It's up to the people
who run your particular site.

4) If you or your company have an advertisement that's relevant to an
existing newsgroup or newsgroups you can post informational postings to
those newsgroups.  However, you are strongly encouraged to keep such
postings hype-free.  What often works very well is to post information
about your services or product and include a contact address, World Wide
Web site, or phone number for people to use to get more information.

For example, if you want to post a notice about your immigration law
services, you could post a message to alt.visa.us or the various
misc.immigration newsgroups, where you'd find a large population of people
interested in that or related subjects.  Posting the same ad to
rec.sport.football.college would *not* be appropriate because
rec.sport.football.college has nothing to do with immigration law, visas,
or becoming an American citizen.

This is not to say that such ads will always be welcome; the proliferation
of inappropriate ads (ads posted in the wrong way to the wrong place) has
resulted in *all* ads, even informational ads posted to the appropriate
newsgroup, tending to get a cold shoulder if not worse.  You can help by
limiting your ads to *informational* postings posted *only* *where*
*appropriate*.

5) In certain cases, you will find groups with 'marketplace' in their
names... for example, rec.games.board.marketplace.  Groups with that word
in their name are intended for buying, selling, and trading items of that
subject or type; for example, rec.games.board.marketplace is the
appropriate place to post a notice if you have a vintage copy of Monopoly
or Diplomacy to sell.

How not to do it
----------------

Unfortunately, there are just about as many *inappropriate* ways to
advertise on Usenet as there are appropriate ways.

1) The first way NOT to do it is to post off-topic ads in off-topic
newsgroups.

For example, you run a rug company.  So you post an advertisement about
your rugs in news.newusers.questions.  Not surprisingly, a lot of people
send you email telling you what a jerk you are.

Why'd they do this, you ask?  It's simple: news.newusers.questions has
nothing to do with selling rugs.  Your ad was as off-topic as if someone
had tried to get a discussion going there about the upcoming football
season or started posting a lot of messages about their recent vacation.

Suppose you own that rug company, and you regularly read
rec.crafts.textiles.weaving.  Would you like it if someone started coming
in and posting a lot of ads to the newsgroup about some homeopathic
ginseng tablets, and then someone else came in and started trying to sell
magazine subscriptions, and it became hard to find discussion of weaving?

"Do unto others as you would have them do unto you" isn't just a good
idea on Usenet.  It's the way things are, and if you act rudely by
posting ads in newsgroups that have nothing to do with what you're
advertising, people will be very unhappy with you.

2) Spamming.

Spamming is defined as posting identical or nearly-identical ads to a lot
of newsgroups, one right after the other.  Since it's really not that
difficult to write a program that will post the same advertisement to
dozens, if not hundreds or thousands of newsgroups, a lot of people have
taken to doing this.

What's happened to people who've spammed?

They've lost their accounts, been mail-bombed (had thousands of pieces of
junk email sent to them), had people call up and yell at them in the
middle of the night, had people forward their mail (by this I mean MAIL
mail, not email) to someplace strange, had people sign them up for
thousands of unwanted magazine subscriptions, had people send them
thousands of pages of condemnatory faxes, and so forth.

*Nothing* is as hated on Usenet as spamming.  It's extremely, unbelievably
rude and if you do it, you *will* come to regret it.  This is not a threat
-- it's an observation. Any benefits spamming might have brought you will
be more than counteracted by the intense public outcry against you in
every newsgroup you posted your ad to.

Some members of the media have gotten the mistaken impression that
spamming is hated because it's *advertising*.  It's true that Usenet
readers don't have much fondness for advertising, but the real reason
spamming is hated so much is because it's unbelievably *rude*.  Each copy
of the ad takes up disk space on thousands of machines around the world --
and if you post the ad 1000 times, that's millions of copies of your
message that *you* are making other people pay to store copies of.  When
you spam, you're hogging hundreds of thousands of dollars worth of other
people's storage space.

So please, don't do it.  I've already explained that *one* copy of an
off-topic ad is rude because it has nothing to do with the group it was
posted to.  Multiply that by a thousand times to get an idea of how rude
it is to spam.

Another consideration against spamming is that Usenet readers developed
defenses against it, so it's not very effective.  There are quite a few
spam detectors running on Usenet, and if one of them detects that the same
message has been posted repeatedly to multiple newsgroups, the humans who
run those spam detectors will step in and actually *erase* the spamming
messages with 'cancel' messages which are honored at most sites around the
world.

A common misconception shared by many members of the media is that
spam is bad because it's *advertising* and that people who cancel spam are
doing so to get rid of *advertising*.  In actual point of fact, most
Usenet users consider cancellation to be extremely bad manners and
something to be done only as a last resort.  When spam-cancellers cancel
spam, it's done because of the *volume* (posting hundreds of times), not
because of the content.

The analogy that's often used is that yes, you have the right to walk down
the street and say whatever you like -- but you do NOT have the right to
stick your head in someone's house at 3 am and shout through a bullhorn.

So if you *do* spam, you're likely to lose your account, have your
personal life made a living hell, possibly get sued by people whose
storage space you're taking up, and not very many people are going to pay
attention to or even see your advertisement.   It's just plain not worth
the grief you'll get.

Sorry to be unpleasant about it, but spam's a really bad idea.

Finally, if you're wondering where the term "spamming" came from, it came
from a Monty Python sketch in which the characters were in a restaurant
which mainly sold spam.  Items on the menu included things like "spam,
spam, spam, eggs, ham, and spam."  Whenever the waitress recited the menu,
a group of Vikings in the corner would chime in with her, chanting the
word "spam" over and over, drowning out everything else.  Some members of
the media have spread the explanation that the word "spamming" derives
from throwing chunks of spam into a fan.  This is not the case.

3) Don't send unsolicited ads via email to people you've seen post.

Another often-practiced and often-punished scheme is to send email to
mailing lists compiled from various newsgroups; people who've posted to
this group or that in the last two weeks wind up on occasion getting ads
for timeshare condos in Cancun or dubious credit schemes.

Suffice it to say that junk email, using Usenet posters' addresses, is
also a really bad idea.  Most sites will yank your account if you do that
kind of thing.

4) Don't mail-merge ads either in order to avoid being called a spammer.

Some advertisers noticed that it was only *identical* postings that were
getting cancelled by the spam cancellers, and cleverly came up with a way
to post their ad to dozens of newsgroups while varying a line or two to
make it look sufficiently different to avoid being cancelled.

For example, one book editor posted ads to dozens of newsgroups about his
book, essentially giving a sales pitch for said book, while adding a
paragraph to each article that purported to contain the text that had been
printed about the given newsgroup in said book.  It was rather obvious
that the editor wasn't interested in getting comments on the text, since
the book had already been published, and eventually an employee at the
company admitted that the technique had been used to try to avoid
triggering the spam cancellers and that the point had indeed been to
broadcast the ad widely.

It's to your ultimate benefit *not* to do the Usenet equivalent of
sweepstakes ads; don't do postings that say things like "Congratulations,
REC.FOOD.DRINK.BEER reader, you are among the lucky few to be included in
this amazing offer."

Conclusion
----------

To make a long story short, off-topic advertising and advertising that
equates to a bullhorn stuck into someone's window in the middle of the
night is a bad idea.  *Please* exercise restraint and don't make the
mistake many have of thinking that just because there's no central
authority that can punish you for spamming newsgroups, that there will be
no consequences if you do.  There will be, and you might be surprised by
the lengths the vengeful Usenet readers can go to when someone spams their
favorite group with yet another off-topic advertisement.  If you want to
advertise on Usenet, you can, but please follow the tips contained in
this document's "How to do it"s section and don't make the mistakes
listed in "How not to do it."


Afterword: Advertising on the Internet
--------------------------------------

It should be noted that there are many ways to advertise on the
Internet that don't involve Usenet at all.  Usenet, you see, is NOT the
same thing as the Internet.  Usenet is transmitted via the Internet, but
is also transmitted via other means (See "What is Usenet" in
news.announce.newusers for more information).  The Internet also includes
services like ftp, telnet, gopher, and the World Wide Web, and no one's
going to cause you the least difficulty if you use them to advertise.

As a matter of fact, thousands of companies have their very own WWW pages
up for people around the planet to use, look at, and get information
from.  A World Wide Web page allows you to put up graphics, text, and
sound in an interactive hypertext format that's remarkably easy to set up
and use via a program like Mosaic or Netscape.

So, here's a parting tip: if you want to advertise via the Internet, get
a WWW page set up, then let people in appropriate newsgroups (and
elsewhere) know where to find it.  If you need help getting going, ask
the people who run your site or scout out the Usenet newsgroup
comp.infosystems.http://www.misc for help.  It's really not that hard to set up
a WWW page, and hey, if you build it, they will come.

Just don't spam anyone in the process, and you'll be all right.



--========================_19125980==_--

1995\08\21@054526 by Markus Imhof

flavicon
face
Oops - I'm terribly sorry. I tried to reply to sorgi, but accidentially
reposted the stuff to the list - with a large attachment file from
.newusers. Please thrash the stuff if you happen to run accross it, and
accept my apologies.

Bye
 Markus

1995\08\21@061632 by Colin Manning

picon face
> Forwarded by:   "Ian Munro" <ELESVR1/ELEQIM>
> Forwarded to:   eleqcm
> Date forwarded: Mon, 21 Aug 1995 08:39:02 +0100 (BST)
> Date sent:      Sun, 20 Aug 1995 17:00:37 -0600
> Send reply to:  pic microcontroller discussion list
<PICLIST%RemoveMEMITVMA.BITNET@spam@spamspamletterbox.rl.ac.uk>
> From:           SORGI <RemoveMEsorgiRemoveMEspamTakeThisOuTTIBALT.SUPERNET.AB.CA>
> Subject:        Information as per your request.
> Originally to:  pahTakeThisOuTspam@spam@canuck.com, toptenTakeThisOuTspamspamBeGonelistserv.clark.net,
spamtidbitsTakeThisOuTspamricevm1.rice.edu,
>                 .....new-listspamspamBeGonevm1.nodak.edu, .....india-lTakeThisOuTspamEraseMEindnet.bgsu.edu,
>                 RemoveMEomri-lspamspamKILLspamubvm.cc.buffalo.edu, STOPspamccman-lEraseMEspamuga.cc.uga.edu,
>                 india-dspamBeGonespamindnet.bgsu.edu, pacs-l@spam@spamuhupvm1.uh.edu,
>                 spam_OUTchina-ndspamspamkentvm.kent.edu, fedjobsspam_OUTspamRemoveMEcaligari.Dartmouth.EDU,
>                 spamchan-msgspamBeGonespamitssrv1.ucsf.edu, spamlookingRemoveMEspamindnet.bgsu.edu,
>                 KILLspamisraelinespam_OUTspamspam_OUTtaunivm.tau.ac.il, macchatspam_OUTspamTakeThisOuTvm.temple.edu,
>                 spamBeGonechina-nnspamspamspamBeGoneasuvm.inre.asu.edu, @spam@tesl-lspamspamspam_OUTcunyvm.cuny.edu,
>                 KILLspamlate-show-newsspamKILLspamamerican.edu, KILLspamjamestown-lspamspamspameva.dc.LSOFT.COM,
>                 germnewsKILLspamspam.....vm.gmd.de, humorspamBeGonespamuga.cc.uga.edu,
online-lspamspam_OUTlistserv.clark.net,
>                 .....linguistRemoveMEspamKILLspamtamvm1.tamu.edu, TakeThisOuTucsmonKILLspamspam.....iubvm.ucs.indiana.edu,
>                 nnewsspam_OUTspamspamBeGonevm1.nodak.edu, cndpsu-l.....spam@spam@psuvm.psu.edu,
@spam@cmpsu-lspamspampsuvm.psu.edu,
>                 spam_OUTroots-lspamBeGonespamspamBeGonevm1.nodak.edu, libref-lRemoveMEspamTakeThisOuTkentvm.kent.edu,
TakeThisOuTtftd-lKILLspamspamtamvm1.tamu.edu,
{Quote hidden}

RemoveMEslajob-lspamspamiubvm.ucs.indiana.edu,
>                 KILLspamcndvt-lspamspamspam_OUTvtvm1.cc.vt.edu, spamcica-l.....spamTakeThisOuTubvm.cc.buffalo.edu,
>                 deosnews@spam@spamspam_OUTpsuvm.psu.edu, STOPspamchina-nnspamutarlvm1.uta.edu,
>                 EraseMEnewslinespam_OUTspamvm.its.rpi.edu, inter-lKILLspamspamspamvtvm1.cc.vt.edu,
TakeThisOuTintercatKILLspamspamoclc.org,
>                 spamcnc-l.....spam@spam@uvvm.uvic.ca, spam_OUTnettrainspamspamubvm.cc.buffalo.edu,
EraseMEcpsrspamBeGonespamgwuvm.gwu.edu,
>                 EraseMEpsyche-lspam_OUTspamspamrfmh.org, bugtraqspam_OUTspamnetspace.org, spam_OUTedtechTakeThisOuTspamKILLspammsu.edu,
>                 TakeThisOuTvmwkshopspamvm.marist.edu,
pm-news%spamua1vm.ua.educhina-ntspam_OUTspamuga.cc.uga.edu,
{Quote hidden}

tesljb-lTakeThisOuTspamspam_OUTcunyvm.cuny.edu,
>                 STOPspamcfs-newsspamspam_OUTlist.nih.gov, EraseMEacadv@spam@spamTakeThisOuTvm1.nodak.edu,
spamBeGoneepaaSTOPspamspamspam_OUTasuvm.inre.asu.edu,
>                 .....epic-l@spam@spamRemoveMEoclc.org, spamBeGonewin95-l.....spamspam_OUTeva.dc.LSOFT.COM,
macprog@spam@spamspamBeGonewuvmd.wustl.edu,
>                 spamBeGonecontentsEraseMEspamacadvm1.uottawa.ca, honda-lspamspamBeGonebrownvm.brown.edu,
>                 spam_OUTinnopacKILLspamspam.....maine.maine.edu,
africa-n%STOPspamutoronto.bitnetRemoveMEspamKILLspamlistserv.net,
>                 @spam@visbas-lspam_OUTspamlistserv.tamu.edu, RemoveMEjte-l.....spamspamBeGonevtvm1.cc.vt.edu,
>                 spam_OUTctheoryKILLspamspamTakeThisOuTvm1.mcgill.ca, edres-l.....spam.....unbvm1.csd.unb.ca,
>                 TakeThisOuTteslej-lspamspamcmsa.berkeley.edu, KILLspame-europe@spam@spamKILLspampucc.princeton.edu,
>                 natodataspam_OUTspamKILLspamcc1.kuleuven.ac.be,
usumts-l%EraseMEbrlncc.bitnet@spam@spamTakeThisOuTlistserv.net,
>                 nursenet%spamBeGoneutoronto.bitnetEraseMEspamspamBeGonelistserv.net, rptcrdEraseMEspamgwuvm.gwu.edu,
>                 wfw-l%umdd.bitnetspamlistserv.net, RemoveMEpmailEraseMEspamspamBeGoneua1vm.ua.edu,
>                 RemoveMEbig-lanSTOPspamspamlistserv.syr.edu, RemoveMEtrdev-lspampsuvm.psu.edu,
spamh-womenRemoveMEspamRemoveMEmsu.edu,
>                 EraseMEpakistanKILLspamspamRemoveMEpsuvm.psu.edu, EraseMEaspire-lKILLspamspamiubvm.ucs.indiana.edu,
>                 spamareport.....spamTakeThisOuTitesmvf1.rzs.itesm.mx, TakeThisOuTtechwr-lTakeThisOuTspamTakeThisOuTvm1.ucc.okstate.edu,
>                 KILLspammde-lEraseMEspammizzou1.missouri.edu,
RemoveMEkidlit-l.....spamEraseMEbingvmb.cc.binghamton.edu,
>                 nihtoc-lTakeThisOuTspamspamBeGonelist.nih.gov, spam_OUTalctsKILLspamspam@spam@UICVM.CC.UIC.EDU,
spamill-lspamuvmvm.uvm.edu,
>                 spammacscrptspam_OUTspamcaligari.Dartmouth.EDU,
fapesp-l%spamBeGonebruspvm.bitnetspamspamlistserv.net,
>                 spam_OUTcruise-lSTOPspamspamTakeThisOuTunlvm.unl.edu,
pgssnews%KILLspamvm1.mcgill.canihongoEraseMEspammitvma.mit.edu,
>                 direct-lspamspamuafsysb.uark.edu, exlibrisspamBeGonespam@spam@rutvm1.rutgers.edu,
>                 STOPspamisworld.....spamEraseMEirlearn.ucd.ie, sbpchoje%brlncc.bitnetspamBeGonespamTakeThisOuTlistserv.net,
>                 KILLspampagemakrTakeThisOuTspamTakeThisOuTindycms.iupui.edu, EraseMEclayartspamspamBeGoneukcc.uky.edu,
>                 spam_OUTmuseum-lEraseMEspam.....unmvma.unm.edu, spamberita-lspamvmd.cso.uiuc.edu,
>                 KILLspamicen-lspamspamEraseMEiubvm.ucs.indiana.edu, arch-lRemoveMEspamSTOPspamtamvm1.tamu.edu,
spam_OUTh-amstdyspam_OUTspamKILLspammsu.edu,
>                 .....pakistanspamspamasuvm.inre.asu.edu, spamBeGonelastwedsspam.....listserv.clark.net,
>                 TakeThisOuTcrtnetTakeThisOuTspamRemoveMEpsuvm.psu.edu, RemoveMEhelp-netKILLspamspamRemoveMEvm.temple.edu,
spamBeGonepu-newsspamspamvm.cc.purdue.edu,
>                 mdk-12%spamBeGoneumdd.bitnet@spam@spamTakeThisOuTlistserv.net, KILLspamansax-lRemoveMEspamwvnvm.wvnet.edu,
>                 EraseMEair-l.....spamvtvm1.cc.vt.edu, spamBeGonecomics-l.....spamKILLspamunlvm.unl.edu,
TakeThisOuTcommcollspam_OUTspamKILLspamukcc.uky.edu,
>                 EraseMEenews-outEraseMEspam@spam@mail.eworld.com, psrt-lEraseMEspammizzou1.missouri.edu,
>                 .....activ-l@spam@spamspam_OUTmizzou1.missouri.edu,
ufrjncen%ufrj.bitnetspam_OUTspamspam_OUTlistserv.net,
>                 TakeThisOuTjobplaceSTOPspamspamTakeThisOuTnews.jobweb.org, STOPspamcar-eng@spam@spamearn.cvut.cz,
>                 @spam@teslca-lRemoveMEspamcunyvm.cuny.edu, TakeThisOuTnetmonthEraseMEspamvm.marist.edu,
>                 RemoveMEmediev-l.....spamukanvm.cc.ukans.edu,
dairy-l%RemoveMEumdd.bitnet.....spamlistserv.net,
>                 spamBeGoneh-womenTakeThisOuTspamUICVM.CC.UIC.EDU, oracle-lKILLspamspam@spam@ccvm.sunysb.edu,
>                 psygrd-jKILLspamspamKILLspamacadvm1.uottawa.ca, spambestwebspamBeGonespam@spam@vm.ege.edu.tr,
>                 spamwx-talkspamvmd.cso.uiuc.edu, KILLspammarmamKILLspamspamspamuvvm.uvic.ca,
>                 RemoveMEchminf-lspamspam.....iubvm.ucs.indiana.edu, EraseMEnetscapeKILLspamspamspam_OUTirlearn.ucd.ie,
>                 aeraTakeThisOuTspamasuvm.inre.asu.edu, @spam@indiaSTOPspamspamcunyvm.cuny.edu,
>                 EraseMEnative-l.....spamEraseMEtamvm1.tamu.edu, spamcwis-l@spam@spammsu.edu,
spam_OUTnatoscispam_OUTspamspamBeGonecc1.kuleuven.ac.be,
>                 .....bgrass-lSTOPspamspamukcc.uky.edu, STOPspamir-l@spam@spamuccvma.ucop.edu,
>                 @spam@fish-ecologyEraseMEspamsearn.sunet.se, spam_OUTkidcafespamvm1.nodak.edu,
>                 spamsonic-verse.....spamTakeThisOuTvm.marist.edu, TakeThisOuTpns-l@spam@spamTakeThisOuTpsuvm.psu.edu,
quiltnetspamspamukcc.uky.edu,
>                 EraseMEphilosopspam_OUTspamspamvm1.yorku.ca, gardensSTOPspamspamukcc.uky.edu,
EraseMEchemed-lspam@spam@uwf.cc.uwf.edu,
>                 TakeThisOuTseasia-l.....spamTakeThisOuTmsu.edu, buslib-l%spam_OUTidbsu.bitnet@spam@spamSTOPspamlistserv.net,
>                 TakeThisOuTqualrs-lKILLspamspamKILLspamuga.cc.uga.edu, winhlp-lSTOPspamspamRemoveMEadmin.humberc.on.ca,
>                 spamBeGonehum-molgenspam@spam@nic.surfnet.nl,
spam_OUTeducational-research@spam@spamEraseMEasuvm.inre.asu.edu,> >                 KILLspamankietaKILLspamspamplearn.edu.pl, spamBeGonevolcanospamRemoveMEasuvm.inre.asu.edu,
>                 spamanthro-lEraseMEspamubvm.cc.buffalo.edu, devel-lspamBeGonespamamerican.edu,
>                 e-poetry%ubvm.cc.buffalo.eduwindowsspamTakeThisOuTvm1.mcgill.ca,> stat-lspam_OUTspamvm1.mcgill.ca,
>                 spamarlis-lspamukcc.uky.edu, EraseMEinfo-macKILLspamspamRemoveMEvmd.cso.uiuc.edu,
spam_OUTtheoryntTakeThisOuTspam@spam@vm1.nodak.edu,
>                 RemoveMEblues-l@spam@spamRemoveMEbrownvm.brown.edu,
newnir-l%spamBeGoneitocsivm.bitnetspam_OUTspamlistserv.net,
>                 TakeThisOuTbbshopspam.....admin.humberc.on.ca, KILLspamasis-lspamspamvmd.cso.uiuc.edu,
>                 nurseresTakeThisOuTspamRemoveMEkentvm.kent.edu, EraseMEscupnews@spam@spamcmsa.berkeley.edu,
>                 vocnetspamBeGonespamKILLspamcmsa.berkeley.edu, .....primaryKILLspamspamRemoveMEumrvmb.umr.edu,
EraseMEtelugu.....spam@spam@vm1.nodak.edu,
>                 flyfishRemoveMEspamKILLspamukcc.uky.edu, spam_OUTsas-lspam_OUTspam.....uga.cc.uga.edu,
spamtec-tenEraseMEspam.....sjuvm.stjohns.edu,
>                 toolb-l.....spam@spam@listserv.arizona.edu, victoriaspamiubvm.ucs.indiana.edu,
>                 STOPspamsuearn-lspam_OUTspamRemoveMEubvm.cc.buffalo.edu, reachKILLspamspamucsbvm.ucsb.edu,
>                 TakeThisOuTcumrec-lRemoveMEspamvm1.nodak.edu, spamBeGoneheproc-lTakeThisOuTspamamerican.edu,
>                 RemoveMEmedtextlspamspamvmd.cso.uiuc.edu, RemoveMEconslinkspamsivm.si.edu,
spamh-teachKILLspamspamKILLspammsu.edu,
>                 TakeThisOuThumanistKILLspamspam.....brownvm.brown.edu, @spam@acsoft-lspamBeGonespamwuvmd.wustl.edu,
>                 @spam@ioob-lspam_OUTspamuga.cc.uga.edu, spam_OUThytel-lTakeThisOuTspamEraseMEkentvm.kent.edu,
>                 RemoveMEflteachspamspamKILLspamubvm.cc.buffalo.edu, h-rhetorspamUICVM.CC.UIC.EDU,
>                 mitbayspam_OUTspammitvma.mit.edu, EraseMEipct-lRemoveMEspamEraseMEguvm.ccf.georgetown.edu,
>                 media-lspambingvmb.cc.binghamton.edu,
childlit.....spamrutvm1.rutgers.edu,
>                 RemoveMEpsycgradEraseMEspamacadvm1.uottawa.ca, TakeThisOuTmentor-lRemoveMEspamvm.its.rpi.edu,
>                 @spam@christiaspamRemoveMEasuvm.inre.asu.edu, nsc94-lRemoveMEspamgumncc.earn.net,
>                 .....k12adminSTOPspamspamTakeThisOuTlistserv.syr.edu, EraseMEe-clipsspamspam_OUTsjuvm.stjohns.edu,
>                 spamBeGonejwaspam_OUTspamubvm.cc.buffalo.edu, RemoveMEcybsys-lRemoveMEspambingvmb.cc.binghamton.edu,
>                 sts-l.....spamKILLspamutkvm1.utk.edu, access-lSTOPspamspamRemoveMEeva.dc.LSOFT.COM,
>                 TakeThisOuTvpiej-lspamvtvm1.cc.vt.edu, STOPspammtg-lTakeThisOuTspamoracle.wizards.com,
>                 .....scit-bibspamqucdn.queensu.ca, TakeThisOuTbirdchatspamlistserv.arizona.edu,
>                 .....poli-sciKILLspamspam@spam@rutvm1.rutgers.edu,
shaksper%utoronto.bitnetspamspamRemoveMElistserv.net,
>                 usuvm-l%TakeThisOuTbrlncc.bitnetspamBeGonespamRemoveMElistserv.net, TakeThisOuTgames-l.....spambrownvm.brown.edu,
>                 spam_OUTtaxacomspam_OUTspamcmsa.berkeley.edu, KILLspamh-asiaRemoveMEspamspammsu.edu,
labmgrRemoveMEspam@spam@ukcc.uky.edu,
>                 balt-lKILLspamspamTakeThisOuTubvm.cc.buffalo.edu, TakeThisOuTcompmed.....spamRemoveMEwuvmd.wustl.edu,
>                 int-lawspamEraseMEvm1.spcs.umn.edu, @spam@gaelic-lspamirlearn.ucd.ie,
>                 RemoveMEnewedu-lRemoveMEspamRemoveMEuhccvm.uhcc.hawaii.edu, EraseMEpnews-lspam_OUTspamSTOPspamsjuvm.stjohns.edu,
>                 KILLspammaps-lRemoveMEspam.....uga.cc.uga.edu, @spam@mla-l.....spam.....iubvm.ucs.indiana.edu,
>                 autism%.....sjuvm.stjohns.eduh-filmRemoveMEspammsu.edu,
TakeThisOuTlibraryspamKILLspammiamiu.acs.muohio.edu,
>                 spam_OUTjapanspamspamEraseMEpucc.princeton.edu, spam_OUTcethspamEraseMEpucc.princeton.edu,
>                 KILLspamquarkxprKILLspamspam@spam@iubvm.ucs.indiana.edu, @spam@aera-c@spam@spamTakeThisOuTasuvm.inre.asu.edu,
>                 spam_OUTjournet@spam@spamSTOPspamqucdn.queensu.ca, spam_OUTmacav-lKILLspamspamuafsysb.uark.edu,
>                 TakeThisOuTsex-lspamBeGonespamtamvm1.tamu.edu, imagelibTakeThisOuTspamlistserv.arizona.edu,
>                 spambibsoft.....spamindycms.iupui.edu, c18-lspampsuvm.psu.edu,
>                 EraseMEbirdeastspamspamBeGonelistserv.arizona.edu, spamassessKILLspamspamukcc.uky.edu,
>                 cdromlan%spam_OUTidbsu.bitnetKILLspamspam.....listserv.net, h-rhetorKILLspamspamSTOPspammsu.edu,
>                 EraseME4ad-lEraseMEspamspam_OUTamerican.edu, notis-lKILLspamspamUICVM.CC.UIC.EDU,
spamBeGonecfs-lspamRemoveMElist.nih.gov,
>                 c+healthKILLspamspamiubvm.ucs.indiana.edu, @spam@dis-l.....spamiubvm.ucs.indiana.edu,
>                 TakeThisOuTmletherspam_OUTspam.....vm1.mcgill.ca, ire-lEraseMEspamEraseMEmizzou1.missouri.edu,
>                 @spam@ccnet-lRemoveMEspamRemoveMEuga.cc.uga.edu, .....itd-jnlEraseMEspamsjuvm.stjohns.edu,
>                 vbdata-lEraseMEspamRemoveMEtamvm1.tamu.edu, circplus%@spam@idbsu.bitnet.....spamRemoveMElistserv.net,
>                 .....lita-l.....spam.....UICVM.CC.UIC.EDU, RemoveMEpubpol-lspamBeGonespam@spam@vm1.spcs.umn.edu,
>                 KILLspamsag-lTakeThisOuTspam.....uafsysb.uark.edu, KILLspamaaashranspam_OUTspamspam_OUTgwuvm.gwu.edu,
RemoveMEtravel-lspamBeGonespam.....vm.ege.edu.tr,
>                 socworkspamEraseMEuafsysb.uark.edu, RemoveMEfriends@spam@spamspamBeGonecaligari.Dartmouth.EDU,
>                 spamBeGonefcr-intTakeThisOuTspamaliga.cesca.es, spammac-l-requestspamspamBeGoneyalevm.ycc.yale.edu,
>                 TakeThisOuTqstudy-lspam_OUTspamTakeThisOuTubvm.cc.buffalo.edu, psyche-dspamBeGonespamEraseMErfmh.org,
spamBeGoneh-diplospamspam_OUTmsu.edu,
>                 spamBeGoneholocausspamspamUICVM.CC.UIC.EDU, awarespamspam_OUTcc1.kuleuven.ac.be,
>                 spamh-urban@spam@spamEraseMEUICVM.CC.UIC.EDU, KILLspamomri-lspamearn.cvut.cz,
>                 spamibmtcp-lspamKILLspampucc.princeton.edu, @spam@slart-lRemoveMEspamcunyvm.cuny.edu,
>                 RemoveMEjewishgenspamspamEraseMEmail.eworld.com, .....athtrn-lSTOPspamspam@spam@iubvm.ucs.india
> To:             Multiple recipients of list PICLIST
<PICLIST%.....MITVMA.BITNETspamBeGonespam.....letterbox.rl.ac.uk>

{Quote hidden}

countries.
> Experience indicates the avarage return will be a minium of $600 US per month.
>
> This is your opportunity to be a part of a powerful group!
>
> ACT NOW! Send your money order for $100 US dollars to SORGI.
> You will recieve your Registration Number for identifiaction and
correspondence.
{Quote hidden}

_______________________________________________________________
>
> ZIP/Postal:
__________________________________________________________________
{Quote hidden}

__________________________________________________________________
>
> ================================================
> Make money orders payable to SORGI and
> Mail to:
>         SORGI
>         Suite 13, 2255 Centre Street North
>         Calgary, Alberta
>         Canada
>         T2E 2T4

What is this all about pleaser inlighten me


----------------------------------------------------------------------
 Colin Manning Technican   Elec.Eng. University of Hertfordshire
               Hatfield  England Tel 01707 284160
----------------------------------------------------------------------

1995\08\21@085416 by David Warman

flavicon
face
>                     Secured Overseas Regulatory Gaming Investments

This is a very convenient acronym.  Consider this:

Script started on Mon Aug 21 12:09:11 1995
1 >telnet tibalt.supernet.ab.ca 25
Trying 198.161.21.5 ...
Connected to tibalt.supernet.ab.ca.
Escape character is '^]'.
220-tibalt.supernet.ab.ca HP Sendmail (1.37.109.16/16.2) ready at Mon, 21 Aug
1995 05:09:30 -0600
220 ESMTP spoken here
VRFY SORGI
250 Tony Sorgi <@spam@sorgispamRemoveMEtibalt.supernet.ab.ca>
QUIT
221 tibalt.supernet.ab.ca closing connection
Connection closed by foreign host.
2 >^D
script done on Mon Aug 21 12:09:43 1995

So, is "Tony" another convenient abbreviation, or is this just bizarre
co-incidence.  Enquring minds have probably already formed some
conclusions.  I do wonder whether this is legal?

Back to PICLIST things, I suppose this an example of the sort
of spammage we can expect as a mailing list.  On the other hand,
the overall S/N is pretty reasonable.

My main concern is that propagation would be slower if this were
a newsgroup.  We would probably also get a lot more totally irrelevant
junk (just opinion, since we'd be open to more cross-posting).

Out of interest, how many people receive this list anyway?  If there
are lots of  people here, then perhaps it would be better to use news.
If the mailing-list server can cope with the load, I'd prefer to stick
to the present format.  Would any of the present readership be unable
to read this list as a newsgroup?

Finally, if this list is moved to news, where should it go?  (This
may have some bearing on it's accessibility to other users.)

Comments, anyone?

Dave

More... (looser matching)
- Last day of these posts
- In 1995 , 1996 only
- Today
- New search...