Return-Path: Delivered-To: apmail-community-archive@www.apache.org Received: (qmail 22836 invoked from network); 17 Apr 2004 19:44:49 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 17 Apr 2004 19:44:49 -0000 Received: (qmail 50712 invoked by uid 500); 17 Apr 2004 19:44:35 -0000 Delivered-To: apmail-community-archive@apache.org Received: (qmail 50551 invoked by uid 500); 17 Apr 2004 19:44:33 -0000 Mailing-List: contact community-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: community@apache.org Delivered-To: mailing list community@apache.org Received: (qmail 50535 invoked from network); 17 Apr 2004 19:44:33 -0000 Received: from unknown (HELO mail.devtech.com) (66.112.202.2) by daedalus.apache.org with SMTP; 17 Apr 2004 19:44:33 -0000 Received: from localhost ([127.0.0.1]) by mail.devtech.com (JAMES SMTP Server 2.2.0-dev) with SMTP ID 782 for ; Sat, 17 Apr 2004 15:44:32 -0400 (EDT) From: "Noel J. Bergman" To: Subject: RE: ASF use spamassassin? Date: Sat, 17 Apr 2004 15:44:18 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: <39933.10.0.0.5.1082218436.squirrel@ags01.agsoftware.dnsalias.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > I think we really need good anti-spam tool rather than hidding > our identities. > I just hope soon the spam problem will find a final solution. The death penalty for convicted spammers would be a start. :-) Or a 1 dollar fine and 1 minute of jail time per spammed recipient. On the technology front, the ASRG (http://asrg.sp.am/) is starting to make headway. I am interested to see how its MARID WG plays out. MARID would require the sender's domain and authorized MTA(s) to be registered in DNS. Dynamic IP addresses present an issue, but there has been discussion about how DHCP users could update their information using Dynamic DNS (DDNS). Subject to DNS propogation, it would allow users in DHCP pools, as well as roaming users, to authenticate a new MTA address. In order for an infected Microsoft Windows system to be an effective spambot, it would have to be able to change the DNS information for the domain(s) it wants to use in forged sending addresses. Otherwise, it would be limited to spoofing whatever domains are registered with the current MTA. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: community-unsubscribe@apache.org For additional commands, e-mail: community-help@apache.org