18 lines
2.9 KiB
HTML
18 lines
2.9 KiB
HTML
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
|
||
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>spamblock</title><link rel="stylesheet" href="../../jargon.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.61.0"/><link rel="home" href="../index.html" title="The Jargon File"/><link rel="up" href="../S.html" title="S"/><link rel="previous" href="spam-bait.html" title="spam bait"/><link rel="next" href="spamhaus.html" title="spamhaus"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">spamblock</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="spam-bait.html">Prev</a> </td><th width="60%" align="center">S</th><td width="20%" align="right"> <a accesskey="n" href="spamhaus.html">Next</a></td></tr></table><hr/></div><dt><a id="spamblock"/><dt xmlns="" id="spamblock"><b>spamblock</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="pronunciation">/spam´blok/</span>, <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p> [poss. by analogy to sunblock] Text inserted in an email address to
|
||
render it invalid and thus useless to spammers. For example, the address
|
||
<tt class="email"><<a href="mailto:jrandom@hacker.org">jrandom@hacker.org</a>></tt> might be transformed to
|
||
<tt class="email"><<a href="mailto:jrandom@NOSPAM.hacker.org">jrandom@NOSPAM.hacker.org</a>></tt>. Adding spamblock to an address
|
||
is often referred to as <span class="firstterm">munging</span> it
|
||
(see <a href="../M/munge.html"><i class="glossterm">munge</i></a>). This evasion tactic depends on the
|
||
fact that most spammers collect names with some sort of <a href="../A/address-harvester.html"><i class="glossterm">address
|
||
harvester</i></a> on volumes too high to de-mung by hand, but
|
||
individual humans reading an email message can readily spot and remove a
|
||
spamblock in the From address.</p><p>Note: This is not actually a very effective tactic, and may already
|
||
be passing out of use in early 1999 after about two years of life. In both
|
||
mail and news, it's essentially impossible to keep a smart address
|
||
harvester from mining out the addresses in the message header and trace
|
||
lines. Therefore the only people who can be protected are third parties
|
||
mentioned by email address in the message — not a common enough case
|
||
to interest spammers.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="spam-bait.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../S.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="spamhaus.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">spam bait </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> spamhaus</td></tr></table></div></body></html>
|