[bcc to all contributors to #63995]

also sprach Don Armstrong <[EMAIL PROTECTED]> [2005.08.24.1024 +0200]:
> The solution (namely, turning @ into <!-- blah -->&#64<!-- blah --> is
> a needless obfuscation that isn't going to actually net us anything.

I agree with this (even though the approach works for me beautifully).

I've had major success with postfix spamtraps. The basic idea:

  for each address [EMAIL PROTECTED], add [EMAIL PROTECTED] (where 1 could be
  anything that's not going to be in regular email addresses; I use
  .tarpit) to whatever webpage.

  on the postfix side, add a PCRE or regexp map entry to
  check_recipient_access:

    /^.+\.bogus@/              DISCARD is a tarpit (explicit)

  profit.

The theory: spammers harvest addresses and [EMAIL PROTECTED] and
[EMAIL PROTECTED] are so close together that they are likely to be in the
same batch of mail sent out. Now if postfix receives
a multi-recipient mail, where [EMAIL PROTECTED] is one of the recipients,
it discards the whole mail.

Look at http://blog.madduck.net how I worked this in with HTML.

I guess one advantage of this is that everyone could do this
themselves, if they have a mail server they admin.

I'd love for @debian.org addresses to do something similar, e.g.
[EMAIL PROTECTED]

-- 
 .''`.   martin f. krafft <[EMAIL PROTECTED]>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)

Reply via email to