<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: A Plan To Reduce Spam</title>
	<atom:link href="http://iampariah.com/projects/other-projects/the-plan-to-reduce-spam.php/feed" rel="self" type="application/rss+xml" />
	<link>http://iampariah.com/projects/other-projects/the-plan-to-reduce-spam.php</link>
	<description>Consulting &#38; Training with Creative &#38; Publishing Workflow Expert Pariah S. Burke &#124; Informing &#38; Empowering Creative Professionals™</description>
	<lastBuildDate>Wed, 24 Aug 2011 17:54:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: George Orwell</title>
		<link>http://iampariah.com/projects/other-projects/the-plan-to-reduce-spam.php/comment-page-1#comment-407</link>
		<dc:creator>George Orwell</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=201#comment-407</guid>
		<description>[ FYI, &#039;employ&#039; is spelled with an &#039;o&#039;. ]

Your plan is naive. Obviously you haven&#039;t done due diligence before posting it to your blog by first asking for discussion in:

news:news.admin.net-abuse.email

Firstly, the registered contact for a web site is not who *sold* your name.

Second, email to the registered contact addresses to my sites are already 99% spam themselves, thus easy to clear out.

Third, even if you stuff the mailbox, all that will happen is further complaints will bounce, and it is still the valid [required] contact address.

Should they need to use their contact address, they can simply clear out  the mailbox first.

Fourth, you haven&#039;t said anything about an URL to a site on an ISP, such as AOL. Oops, won&#039;t help there.

It is  good you are using Javascript to construct mail URLs at runtime. Most harvesters don&#039;t run a rendering engine. But they could if the practice of using Javascript became widespread.</description>
		<content:encoded><![CDATA[<p>[ FYI, ‘employ’ is spelled with an ‘o’. ]</p>
<p>Your plan is naive. Obviously you haven’t done due diligence before posting it to your blog by first asking for discussion in:</p>
<p>news:news.admin.net-abuse.email</p>
<p>Firstly, the registered contact for a web site is not who *sold* your name.</p>
<p>Second, email to the registered contact addresses to my sites are already 99% spam themselves, thus easy to clear out.</p>
<p>Third, even if you stuff the mailbox, all that will happen is further complaints will bounce, and it is still the valid [required] contact address.</p>
<p>Should they need to use their contact address, they can simply clear out  the mailbox first.</p>
<p>Fourth, you haven’t said anything about an URL to a site on an ISP, such as AOL. Oops, won’t help there.</p>
<p>It is  good you are using Javascript to construct mail URLs at runtime. Most harvesters don’t run a rendering engine. But they could if the practice of using Javascript became widespread.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Orwell</title>
		<link>http://iampariah.com/projects/other-projects/the-plan-to-reduce-spam.php/comment-page-1#comment-408</link>
		<dc:creator>George Orwell</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=201#comment-408</guid>
		<description>Great, I gotta reply to myself...

I read a little closer about what you meant when you said the web site sold your name. Okay, they sold your name. Ticketmaster, BTW, is guaranteed to do that:

http://politechbot.com/p-05001.html

Unfortunately, the vast majority of people are not going to be able to configure their mail server, or even have their own mail server, to do what you suggest.

What I do is slightly different: I instantiate (using my ISPs webform for my domain) a new name for purchases, such as paypal-dot-com@. Should I get spam, which hasn&#039;t happened yet from a purchase, I would simply delete the forward to my real mailbox.

Not that regular lusers would be able to handle that either.

If you did make a purchase via a webform on say an AOL site, and it didn&#039;t have a privacy policy stating they wouldn&#039;t sell your name, complaining to AOL won&#039;t get you far.

A webbug is another way of getting on a spam list. You get an email, sometimes they just generate lots of names and try them. Should you make the mistake of reading your email with image loading turned on, congratulations: you&#039;ve just confirmed your address as valid. All the spammer need do is work a unique number into any image URL that they can then match up with your email address.

Your subscription process doesn&#039;t involve a confirmation. I take it you&#039;ve never been listbombed. That&#039;s when someone subscribes you to dozens and dozens of lists that don&#039;t have the now-usual confirmation step of a reply before adding the email address to the list. Take the time to do that with your list. Freeware called ezmlm will automatically handle this for you.</description>
		<content:encoded><![CDATA[<p>Great, I gotta reply to myself…</p>
<p>I read a little closer about what you meant when you said the web site sold your name. Okay, they sold your name. Ticketmaster, BTW, is guaranteed to do that:</p>
<p><a href="http://politechbot.com/p-05001.html" rel="nofollow">http://politechbot.com/p-05001.html</a></p>
<p>Unfortunately, the vast majority of people are not going to be able to configure their mail server, or even have their own mail server, to do what you suggest.</p>
<p>What I do is slightly different: I instantiate (using my ISPs webform for my domain) a new name for purchases, such as paypal-dot-com@. Should I get spam, which hasn’t happened yet from a purchase, I would simply delete the forward to my real mailbox.</p>
<p>Not that regular lusers would be able to handle that either.</p>
<p>If you did make a purchase via a webform on say an AOL site, and it didn’t have a privacy policy stating they wouldn’t sell your name, complaining to AOL won’t get you far.</p>
<p>A webbug is another way of getting on a spam list. You get an email, sometimes they just generate lots of names and try them. Should you make the mistake of reading your email with image loading turned on, congratulations: you’ve just confirmed your address as valid. All the spammer need do is work a unique number into any image URL that they can then match up with your email address.</p>
<p>Your subscription process doesn’t involve a confirmation. I take it you’ve never been listbombed. That’s when someone subscribes you to dozens and dozens of lists that don’t have the now-usual confirmation step of a reply before adding the email address to the list. Take the time to do that with your list. Freeware called ezmlm will automatically handle this for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pariah Burke</title>
		<link>http://iampariah.com/projects/other-projects/the-plan-to-reduce-spam.php/comment-page-1#comment-409</link>
		<dc:creator>Pariah Burke</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=201#comment-409</guid>
		<description>Thanks for the well thought out feedback, George.

I think something basic may have gotten lost in the translation of my plan. I do not propose a plan to &lt;i&gt;eliminate&lt;/i&gt; spam, merely one to &lt;i&gt;reduce&lt;/i&gt; it.

You&#039;re right, the vast majority of the Internet users out here neither possess the needed technology to take advantage of the plan (beyond the safety steps I&#039;ve given regarding protecting their own e-mail addresses, sending mail to lists via BCC, etc), nor are they technologically savvy enough to make use of mail forwarders on a configurable mail server if they had access to one. I&#039;m not saying that everyone can or even should follow my plan of keying addresses and sending back to the originating site any spam received to those addresses. My plan is geared toward people like you and me that &lt;i&gt;do &lt;/i&gt;have access to that technology and the skill to use it. There are quite a few of us out here who fit that profile.

It may be a bit naive, but think about it:  Retaliation against the spam senders has been proven time and again as ineffectual and a waste of one&#039;s time. Attacking the advertisers who use spam as a means of promotion is only slightly more effective since the majority of them are small, home-based businesses running Pyramid or Ponzi scams, not larger companies who have a vested interest in promoting a good brand image.

Equally useless is any plan to go after the ISPs and service providers who enable spam because, by and large, professional spammers maintain their own servers or use disposable accounts.

So, we&#039;ve eliminated three of the five entities in the spam process. The fourth is, of course, the recipient. The fifth is the company or individual who collects the e-mail addresses.

As you noted, I use Javascript to reduce (again, not eliminate) the instances of a listable hit upon my site. I also employ [it was a typo earlier, thank you] other systems through the blog and other places to protect the addresses of my visitors.

What I am talking about is those sites that require us to provide an e-mail address before granting us access to something we desire. Maybe it&#039;s a small software publisher&#039;s site who sends an activation key to one via e-mail after purchase. Maybe it&#039;s a members-only news site like ConsumerReports.com or TheNYTimes.com. It could be anything. More and more lately, even for free content, registration is the norm. It helps sites show a provable user base for promotion, setting advertising rates, securing financing, arranging partnerships, and so on. I fully support registration... As long as the registrant&#039;s information is kept confidential.

When it isn&#039;t, the company with whom one has registered becomes the fifth entity in the spam chain:  The pimp, if you will.

If enough of us with the ability and resources sent our spam back to the pimp who sold us out to it, that pimp will have to re-evaluate his profit versus aggravation ratio. Eventually he will ask himself:  Is it worth it to make a few hundred bucks here and there when I have to keep filtering out several hundred copies of each of several hundred spam messages just to read my e-mail? How often is it worth it to me change e-mail addresses just to keep selling lists?

You stated:
&lt;div class=&quot;blogquote&quot;&gt;&#8220;Third, even if you stuff the mailbox, all that will happen is further complaints will bounce, and it is still the valid [required] contact address.&lt;/div&gt;

&lt;div class=&quot;blogquote&quot;&gt;&#8220;Should they need to use their contact address, they can simply clear out the mailbox first.&#8221;&lt;/div&gt;

Sure, they can clear out their boxes. But, just like the rest of us, if that box &lt;i&gt;may&lt;/i&gt; contain any desired mail, they&#039;ll need to sift through it. Automated filters, as I&#039;m sure you&#039;ve learned first hand, have a limited lifespan. Spammers are constantly devising new tricks to defeat our filters (my favorite is inserting random characters between letters of a common keyword, and those characters being set by HTML or CSS to not show in the rendered page). So, the pimps then have to sift through their mail, just like the rest of us--thus the frustration factor transferred from us, the intended recipient, to them, the instrument of our would-be frustration.

Further, those addresses that are required domain contacts are typically used for something important:  Communication with the registrar. Many people aren&#039;t savvy enough to mark on their calendars when a domain is up for renewal, so, lest the domain go down, the site owner will want a means of receiving reminders if nothing else.

&lt;div class=&quot;blogquote&quot;&gt;&#8220;What I do is slightly different: I instantiate (using my ISPs webform for my domain) a new name for purchases, such as paypal-dot-com@. Should I get spam, which hasn’t happened yet from a purchase, I would simply delete the forward to my real mailbox.&#8221;&lt;/div&gt;

Why delete the forward? What I suggest is, instead of deleting the forwarding address, &lt;i&gt;redirect it to the individual or company responsible for the spam&lt;/i&gt;. By deleting the forwarder you&#039;re acting defensively, which is what we all have been doing for years. We act in defense of our inboxes, inviting the spam industry to continue on the offensive, the easier side, working to defeat our defenses without ever taking the defense themselves.

I want to change that. The best defense is a good offense. Turn your forwarder back on the source. Make them defend against their own defense-defeating mail. As you know, it&#039;s a simple matter to do. Once you&#039;ve done a whois on the domain, drop a contact&#039;s e-mail address into your forwarder, and be done with it. Such a small effort, done by a few hundred of us who can do that, would make a big effort. It would put those who would victimize us into the position of being the victims of their own actions.

There is nothing exploitative about sending spam back to these people. Mail bombing them is bad, but by sending back spam they caused to be sent, they are reaping only their own seeds. Should they somehow cause the sold address to no longer receive spam, they will no longer receive spam from it. However, should the sold address generate a dozen unsolicited messages per day as a result of the pimp&#039;s actions, then the pimp will receive that mail. The pimp receives only what s/he causes to be sent. Nothing more, nothing less.

&lt;div class=&quot;blogquote&quot;&gt;&#8220;If you did make a purchase via a webform on say an AOL site, and it didn’t have a privacy policy stating they wouldn’t sell your name, complaining to AOL won’t get you far.&#8221;&lt;/div&gt;

Right. A large company like that and you&#039;re out of luck, with this plan, anyway. That doesn&#039;t mean you shouldn&#039;t fight the not-so-giant companies.

I was unaware of the workings of a webbug, though I had a pretty good idea that something of that sort was going on. Thanks for informing me.

Listbombed, yes, I have, too many times. Same thing:  Spam the mail back to the site on which one has used the keyed address being listbombed.

Actually, I use NotifyList.com for my Saturday Slant list. For the subscriptions to this blog, I&#039;ll look into ezmlm. Thanks.

Again, thanks for responding. I really hope you and the 823 unique visitors this page has logged since I put it up will join me in this plan to send the frustration of spam back to some of the sources.</description>
		<content:encoded><![CDATA[<p>Thanks for the well thought out feedback, George.</p>
<p>I think something basic may have gotten lost in the translation of my plan. I do not propose a plan to <i>eliminate</i> spam, merely one to <i>reduce</i> it.</p>
<p>You’re right, the vast majority of the Internet users out here neither possess the needed technology to take advantage of the plan (beyond the safety steps I’ve given regarding protecting their own e-mail addresses, sending mail to lists via BCC, etc), nor are they technologically savvy enough to make use of mail forwarders on a configurable mail server if they had access to one. I’m not saying that everyone can or even should follow my plan of keying addresses and sending back to the originating site any spam received to those addresses. My plan is geared toward people like you and me that <i>do </i>have access to that technology and the skill to use it. There are quite a few of us out here who fit that profile.</p>
<p>It may be a bit naive, but think about it:  Retaliation against the spam senders has been proven time and again as ineffectual and a waste of one’s time. Attacking the advertisers who use spam as a means of promotion is only slightly more effective since the majority of them are small, home-based businesses running Pyramid or Ponzi scams, not larger companies who have a vested interest in promoting a good brand image.</p>
<p>Equally useless is any plan to go after the ISPs and service providers who enable spam because, by and large, professional spammers maintain their own servers or use disposable accounts.</p>
<p>So, we’ve eliminated three of the five entities in the spam process. The fourth is, of course, the recipient. The fifth is the company or individual who collects the e-mail addresses.</p>
<p>As you noted, I use Javascript to reduce (again, not eliminate) the instances of a listable hit upon my site. I also employ [it was a typo earlier, thank you] other systems through the blog and other places to protect the addresses of my visitors.</p>
<p>What I am talking about is those sites that require us to provide an e-mail address before granting us access to something we desire. Maybe it’s a small software publisher’s site who sends an activation key to one via e-mail after purchase. Maybe it’s a members-only news site like ConsumerReports.com or TheNYTimes.com. It could be anything. More and more lately, even for free content, registration is the norm. It helps sites show a provable user base for promotion, setting advertising rates, securing financing, arranging partnerships, and so on. I fully support registration… As long as the registrant’s information is kept confidential.</p>
<p>When it isn’t, the company with whom one has registered becomes the fifth entity in the spam chain:  The pimp, if you will.</p>
<p>If enough of us with the ability and resources sent our spam back to the pimp who sold us out to it, that pimp will have to re-evaluate his profit versus aggravation ratio. Eventually he will ask himself:  Is it worth it to make a few hundred bucks here and there when I have to keep filtering out several hundred copies of each of several hundred spam messages just to read my e-mail? How often is it worth it to me change e-mail addresses just to keep selling lists?</p>
<p>You stated:</p>
<div class="blogquote">“Third, even if you stuff the mailbox, all that will happen is further complaints will bounce, and it is still the valid [required] contact address.</div>
<div class="blogquote">“Should they need to use their contact address, they can simply clear out the mailbox first.”</div>
<p>Sure, they can clear out their boxes. But, just like the rest of us, if that box <i>may</i> contain any desired mail, they’ll need to sift through it. Automated filters, as I’m sure you’ve learned first hand, have a limited lifespan. Spammers are constantly devising new tricks to defeat our filters (my favorite is inserting random characters between letters of a common keyword, and those characters being set by HTML or CSS to not show in the rendered page). So, the pimps then have to sift through their mail, just like the rest of us–thus the frustration factor transferred from us, the intended recipient, to them, the instrument of our would-be frustration.</p>
<p>Further, those addresses that are required domain contacts are typically used for something important:  Communication with the registrar. Many people aren’t savvy enough to mark on their calendars when a domain is up for renewal, so, lest the domain go down, the site owner will want a means of receiving reminders if nothing else.</p>
<div class="blogquote">“What I do is slightly different: I instantiate (using my ISPs webform for my domain) a new name for purchases, such as paypal-dot-com@. Should I get spam, which hasn’t happened yet from a purchase, I would simply delete the forward to my real mailbox.”</div>
<p>Why delete the forward? What I suggest is, instead of deleting the forwarding address, <i>redirect it to the individual or company responsible for the spam</i>. By deleting the forwarder you’re acting defensively, which is what we all have been doing for years. We act in defense of our inboxes, inviting the spam industry to continue on the offensive, the easier side, working to defeat our defenses without ever taking the defense themselves.</p>
<p>I want to change that. The best defense is a good offense. Turn your forwarder back on the source. Make them defend against their own defense-defeating mail. As you know, it’s a simple matter to do. Once you’ve done a whois on the domain, drop a contact’s e-mail address into your forwarder, and be done with it. Such a small effort, done by a few hundred of us who can do that, would make a big effort. It would put those who would victimize us into the position of being the victims of their own actions.</p>
<p>There is nothing exploitative about sending spam back to these people. Mail bombing them is bad, but by sending back spam they caused to be sent, they are reaping only their own seeds. Should they somehow cause the sold address to no longer receive spam, they will no longer receive spam from it. However, should the sold address generate a dozen unsolicited messages per day as a result of the pimp’s actions, then the pimp will receive that mail. The pimp receives only what s/he causes to be sent. Nothing more, nothing less.</p>
<div class="blogquote">“If you did make a purchase via a webform on say an AOL site, and it didn’t have a privacy policy stating they wouldn’t sell your name, complaining to AOL won’t get you far.”</div>
<p>Right. A large company like that and you’re out of luck, with this plan, anyway. That doesn’t mean you shouldn’t fight the not-so-giant companies.</p>
<p>I was unaware of the workings of a webbug, though I had a pretty good idea that something of that sort was going on. Thanks for informing me.</p>
<p>Listbombed, yes, I have, too many times. Same thing:  Spam the mail back to the site on which one has used the keyed address being listbombed.</p>
<p>Actually, I use NotifyList.com for my Saturday Slant list. For the subscriptions to this blog, I’ll look into ezmlm. Thanks.</p>
<p>Again, thanks for responding. I really hope you and the 823 unique visitors this page has logged since I put it up will join me in this plan to send the frustration of spam back to some of the sources.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Orwell</title>
		<link>http://iampariah.com/projects/other-projects/the-plan-to-reduce-spam.php/comment-page-1#comment-410</link>
		<dc:creator>George Orwell</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=201#comment-410</guid>
		<description>I hope I am not monopolizing replies, and thanks for not getting upset at my brisk attitude. I&#039;m used to rougher forums, i.e. Usenet.

I have seen almost no spam from registrations. They all seem to have an opt-out (or even better: opt-in) checkboxes. How much spam and from where are you getting hit??? Inquiring minds wanna know.

Anyone using Ticketmaster had better be ready to revoke the email address once the transaction is complete.

I&#039;m already using unique addresses that I can revoke when I order stuff.

Where do I get spammed from? My
InterNIC registrations, mailing lists,
and Usenet.

I don&#039;t see any global way of eliminating or even noticeably reducing spam without going to an everyone-gets-registered-to-access the Internet scheme, which of course would be horrible. They&#039;ve got that in China.

What might I try locally?

For mailing lists, a unique address which I&#039;ll change if I start getting spam. Unsubscribe, resubscribe.

For Usenet, I&#039;ve found you can put an URL within the comment field where your name goes. I&#039;ll make a web page with a form on it to send me email, protecting the email address either by turning off read permissions and leaving execute permissions, else turning off all non-owner permissions and using cgiwrap.

The address portion will be needed to do a signup with a Usenet service,
but thereafter I can just forward it to
cypher@punk.net, which is a /dev/null sinkhole everyone has permission to use. Also, there are addresses at www.privacy.net/email that can be used for a &quot;go away&quot; autoreply.

Anyone who would want to reply to me would be able to figure out to pull up the URL and enter the message in the webform.

Should it catch on (someone offer it as a service), then spammers would write client-side http scripts, but one could add random letter pictures that must be hand entered, as hotmail.com now uses to prevent automated registrations.

Same thing for web site registrations (InterNIC): use a form. It might require using a real address, then editing it to the http form address. It might need changing the colon and slashes to something obvious like dashes to pass syntax checks.

httpColonSlashSlashPath.com

If necessary, use the trick described for Usenet to put the whole URL in the name/comment portion of the address within double quotes.

&quot;first last http://blah.com&quot; 

You might need to get a reply there, at least initially. Maybe only allow emails from your registrar and the
ISP that hosts your site, forwarding
the rest into the bit bucket.

The good thing is you can always decide to forward it back to your real email address for a while, in case, say, you need to complain about being forged. You can&#039;t complain if you don&#039;t own the visible email address and can receive email there.

Another option for site registration is to use the $50/year ones at Tonga, which is really in a consulate in the US somewhere.

http://homepage.to/dnsrgstr.htm

#  Unlike any other registrar, nobody can query your domain name and find out who owns that name, what servers or hosting provider you are using in what country or any other information about your domain name registration. They will only tell people whether or not a specific domain name has been registered.

----

I think I read somewhere that you are in Portland, OR. Condolences. ;-)

Also, that you have Mac OS X.

I got that OS upgrade from 9 several weeks ago, and I am planning on moving all my operations onto it. It&#039;s fabulous.

Have you tried training its junkmail spotter? Some sort of heuristics are involved. Take your main mail address, send it to two real POP boxes, read one using Mail under Mac OS X and see how intelligent it becomes. In training mode you can click to change the status from not-junk to Junk and the udder way.

I&#039;m splitting (forwarding) my email into three pop boxes for now. One for my regular machine, one for the iMac, and one for reading it while at work.

OS X Mail has a full filtering capability under Preferences-&gt;Rules.</description>
		<content:encoded><![CDATA[<p>I hope I am not monopolizing replies, and thanks for not getting upset at my brisk attitude. I’m used to rougher forums, i.e. Usenet.</p>
<p>I have seen almost no spam from registrations. They all seem to have an opt-out (or even better: opt-in) checkboxes. How much spam and from where are you getting hit??? Inquiring minds wanna know.</p>
<p>Anyone using Ticketmaster had better be ready to revoke the email address once the transaction is complete.</p>
<p>I’m already using unique addresses that I can revoke when I order stuff.</p>
<p>Where do I get spammed from? My<br />
InterNIC registrations, mailing lists,<br />
and Usenet.</p>
<p>I don’t see any global way of eliminating or even noticeably reducing spam without going to an everyone-gets-registered-to-access the Internet scheme, which of course would be horrible. They’ve got that in China.</p>
<p>What might I try locally?</p>
<p>For mailing lists, a unique address which I’ll change if I start getting spam. Unsubscribe, resubscribe.</p>
<p>For Usenet, I’ve found you can put an URL within the comment field where your name goes. I’ll make a web page with a form on it to send me email, protecting the email address either by turning off read permissions and leaving execute permissions, else turning off all non-owner permissions and using cgiwrap.</p>
<p>The address portion will be needed to do a signup with a Usenet service,<br />
but thereafter I can just forward it to<br />
<a href="javascript:degrease('hDumjwauzspbsjy',5)">cypher@punk.net</a>, which is a /dev/null sinkhole everyone has permission to use. Also, there are addresses at <a href="http://www.privacy.net/email" rel="nofollow">http://www.privacy.net/email</a> that can be used for a “go away” autoreply.</p>
<p>Anyone who would want to reply to me would be able to figure out to pull up the URL and enter the message in the webform.</p>
<p>Should it catch on (someone offer it as a service), then spammers would write client-side http scripts, but one could add random letter pictures that must be hand entered, as hotmail.com now uses to prevent automated registrations.</p>
<p>Same thing for web site registrations (InterNIC): use a form. It might require using a real address, then editing it to the http form address. It might need changing the colon and slashes to something obvious like dashes to pass syntax checks.</p>
<p>httpColonSlashSlashPath.com</p>
<p>If necessary, use the trick described for Usenet to put the whole URL in the name/comment portion of the address within double quotes.</p>
<p>“first last <a href="http://blah.com" rel="nofollow">http://blah.com</a>” </p>
<p>You might need to get a reply there, at least initially. Maybe only allow emails from your registrar and the<br />
ISP that hosts your site, forwarding<br />
the rest into the bit bucket.</p>
<p>The good thing is you can always decide to forward it back to your real email address for a while, in case, say, you need to complain about being forged. You can’t complain if you don’t own the visible email address and can receive email there.</p>
<p>Another option for site registration is to use the $50/year ones at Tonga, which is really in a consulate in the US somewhere.</p>
<p><a href="http://homepage.to/dnsrgstr.htm" rel="nofollow">http://homepage.to/dnsrgstr.htm</a></p>
<p>#  Unlike any other registrar, nobody can query your domain name and find out who owns that name, what servers or hosting provider you are using in what country or any other information about your domain name registration. They will only tell people whether or not a specific domain name has been registered.</p>
<p>—-</p>
<p>I think I read somewhere that you are in Portland, OR. Condolences. ;-)</p>
<p>Also, that you have Mac OS X.</p>
<p>I got that OS upgrade from 9 several weeks ago, and I am planning on moving all my operations onto it. It’s fabulous.</p>
<p>Have you tried training its junkmail spotter? Some sort of heuristics are involved. Take your main mail address, send it to two real POP boxes, read one using Mail under Mac OS X and see how intelligent it becomes. In training mode you can click to change the status from not-junk to Junk and the udder way.</p>
<p>I’m splitting (forwarding) my email into three pop boxes for now. One for my regular machine, one for the iMac, and one for reading it while at work.</p>
<p>OS X Mail has a full filtering capability under Preferences-&gt;Rules.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flüge USA</title>
		<link>http://iampariah.com/projects/other-projects/the-plan-to-reduce-spam.php/comment-page-1#comment-411</link>
		<dc:creator>Flüge USA</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=201#comment-411</guid>
		<description>A good idea!
</description>
		<content:encoded><![CDATA[<p>A good idea!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

