[no subject]

Actually, a good chunk of spam would be blocked, given the 100+ filters
I've had to add for my *incoming* mail.  'course, I'd give the hackers two
weeks before their next virus payload combined the current SMTP client
capability with a POP3 or IMAP password sniffer so as to reroute the
traffic to the ISP's designated outbound relay.  Then we're looking at
greater enforcement of encrypted-password-type solutions instead of the
cleartext password transmissions incumbent in the legacy mail retrieval
protocols that are still being used today.


</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="00597" href="msg00597.html">[ale] (no subject)</a></strong>
<ul><li><em>From:</em> jasonday at worldnet.att.net (Jason Day)</li></ul></li>
<li><strong><a name="00599" href="msg00599.html">[ale] (no subject)</a></strong>
<ul><li><em>From:</em> jdr at xcorps.net (Jonathan Rickman)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00601.html">[ale] Woof</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00603.html">[ale] squidGuard</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00599.html">[ale] (no subject)</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00607.html">[ale] (no subject)</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00602"><strong>Date</strong></a></li>
<li><a href="threads.html#00602"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

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