From: "Geo" 

This is a multi-part message in MIME format.

------=_NextPart_000_007B_01C525AE.982A66A0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

it only has to do with email as far as the network, it is not specific = to
email. It's really no different than using a vpn to do your email =
connections. You have still only secure one leg of a three leg =
transaction.

You have seen the type of people I mentioned? I live in a world FULL of =
then where they claim they have seen people like me..

Geo.
  "Rich"  wrote in message news:4230ed76{at}w3.nls.net...
     Sure it has to do with email.  We are discussing email.

     I have seen the type of people you mention.  I don't think it is =
that significant.  I have met people that don't know their own phone =
number and excuse this because they don't call themselves.  I would not =
be surprised to meet people that don't know their own email address or =
that of others.  They know how to receive email and how to send it.

  Rich

    "Geo"  wrote in message =
news:4230d8cc$1{at}w3.nls.net...
    the "security" you are claiming for email is protection against =
someone sniffing your traffic on the network, it really has nothing to = do
with email.

    As for the hard core computer user, I don't imagine you hear many =
people at MS talking on the phone saying "oh my email address, it's
www = dot ... at which point you know you're in trouble. I see that all the
= time, not just from people I work with but from customers and suppliers.
= You have to understand these people don't know the difference between a =
URL and an email address but they can tell the difference between an =
injection screw and an extrusion screw. It's a different world from = where
you work. They would rather have a paper desk calendar than a = computer
based one.

    Geo.
      "Rich"  wrote in message news:42307b9b{at}w3.nls.net...
         I don't understand why you are not sure.  Its the channel.  I =
disagree with the rest of your comments.

         Not everyone is a hard core computer user though all are =
obviously computer users.  You obviously have never seen this which may =
be why you don't understand.  It is clear to the recipient.  And BTW, if =
you use the global address book you never seen actual email addresses =
unless you want to.

      Rich

        "Geo"  wrote in message =
news:42302c85$1{at}w3.nls.net...
        "Rich"  wrote in message news:422fe6b0{at}w3.nls.net...
        >>an untrusted channel not a secure channel.  Think of it as =
similar to
        delivering a signed download over HTTP vs. any download (signed =
or not) over
        HTTPS.<<

        I'm not sure which you are claiming is secure but the signed =
example
        requires both client ends to use the same signing system and the =
https
        example is between you and your server but not the rest of the =
email
        transaction. In the first case email isn't secure because =
everyone isn't
        using the same signing system (it's not required) and in the =
second example
        it's wide open between your server and every other server on the =
planet so
        again it's not secure.

        >>To schedule I meeting

        In this example you assume everyone you are inviting to the =
meeting is a
        hard core computer user, a fair assumption if you work for a =
computer
        related company but not if you work for a plastics company where =
most
        employees barely grasp the concept that an email address has to =
have an {at} in
        it..

        Geo.


------=_NextPart_000_007B_01C525AE.982A66A0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








it only has to do with email as far as =
the network,=20
it is not specific to email. It's really no different than using a vpn = to do=20
your email connections. You have still only secure one leg of a three = leg=20
transaction.
 
You have seen the type of people I =
mentioned? I=20
live in a world FULL of then where they claim they have seen people like =

me..
 
Geo.

  "Rich" <{at}> wrote in message news:4230ed76{at}w3.nls.net...
     Sure it
has to do with =
email. =20
  We are discussing email.
   
     I have
seen the type of =
people you=20
  mention.  I don't think it is that significant.  I have met =
people=20
  that don't know their own phone number and excuse this because they =
don't call=20
  themselves.  I would not be surprised to meet people that don't =
know=20
  their own email address or that of others.  They know how to =
receive=20
  email and how to send it.
   
  Rich
   
  

    "Geo" <georger{at}nls.net>=20">mailto:georger{at}nls.net">georger{at}nls.net>=20
    wrote in message news:4230d8cc$1{at}w3.nls.net...
    the "security"
you are claiming for =
email is=20
    protection against someone sniffing your traffic on the network, it =
really=20
    has nothing to do with email.
     
    As for the hard core
computer user, =
I don't=20
    imagine you hear many people at MS talking on the phone saying "oh =
my email=20
    address, it's www dot ... at which point you know you're in trouble. =
I see=20
    that all the time, not just from people I work with but from =
customers and=20
    suppliers. You have to understand these people don't know the =
difference=20
    between a URL and an email address but they can tell the difference =
between=20
    an injection screw and an extrusion screw. It's a different world =
from where=20
    you work. They would rather have a paper desk calendar than a =
computer based=20
    one.
     
    Geo.
    

      "Rich" <{at}> wrote in message news:42307b9b{at}w3.nls.net...
         I
don't understand =
why you are=20
      not sure.  Its the channel.  I disagree with the rest of =
your=20
      comments.
       
         Not
everyone is a =
hard core=20
      computer user though all are obviously computer users.  You =
obviously=20
      have never seen this which may be why you don't understand.  =
It is=20
      clear to the recipient.  And BTW, if you use the global =
address book=20
      you never seen actual email addresses unless you want =
to.
       
      Rich
       
      
        "Geo" <georger{at}nls.net>=20">mailto:georger{at}nls.net">georger{at}nls.net>=20
        wrote in message news:42302c85$1{at}w3.nls.net..."Rich"=20
        <{at}> wrote in message news:422fe6b0{at}w3.nls.net...>=
>an=20
        untrusted channel not a secure channel.  Think of it as =
similar=20
        todelivering a signed download over HTTP vs. any download =
(signed or=20
        not) overHTTPS.<<I'm
not sure which you are =
claiming=20
        is secure but the signed examplerequires both client ends to =
use the=20
        same signing system and the httpsexample is between you and =
your=20
        server but not the rest of the emailtransaction. In the =
first case=20
        email isn't secure because everyone isn'tusing the same =
signing=20
        system (it's not required) and in the second exampleit's =
wide open=20
        between your server and every other server on the planet =
soagain=20
        it's not secure.>>To schedule I
meetingIn =
this=20
        example you assume everyone you are inviting to the meeting is =
ahard=20
        core computer user, a fair assumption if you work for a=20
        computerrelated company but not if you work for a plastics =
company=20
        where mostemployees barely grasp the concept that an email =
address=20
        has to have an {at}=20
  =
init..Geo.

------=_NextPart_000_007B_01C525AE.982A66A0--

--- BBBS/NT v4.01 Flag-5