[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Wed, 28 Dec 2005 13:50:41 -0500 -->
- <!--x-from-r13: wfurrgf ng lnubb.pbz (Xrenyq Eurrgf) -->
- <!--x-message-id: 2D043118-CB95-4126-BBC2-[email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: D44049C9-EB47-4D27-9E18-[email protected] -->
- <!--x-reference: 20051228131827.5099b470@aud --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] Speedfactory now requires mail contents to be readable -->
- <li><em>date</em>: Wed, 28 Dec 2005 13:50:41 -0500</li>
- <li><em>from</em>: jsheets at yahoo.com (Jerald Sheets)</li>
- <li><em>in-reply-to</em>: <20051228131827.5099b470@aud></li>
- <li><em>references</em>: <<a href="msg00358.html">[email protected]</a>> <<a href="msg00360.html">[email protected]</a>> <20051228131827.5099b470@aud></li>
- <li><em>subject</em>: [ale] Speedfactory now requires mail contents to be readable</li>
Unfortunately, liability meets that of being declared a "publisher"
and culpable for what your users say as well as being a good
policeman on your network and being responsible also for what your
users do.
I would offer that the liabilities are such that they are taking
steps to control what they *can* control by any means they have
available to them.
Jerald M. Sheets jr.
Sr. UNIX Systems Administrator
The Weather Channel Interactive
404.293.8762
On Dec 28, 2005, at 1:18 PM, Robert Story wrote:
> On Wed, 28 Dec 2005 11:06:27 -0500 Jerald wrote:
> JS> It is in Speedfactory's best interest to do
> JS> this type of automated scanning, so as to escape culpability in
> the
> JS> spread of viruses and trojans, as well as staying off various
> JS> blacklists hither and yon.
>
> I don't know about that. Once they start inspecting content,
> doesn't that make
> them *more* culpable? What's next, rejecting mail with dirty words
> that might
> offend someone? Or PGP encrypted messages? If I were a
> speedfactory customer,
> I'd be screaming bloody murder, and checking my terms of service.
>
> It's one thing for a company to have a policy to reject or quarantine
> reception of encrypted zip files, but another thing entirely for an
> ISP to
> block sending them.
>
> All this will do is teach people to rename the file to '.txt', with
> instructions to rename the file back to '.zip' to get to it. Once
> this becomes
> the SOP, it won't be long before the virii employ the same methods
> to lure the
> clueless into their trap.
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00358" href="msg00358.html">[ale] Speedfactory now requires mail contents to be readable</a></strong>
<ul><li><em>From:</em> runman at speedfactory.net (runman)</li></ul></li>
<li><strong><a name="00360" href="msg00360.html">[ale] Speedfactory now requires mail contents to be readable</a></strong>
<ul><li><em>From:</em> jsheets at yahoo.com (Jerald Sheets)</li></ul></li>
<li><strong><a name="00366" href="msg00366.html">[ale] Speedfactory now requires mail contents to be readable</a></strong>
<ul><li><em>From:</em> rstory-l at revelstone.com (Robert Story)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00368.html">[ale] Speedfactory now requires mail contents to be readable</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00370.html">[ale] Speedfactory now requires mail contents to be readable</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00366.html">[ale] Speedfactory now requires mail contents to be readable</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00381.html">[ale] Speedfactory now requires mail contents to be readable</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00369"><strong>Date</strong></a></li>
<li><a href="threads.html#00369"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>