[Az-Geocaching] Boy, Did I Mess Up!

WOLFB8 listserv@azgeocaching.com
Sat, 25 Jan 2003 08:58:28 -0700


This is a multi-part message in MIME format.

------=_NextPart_000_004A_01C2C44F.EDB4BA20
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Steve correct me if I am wrong=20

When we (the geocacher ) meet with the land management last year were =
not asked to remove all caches from wilderness lands. From the sound of =
what is going on now we did not respond to there request and now our =
going to pay the price... There is no one to blame but our selves.=20

let look at state trust land ...I believe that every state trust cache =
owner has updated there page to reflect the need for a permit. Which is =
what state trust requested and then they told us about the one we were =
not sure of........ To the best of my knowledge there is no way in to =
the sups that does have signs (the signs are all over the place) that =
say wilderness area... So folks by our lack of action we may lose more =
land.. That bites but they have the power we do not

I suggest that every cache owner get permission for the caches they have =
out there and any future caches they may want to place. Make life easy =
if it on national park land , wilderness land or by a archaeological =
site don't ask and do not even think about putting a cache there....
We will be known by the tracks we leave behind
  ----- Original Message -----=20
  From: Team Tierra Buena=20
  To: listserv@azgeocaching.com=20
  Sent: Friday, January 24, 2003 11:14 AM
  Subject: [Az-Geocaching] Boy, Did I Mess Up!


  So I was rushing a little yesterday afternoon when I posted this
  message. And I didn't realize that the way I posted the message, that
  NOBODY was going to read what was underneath my little "introduction".
  Just after I hit "send" my computer crashed.

  So I finally get back on line Friday morning and find 30-odd messages
  about the Forest Service issue, but not a single one that indicates
  anyone saw what's below. Folks, PLEASE read the quotes below this all
  the way to the bottom.

  Thanks and apologies,

  Steve
  Team Tierra Buena
  "Making communication tougher than it needs to be."


  > -----Original Message-----
  > From: az-geocaching-admin@listserv.azgeocaching.com=20
  > [mailto:az-geocaching-admin@listserv.azgeocaching.com] On=20
  > Behalf Of Team Tierra Buena
  > Sent: Thursday, January 23, 2003 4:59 PM
  > To: listserv@azgeocaching.com
  > Subject: [Az-Geocaching] FW: Geocaching on FS Land
  >=20
  >=20
  > Let's hang on and see what other information we get. This, at=20
  > least, is encouraging.
  >=20
  > Steve
  > Team Tierra Buena
  >=20
  > > -----Original Message-----
  > > From: Scott Wood
  > > Sent: Thursday, January 23, 2003 4:51 PM
  > > To: Steve Gross
  > > Subject: Re: Geocaching on FS Land
  > >=20
  > >=20
  > >=20
  > > Steve,
  > > This is news to me. Last I heard, our Regional Director for=20
  > recreation=20
  > > came out in favor of geocaching and I have heard nothing from my=20
  > > Forest Supervisor to indicate that we were about to adopt such a=20
  > > policy. I'll see what I can find out.
  > >=20
  > > =
+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=
=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+
  > > J. Scott Wood
  > > Forest Archaeologist / Heritage Program Manager
  > > Tonto National Forest
  >=20
  > ____________________________________________________________
  > Az-Geocaching mailing list listserv@azgeocaching.com
  > To edit your setting, subscribe or unsubscribe visit:=20
  > http://listserv.azgeocaching.com/mailman/listinfo/az-geocachin
  g

  Arizona's Geocaching Resource
  http://www.azgeocaching.com

  ____________________________________________________________
  Az-Geocaching mailing list listserv@azgeocaching.com
  To edit your setting, subscribe or unsubscribe visit:
  http://listserv.azgeocaching.com/mailman/listinfo/az-geocaching

  Arizona's Geocaching Resource
  http://www.azgeocaching.com
------=_NextPart_000_004A_01C2C44F.EDB4BA20
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Steve correct me if I am wrong =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>When we (the geocacher ) meet with the =
land=20
management last year were not asked to remove all caches from wilderness =
lands.=20
>From the sound of what is going on now we did not respond to there =
request and=20
now our going to pay the price... There is no one to blame but our =
selves.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>let look at state trust land ...I =
believe that=20
every state trust cache owner has updated there page to reflect the need =
for a=20
permit. Which is what&nbsp;state trust&nbsp;requested and then =
they&nbsp;told us=20
about the one we were not&nbsp;sure of........ To the best of my =
knowledge there=20
is no way in to the sups that does have signs (the signs are all over =
the place)=20
that say wilderness area... So&nbsp;folks by our lack of action we may =
lose more=20
land.. That bites but they have the power we do not</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I suggest that every cache owner get =
permission for=20
the caches they have out there and any future caches they may want to =
place.=20
Make life easy if it on national park land , wilderness land or by a=20
archaeological site don't ask and do not even think about putting a =
cache=20
there....</FONT></DIV>
<DIV>We will be known by the tracks we leave behind</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dteamtierrabuena@earthlink.net=20
  href=3D"mailto:teamtierrabuena@earthlink.net">Team Tierra Buena</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dlistserv@azgeocaching.com=20
  =
