<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Re: Blocking certain terrorism/porn sites and DNS</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Since when is Internet email reliable?<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: J. Oquendo [<A HREF="mailto:sil@politrix.org">mailto:sil@politrix.org</A>]<BR>
Sent: Thu Aug 18 14:38:31 2005<BR>
To: nanog@nanog.org<BR>
Cc: William Allen Simpson<BR>
Subject: Re: Blocking certain terrorism/porn sites and DNS<BR>
<BR>
<BR>
<BR>
On Thu, 18 Aug 2005, William Allen Simpson wrote:<BR>
<BR>
> Apparently, you did.... Of course, repeated posting here will vastly<BR>
> improve your opportunity to examine binaries handily delivered directly<BR>
> to your own email box. ;-)<BR>
<BR>
"handily delivered directly to your own email box." I take note of "your<BR>
own email box." So again I ask, how do you propose dealing with mail that<BR>
was "handily delivered" to your clients' email boxes. Or would you just be<BR>
assuming "if test -f LOOKS_LIKE_MY_EMAIL then filter_that".<BR>
<BR>
Either way you want to cut your comment it would take a bit of snooping to<BR>
parse out traffic not destined to your own email box(es). So what do you<BR>
tell your customer "Oh by the way we had to snoop in on your sessions to<BR>
stop some new and improved MS uberworm." If so, when do you do it,<BR>
when your network is crawling, after the fact... What if you're off by one<BR>
and accidentally filter out say a contract worth a lot. Again, if I'm<BR>
missing something by all means e-smack me.<BR>
<BR>
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+<BR>
J. Oquendo<BR>
GPG Key ID 0x97B43D89<BR>
<A HREF="http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x97B43D89">http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x97B43D89</A><BR>
<BR>
To conquer the enemy without resorting to war is the most<BR>
desirable. The highest form of generalship is to conquer<BR>
the enemy by strategy." - Sun Tzu<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>