* Joerg-Olaf Schaefers wrote: > Im Hinblick auf spam prevention wird es dann aber durchaus > wieder interessant:
Ja, denn mail-archive.com ist genau das, was Spammer suchen ;-) > --snip-- http://www.mail-archive.com/faq.html#spam > > The Mail Archive utilizes two levels of electronic countermeasures to > prevent spam incidents. First, we explicitly block spam harvesting > robots (spambots) from accessing our server. We deny access, at the > server level, for any software that matches the browser ID of a known > spambot. Wettrüsten Teil eins: Man definiere seine Spambot-Zeile passend. > Our second line of defense is to make sure that the web pages > themselves are spambot resistant. We do not use any unshielded mailto: > hyperlinks, email addresses and we strip out, scramble, or obfuscate > email addresses from message headers and bodies. Yet we still provide > a way for people to reply to an archived message, using their regular > email software. This feat is achieved with a special POST protected > CGI gateway which returns a mailto: URL to the user agent. This > technique is extremely effective in blocking generic spam harvesting > robots; for more information, see Mullane's Spambot Beware guide. Wie schnell soll ich einen Harvester schreiben, der das ab kann? Selbst für whois auf tv Domains hat man so einen Blödsinn sich überlegt: Pro angegebene registrierte E-Mail kann man sechs Anfragen stellen. Lösung: Alle sechs Anfrage wird eine neue /dev/nul Adresse angemeldet. Automatisch. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]