<html>
<head>
</head>
<body>
On 04/19/02 11:39 AM, Tony Langdon wrote:<br>
<blockquote type="cite" cite="mid:B17EB7B34580D311BE38525405DF6232C37354@atc-mail-db.atctraining.com.au">
<blockquote type="cite">
<pre wrap="">so the only defense is to carefully check the origin and request the<br>sysadmin of the offending account do something about it (although this<br>is pretty useless because odds on the account source will be bogus.)<br><br>ignore it and it won't get worse.<br></pre>
</blockquote>
<pre wrap=""><!----><br>You may want to sign up to Spamcop (<a class="moz-txt-link-freetext" href="http://spamcop.net">http://spamcop.net</a>). Once signed up (a<br>basic reporting account is free), you can feed the spam in and have spamcop<br>report the abuse, or if you prefer, use the information from its analysis to<br>report the spam yourself.</pre>
</blockquote>
yes I saw this too. However, I was under the impression that it was a service
provider solution....<br>
<br>
anyway, as of this moment, we are not too heavily inundated with spam at
work (in many ways this is an RMIT wide problem too) <br>
on the home front, it is frustrating (at least from a frustration of service
point of view) but at this point I am able to put up with it...<br>
<br>
When private email lists get onto spam lists, then something has to be done
about it because the problem quickly escalates, particularly when one member
of the list confirms that the email address is valid and the address gets
passed around into multiple lists.<br>
<br>
<pre class="moz-signature" cols="$mailwrapcol">--
Dr Paul van den Bergen
SERC
goofey:bulwynkl
<a class="moz-txt-link-abbreviated" href="mailto:paul@serc.rmit.edu.au">paul@serc.rmit.edu.au</a>
+613 9925 1624 (RMIT)
+613 9905 4654 (Monash-less often)
</pre>
<br>
</body>
</html>