>>>>> "markd" == markd <[EMAIL PROTECTED]> writes:
markd> Hmm. Lemme get this right. You're telling me that people
markd> modify their email addresses so that spammers cannot
markd> automatically harvest them yet you then say that Gnus has code
markd> that automatically processes them? Are all harvester
markd> programmers too dumb to make this connection? I doubt it.
Well, true, some harvester programmers have half a grain of sense
somewhere in their rotten minds that allows them to use a whole lot of
regex's to defeat regular nospam e-mail addresses which people like
myself modify automatically through our MUA when we reply. But there
is no reason someone can't put "Reply to [EMAIL PROTECTED]
(remove biteme from domain)" in their sig which is totally unusual,
and annoying to have to cut and edit for a personal reply, but it
works. And since you but in a fake domain it bites the pants off the
people sending the spam... I would put up with people using this
method since I understand the frustations of spam...
>> A better alternative, IMHO, is to use a certain anti-spam e-mail
>> address (someone on this list uses it but I can't remember who)
>> that only lasts like a week, and then its gone. This gives most ppl
>> enuf
markd> Indeed this is an excellent strategy - if done properly. The
markd> problem is, a lot of people don't have the ability to capture
markd> all addresses in a domain - and of course user-random@domain
markd> is trivially defeated by a competent slicer and dicer if
markd> user@domain is valid. So this strategy only truly works for
markd> personal domains.
Here's a crazy idea: And it puts the pressure on crap MUA's, too :)
Use the user-random@domain format, but have the e-mail piped through a
command that checks the References in the e-mail, and if it contains a
valid reference to an e-mail that was posted from your own mail relay,
then it passes it, otherwise, it bounces it (or trashes it). How does
that sound? Have I missed anything?
>> time to reply. This won't cut down your bandwidth, however, but it
markd> If you can control your DNS you can apply a similar strategy
markd> to your domain by generating a reply address of
markd> [EMAIL PROTECTED] where @domain is not a valid mail
markd> target. But again, the number of people who have the
markd> opportunity, or capability to do this, are low.
True, but there are domain hosters out there who will host your domain
for $99 per year (sorry I don't know their names, I just remember
coming across them on occasion) that will let you modify your DNS at
will. Not as elegant as your own BIND server (which is what I have,
and I highly advise it for anyone serious about control), but if you
can work out some type of automation, it could do the job.
Regards
--
"Win95 not found, [P]arty, [C]elebrate, [D]rink ?"
