A much more rational strategy. I have a line in my router for my personal address:
<cbort-*> = cbort
That way, I can give an address to entities that I don't entirely trust not to pass the address along to third parties. If I submit a form on XYZ's web site, I can give my address as [EMAIL PROTECTED] and know that I will receive mail sent to that address. If I subsequently start getting mail to that address from a third party, I will know that XYZ sold me out. If it gets bad, I can turn cbort-xyz into a spamtrap.
One danger that I discovered with a scheme exactly like this was that the part before the hyphen is actually a valid address.
Some harvesters appear to discard stuff after a hyphen thinking it to be anti spam stuff like "-removeme".
Also, some bulk mailers appear to truncate addresses in a attempt to get around similar suffixes. So they would try:
cbort-xy
cbort-x
cbort-
cbort <---- bingo!
To defeat these slimeballs, I use addresses of the form [EMAIL PROTECTED], where the "xyz" identifies the recipient and "z" (the real letter z!) is not an address. My router entries then become:
<z-badguy> = spamtrap
<z-*> = realaddress
A disadvantage I have found with this approach is that some Java based email address verifiers on web forms do not accept addresses containing hyphens.
-- Neil
Neil Herber Corporate info at http://www.eton.ca/ Eton Systems, 15 Pinepoint Drive, Nepean, ON, Canada K2H 6B1 Tel: (613) 829-4668
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
