RE: Spam?

"Matt Beland" <[email protected]>
Newsgroups gmane.network.wireless.seattle.general
Message-ID <[email protected]>
Meaniemail said:
> thats a pretty bull answer, there is no reason other than lazyness why
> someone isn't either:

Nonsense. Most people stopped caring years ago. My first reaction to the
initial complaint - admittedly pre-caffeine on a Monday - was "hey, 1999
called, they want their issue back." Preventing your email address from
getting on a spam list is possible by only one method. Know what it is?

Don't use that address. At all. Period. No sending mail from it, don't
give it to anyone to send anything to it, zippo. Which would be kinda
worthless, wouldn't it? (Oh - and even *that* isn't perfect, if the domain
exists. Check out a real mail server's log sometime and see how many
random connections are made to it just trying random names and letter
combinations as destination addresses. I once got spam on an address that
was used only by an automated test script on a public-facing but private
network. The domain and user were valid, and the mail server accepted
connections from the outside world, so...)

Sure, it's a valid point that this type of thing makes it *easier*. But
it's just as much bull to claim that this type of thing is the source of
the problem, too. Besides - an open forum, such as this list, for an open
group, such as SeattleWireless - so open they leave anonymous write
available on the Wiki - deliberately blocking access to the archives or
munging mail addresses? Heh. Even if those measures were effective - and
they're not, just so we're clear - don't you think that'd look kinda
silly?

-- 
Matt Beland
[email protected]
http://www.rearviewmirror.org

_______________________________________________
Talk mailing list
[email protected]
http://seattlewireless.net/mailman/listinfo/talk
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.