[no subject]

*********** REPLY SEPARATOR  ***********
On 9/1/2004 at 1:45 PM Jason Day wrote:

>On Wed, Sep 01, 2004 at 01:56:45AM -0400, Robert Reese wrote:
>> I
>> *will* not have have Google or anyone else peruse through any email I
>send
>> to a gmail user, and certainly am not interested in having Google sniff
>any
>> email sent to me from a gmail account.  ;c)
>
>As opposed to the various virus scanners and spam filters that sniff any
>email you send?

None of them scan them for the purpose of analyzing content for the purpose
of individualized statistics.  Neither of them accrue usage data on a
per-user basis.


>  Or the unscrupulous sysadmin at any of the servers your
>email happens to pass through, who reads random email messages for the
>fun of it?

First, I've never sent anything plain-text that would embarrass me. 
Second, I'll encrypt it if I don't care for spying sysops.  Third, a wild
sysop doesn't have the capabilities to catalog and analyze all of my
messages.  In other words, apples and torque wrenches.


>  Unless you use encryption, there is nothing secure or
>private about email, no matter which provider you use.

You are 100% correct with that statement.


>>In addition, there is a technical limitation to your gmail filter: there 
>is nothing that prevents any of your email recipients from forwarding
>their email to a gmail account.  The *only* way to keep Google, or
>anybody, from sniffing your email is to use encryption.

The same technical limitation exists for your exception: a recipient can
decrypt and forward, still.  However, that is a third-party transaction,
not a first-person transaction.  With a GMail account, then 100% of
unencrypted messages get scanned and analyzed.

By the way, you might find a couple of links from another related post
interesting:

<a  rel="nofollow" href="http://www.epic.org/privacy/gmail/faq.html";>http://www.epic.org/privacy/gmail/faq.html</a>
<a  rel="nofollow" href="http://gmail-is-too-creepy.com/";>http://gmail-is-too-creepy.com/</a>

Thanks to Christopher Russell for the links. ;c)


Cheers,
Robert Reese~

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
Comment: No one has the right to NOT be offended!

iQA/AwUBQTZgKbw8BOWncaQMEQJGjQCg6dydWeNPwNpfI3H7UHtgL5rwqacAmwbC
hvxlob8gcBhgor30lnOvYynW
=jdNR
-----END PGP SIGNATURE-----


Type: DH/DSS 4096/1024 AES-256
Key ID: 0xA771A40C
Fingerprint: CAE2 81CA A7CD 6681 341C  E3A9 BC3C 04E5 A771 A40C



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00040" href="msg00040.html">[ale] What's so special about gmail invites?</a></strong>
<ul><li><em>From:</em> hbbs at comcast.net (Jeff Hubbs)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00000" href="msg00000.html">[ale] What's so special about gmail invites?</a></strong>
<ul><li><em>From:</em> ale at sixit.com (Robert Reese)</li></ul></li>
<li><strong><a name="00030" href="msg00030.html">[ale] What's so special about gmail invites?</a></strong>
<ul><li><em>From:</em> jasonday at worldnet.att.net (Jason Day)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00037.html">[ale] Specify permissions, owner, and group of newly created files</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00039.html">[ale] Keepass for Linux?</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00030.html">[ale] What's so special about gmail invites?</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00040.html">[ale] What's so special about gmail invites?</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00038"><strong>Date</strong></a></li>
<li><a href="threads.html#00038"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>