href=3D"mailto:listserv@azgeocaching.com">listserv@azgeocaching.com</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, January 24, 2003 =
11:14=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Az-Geocaching] Boy, =
Did I Mess=20
  Up!</DIV>
  <DIV><BR></DIV>So I was rushing a little yesterday afternoon when I =
posted=20
  this<BR>message. And I didn't realize that the way I posted the =
message,=20
  that<BR>NOBODY was going to read what was underneath my little=20
  "introduction".<BR>Just after I hit "send" my computer =
crashed.<BR><BR>So I=20
  finally get back on line Friday morning and find 30-odd =
messages<BR>about the=20
  Forest Service issue, but not a single one that indicates<BR>anyone =
saw what's=20
  below. Folks, PLEASE read the quotes below this all<BR>the way to the=20
  bottom.<BR><BR>Thanks and apologies,<BR><BR>Steve<BR>Team Tierra=20
  Buena<BR>"Making communication tougher than it needs to =
be."<BR><BR><BR>&gt;=20
  -----Original Message-----<BR>&gt; From: <A=20
  =
href=3D"mailto:az-geocaching-admin@listserv.azgeocaching.com">az-geocachi=
ng-admin@listserv.azgeocaching.com</A>=20
  <BR>&gt; [mailto:az-geocaching-admin@listserv.azgeocaching.com] On =
<BR>&gt;=20
  Behalf Of Team Tierra Buena<BR>&gt; Sent: Thursday, January 23, 2003 =
4:59=20
  PM<BR>&gt; To: <A=20
  =
href=3D"mailto:listserv@azgeocaching.com">listserv@azgeocaching.com</A><B=
R>&gt;=20
  Subject: [Az-Geocaching] FW: Geocaching on FS Land<BR>&gt; <BR>&gt; =
<BR>&gt;=20
  Let's hang on and see what other information we get. This, at <BR>&gt; =
least,=20
  is encouraging.<BR>&gt; <BR>&gt; Steve<BR>&gt; Team Tierra =
Buena<BR>&gt;=20
  <BR>&gt; &gt; -----Original Message-----<BR>&gt; &gt; From: Scott =
Wood<BR>&gt;=20
  &gt; Sent: Thursday, January 23, 2003 4:51 PM<BR>&gt; &gt; To: Steve=20
  Gross<BR>&gt; &gt; Subject: Re: Geocaching on FS Land<BR>&gt; &gt; =
<BR>&gt;=20
  &gt; <BR>&gt; &gt; <BR>&gt; &gt; Steve,<BR>&gt; &gt; This is news to =
me. Last=20
  I heard, our Regional Director for <BR>&gt; recreation <BR>&gt; &gt; =
came out=20
  in favor of geocaching and I have heard nothing from my <BR>&gt; &gt; =
Forest=20
  Supervisor to indicate that we were about to adopt such a <BR>&gt; =
&gt;=20
  policy. I'll see what I can find out.<BR>&gt; &gt; <BR>&gt; &gt;=20
  =
+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=
=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+<BR>&gt; &gt; J. Scott=20
  Wood<BR>&gt; &gt; Forest Archaeologist / Heritage Program =
Manager<BR>&gt; &gt;=20
  Tonto National Forest<BR>&gt; <BR>&gt;=20
  ____________________________________________________________<BR>&gt;=20
  Az-Geocaching mailing list <A=20
  =
href=3D"mailto:listserv@azgeocaching.com">listserv@azgeocaching.com</A><B=
R>&gt;=20
  To edit your setting, subscribe or unsubscribe visit: <BR>&gt; <A=20
  =
href=3D"http://listserv.azgeocaching.com/mailman/listinfo/az-geocachin">h=
ttp://listserv.azgeocaching.com/mailman/listinfo/az-geocachin</A><BR>g<BR=
><BR>Arizona's=20
  Geocaching Resource<BR><A=20
  =
href=3D"http://www.azgeocaching.com">http://www.azgeocaching.com</A><BR><=
BR>____________________________________________________________<BR>Az-Geo=
caching=20
  mailing list <A=20
  =
href=3D"mailto:listserv@azgeocaching.com">listserv@azgeocaching.com</A><B=
R>To=20
  edit your setting, subscribe or unsubscribe visit:<BR><A=20
  =
href=3D"http://listserv.azgeocaching.com/mailman/listinfo/az-geocaching">=
http://listserv.azgeocaching.com/mailman/listinfo/az-geocaching</A><BR><B=
R>Arizona's=20
  Geocaching Resource<BR><A=20
  =
href=3D"http://www.azgeocaching.com">http://www.azgeocaching.com</A></BLO=
CKQUOTE></BODY></HTML>

------=_NextPart_000_004A_01C2C44F.EDB4BA20--